release-notes/FC-6 Makefile, NONE, 1.1 README-Accessibility, NONE, 1.1 README.fedora-release, NONE, 1.1 about-gnome.desktop, NONE, 1.1 about-gnome.desktop.in, NONE, 1.1 about-kde.desktop, NONE, 1.1 about-kde.desktop.in, NONE, 1.1 about-title.xsl, NONE, 1.1 fedora-release-notes.spec, NONE, 1.1 indexhtml-foot, NONE, 1.1 indexhtml-head, NONE, 1.1 main.xsl, NONE, 1.1 readmes.xsl, NONE, 1.1 sources, NONE, 1.1
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Sat Oct 28 22:21:36 UTC 2006
Author: pfrields
Update of /cvs/docs/release-notes/FC-6
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6395/FC-6
Added Files:
Makefile README-Accessibility README.fedora-release
about-gnome.desktop about-gnome.desktop.in about-kde.desktop
about-kde.desktop.in about-title.xsl fedora-release-notes.spec
indexhtml-foot indexhtml-head main.xsl readmes.xsl sources
Log Message:
Add FC-6 branch. This branch should be used for errata updates, not devel -- although syncing them is fine.
--- NEW FILE Makefile ---
########################################################################
# Fedora Documentation Project Per-document Makefile
# License: GPL
# Copyright 2005,2006 Tommy Reynolds, MegaCoder.com
########################################################################
#
# Document-specific definitions.
#
DOCBASE = RELEASE-NOTES
PRI_LANG = en_US
OTHERS = el es it pl pt_BR pt ru sv zh_CN
FDPDIR = ${PWD}/../..
# Special legalnotice for this document:
LEGALNOTICEBASE =legalnotice-relnotes
# Special basename for packaging:
PKGNAME =fedora-release-notes
# Special PKGRPMFLAGS to keep Rawhide happy for f13
PKGRPMFLAGS =--define "_topdir ${PWD}" --define "_specdir ${PWD}" --define "_sourcedir ${PWD}" --define "_srcrpmdir ${PWD}" --define "_rpmdir ${PWD}"
########################################################################
# List each XML file of your document in the template below. Append the
# path to each file to the "XMLFILES-${1}" string. Use a backslash if you
# need additional lines. Here, we have one extra file "en/para.xml"; that
# gets written as "${1}/para.xml" because later, make(1) will need to compute
# the necesssary filenames. Oh, do NOT include "fdp-info.xml" because that's
# a generated file and we already know about that one...
define XMLFILES_template
XMLFILES-${1}= ${1}/ArchSpecific.xml \
${1}/BackwardsCompatibility.xml \
${1}/Colophon.xml \
${1}/DatabaseServers.xml \
${1}/Desktop.xml \
${1}/Devel.xml \
${1}/Extras.xml \
${1}/Entertainment.xml \
${1}/Feedback.xml \
${1}/FileSystems.xml \
${1}/I18n.xml \
${1}/Installer.xml \
${1}/Java.xml \
${1}/Kernel.xml \
${1}/Legacy.xml \
${1}/Multimedia.xml \
${1}/OverView.xml \
${1}/PackageChanges.xml \
${1}/PackageNotes.xml \
${1}/ProjectOverview.xml \
${1}/RELEASE-NOTES.xml \
${1}/Security.xml \
${1}/Virtualization.xml \
${1}/WebServers.xml \
${1}/Welcome.xml \
${1}/Xorg.xml \
${1}/about-fedora.xml \
${1}/README.xml \
${1}/README-BURNING-ISOS.xml \
${1}/homepage.xml
endef
#
########################################################################
include ../../docs-common/Makefile.common
########################################################################
#
# If you want to add additional steps to any of the
# targets defined in "Makefile.common", be sure to use
# a double-colon in your rule here. For example, to
# print the message "FINISHED AT LAST" after building
# the HTML document version, uncomment the following
# line:
#${DOCBASE}-en/index.html::
# echo FINISHED AT LAST
########################################################################
###########
#
# Get or build OMF.
#
# If the per-doc Makefile provides a ${OMFINFILES} list, we use those.
# If it does not, and ${BUILDOMF} is defined, make one using XSLT and
# rpm-info data.
#
# The template OMF files are expected to use @VARNAME@ notation to
# allow replacement of their content dynamically at build time. They
# should retain this notation during PO/POT conversion so that
# translators never have to worry about that content. Substitution
# only occurs during the packaging process.
#
# FIXME: There may not be a need to have the ${PRI_LANG} prefixing
# each entry in ${OMFINFILES}. Might be a good idea to take that out.
# if OMFINFILES is empty, try and get the file list.
# If it's still empty, and BUILDOMF is set, use that to populate the list.
# Otherwise it stays empty. After all, we may not want them at all.
ifeq "${OMFINFILES}" ""
OMFINFILES=$(foreach F,$(wildcard ${PRI_LANG}/*.omf.in),$(shell basename ${F}))
ifeq "${OMFINFILES}" ""
ifdef BUILDOMF
OMFINFILES=${PKGNAME}.omf.in
${PRI_LANG}/${PKGNAME}.omf.in:: ${PRI_LANG}/${RPMINFO}
${XSLTPROC} --stringparam lang ${PRI_LANG} \
--stringparam docbase ${PKGNAME} \
${FDPDIR}/docs-common/packaging/omf-in.xsl \
$< > $@
endif
endif
endif
showvars::
@echo "OMFINFILES=\"${OMFINFILES}\""
define OMFVAR_template
$(foreach F,${OMFINFILES},$(eval OMFINFILES-${1}+=${1}/${F}))
$(foreach F,${OMFINFILES},$(eval OMFFILES-${1}+=$(patsubst %.in,${1}/%,${F})))
$(foreach F,${OMFINFILES},$(eval PKGOMFFILES-${1}+=$(patsubst \
%.omf.in,$(if $(findstring ${PRI_LANG},${1}),%-C.omf,%-${1}.omf), \
${F})))
showvars-debug::
@echo "PKGOMFFILES-${1}=\"${PKGOMFFILES-${1}}\""
@echo "OMFFILES-${1}=\"${PKGOMFFILES-${1}}\""
endef
$(foreach L,${LANGUAGES},$(eval $(call OMFVAR_template,${L})))
define OMFIN_template
.PHONY: omf-in-${1}
omf-in-${1}:: ${OMFINFILES-${1}}
# Treat .omf.in files just like XML... since they are!
$(foreach F,${OMFINFILES},$(eval $(call XML_template,${1},${PRI_LANG}/${F})))
clean::
${RM} ${OMFINFILES-${1}}
help::
@printf ${TFMT} 'omf-in-${1}' 'Make OMF input file for ${1}'
endef
$(foreach L,${OTHERS},$(eval $(call OMFIN_template,${L})))
.PHONY: omf-in
omf-in:: $(foreach L,${LANGUAGES},${OMFINFILES-${L}})
help::
@printf ${TFMT} 'omf-in' 'Make all OMF input files'
# To make the real OMF, just do a quick bit of sed processing.
# The spacing in the second command is purposeful to ensure no extra
# space appears in the sed command.
#
# Note the difference between @LANG@ and @LANGC@: the former is always
# replaced by the locale name, whereas the latter is replaced by the
# locale name *unless* the locale is en_US, in which case is is replaced
# by "C", the fallback.
%.omf: %.omf.in
sed -e 's!@RELEASE@!${VERSION}!g' $< > $@
sed -i 's!@DATE@!${REVDATE}!g' $@
sed -i 's!@LANG@!$(patsubst %/$(shell basename $<),%,$<)!g' $@
sed -i 's!@LANGC@!$(if $(findstring en_US,$(patsubst \
%/$(shell basename $<),%,$<)),C,$(patsubst \
%/$(shell basename $<),%,$<))!g' $@
define OMF_template
.PHONY: omf-${1}
omf-${1}:: ${OMFFILES-${1}}
clean::
${RM} ${OMFFILES-${1}}
help::
@printf ${TFMT} 'omf-${1}' 'Make all OMF files for ${1} locale'
endef
$(foreach L,${LANGUAGES},$(eval $(call OMF_template,${L})))
.PHONY: omf
omf:: $(foreach L,${LANGUAGES},${OMFFILES-${L}})
help::
@printf ${TFMT} 'omf' 'Make all OMF files for all locales'
define HACK_HTML_template
.PHONY: homepage-${1}
$(eval HOMEPAGEDIR=homepage)
$(eval HTMLEXTRAFILES-${1}=${HOMEPAGEDIR}/index-${1}.html)
$(eval HOMEPAGE_CSS=${HOMEPAGEDIR}/homepage.css)
$(eval HOMEPAGE_XSL=${HOMEPAGEDIR}/homepage.xsl)
homepage-${1}:: ${HOMEPAGEDIR}/index-${1}.html
${HOMEPAGEDIR}/index-${1}.html:: ${1}/homepage.xml ${XMLDEPFILES-${1}}
# Can we get away with just the above? Let's see...
LANG=$(1).UTF-8 ${XMLTO} html -x $(XSLHTML) -m ${HOMEPAGE_XSL} $(1)/homepage.xml
move-if-change index.html ${HOMEPAGEDIR}/index-${1}.html
mkdir -p stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png stylesheet-images
clean::
rm -rf ${HOMEPAGEDIR}/index-${1}.html stylesheet-images/
endef
$(foreach L,${LANGUAGES},$(eval $(call HACK_HTML_template,${L})))
define HACK_TXT_template
.PHONY: readme-${1} readme-isoburn-${1}
$(eval TXTEXTRAFILES-${1}=README-${1}.txt README-BURNING-ISOS-${1}.txt)
readme-${1}:: README-${1}.txt
README-${1}.txt:: ${1}/README.xml
LANG=${1}.UTF-8 ${XMLLINT} ${XMLLINTOPT} ${1}/README.xml \
> ${1}/README.lint.xml
LANG=${1}.UTF-8 ${XSLTPROC} \
${FDPDIR}/docs-common/packaging/strip-for-txt.xsl \
${1}/README.lint.xml > ${1}/README.stripped.xml && \
${RM} -f ${1}/README.lint.xml
LANG=${1}.UTF-8 ${XMLTO} ${XMLTOTXTPOSTOPT} txt \
${1}/README.stripped.xml && \
move-if-change README.stripped.txt README-${1}.txt
readme-isoburn-${1}:: README-BURNING-ISOS-${1}.txt
README-BURNING-ISOS-${1}.txt:: ${1}/README-BURNING-ISOS.xml
LANG=${1}.UTF-8 ${XMLLINT} ${XMLLINTOPT} ${1}/README-BURNING-ISOS.xml \
> ${1}/README-BURNING-ISOS.lint.xml
LANG=${1}.UTF-8 ${XSLTPROC} \
${FDPDIR}/docs-common/packaging/strip-for-txt.xsl \
${1}/README-BURNING-ISOS.lint.xml > \
${1}/README-BURNING-ISOS.stripped.xml && \
${RM} -f ${1}/README-BURNING-ISOS.lint.xml
LANG=${1}.UTF-8 ${XMLTO} ${XMLTOTXTPOSTOPT} txt \
${1}/README-BURNING-ISOS.stripped.xml && \
move-if-change README-BURNING-ISOS.stripped.txt \
README-BURNING-ISOS-${1}.txt
clean::
${RM} -f ${TXTEXTRAFILES-${1}}
${RM} -f ${1}/README.stripped.xml ${1}/README-BURNING-ISOS.stripped.xml
txt-${1} text-${1}:: ${TXTEXTRAFILES-${1}}
showvars::
@echo "TXTEXTRAFILES-${1}=\"${TXTEXTRAFILES-${1}}\""
endef
$(foreach L,${LANGUAGES},$(eval $(call HACK_TXT_template,${L})))
.PHONY: readme
readme:: $(foreach L,${LANGUAGES},${TXTEXTRAFILES-${L}})
#########
#
# These rules are for use in packaging the release notes for an ISO
# spin. To do so, just run "make release-pkg" and out pops a shiny
# tarball named "${PKGNAME}-<VER>.tar.gz where <VER> is the FC
# release (5.91, 6, etc.).
#
#########
#define PKGOMFFILES_template
#ifeq "${1}" "${PRI_LANG}"
#PKGOMFFILES-${1}=$(patsubst %.omf,%-C.omf,${OMFFILES-${1}})
#else
#PKGOMFFILES-${1}=$(patsubst %.omf,%-${1}.omf,${OMFFILES-${1}})
#endif
#showvars::
# @echo "PKGOMFFILES-${1}=${PKGOMFFILES-${1}}"
#endef
$(foreach L,${LANGUAGES},$(eval $(call PKGOMFFILES_template,${L})))
define PKGOMF_DOC_template
.PHONY: pkgomf-${1}-${2}
ifeq "${2}" "${PRI_LANG}"
pkgomf-${1}-${2}:: ${PKGNAME}-${VERSION}/${1}-C.omf
${PKGNAME}-${VERSION}/${1}-C.omf:: ${2}/${1}.omf
mkdir -p ${PKGNAME}-${VERSION}
cp ${2}/${1}.omf $$@
else
pkgomf-${1}-${2}:: ${PKGNAME}-${VERSION}/${1}-${2}.omf
${PKGNAME}-${VERSION}/${1}-${2}.omf:: ${2}/${1}.omf
mkdir -p ${PKGNAME}-${VERSION}
cp ${2}/${1}.omf $$@
endif
endef
$(foreach L,${LANGUAGES}, \
$(foreach F,$(patsubst %.omf.in,%,${OMFINFILES}), \
$(eval $(call PKGOMF_DOC_template,${F},${L}))))
define PKGOMF_template
.PHONY: pkgomf-${1}
pkgomf-${1}:: $(foreach F,${PKGOMFFILES-${1}},${PKGNAME}-${VERSION}/${F})
$(eval PKGFILES-${1}+=$(foreach F,${PKGOMFFILES-${1}},${PKGNAME}-${VERSION}/${F}))
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGOMF_template,${L})))
define PKGHTML_NOCHUNKS_template
.PHONY: pkghtml-nochunks-${1}
pkghtml-nochunks-${1}:: ${PKGNAME}-${VERSION}/${DOCBASE}-${1}.html
$(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${DOCBASE}-${1}.html)
${PKGNAME}-${VERSION}/${DOCBASE}-${1}.html:: ${DOCBASE}-${1}.html
mkdir -p ${PKGNAME}-${VERSION}
cp ${DOCBASE}-${1}.html $$@
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGHTML_NOCHUNKS_template,${L})))
define PKGHTML_HOMEPAGE_template
.PHONY: pkghtml-homepage-${1}
pkghtml-homepage-${1}:: ${PKGNAME}-${VERSION}/${HOMEPAGEDIR}/index-${1}.html
$(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${HOMEPAGEDIR}/index-${1}.html)
${PKGNAME}-${VERSION}/${HOMEPAGEDIR}/index-${1}.html:: ${HOMEPAGEDIR}/index-${1}.html
mkdir -p ${PKGNAME}-${VERSION}/${HOMEPAGEDIR}
cp ${HOMEPAGEDIR}/index-${1}.html $$@
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGHTML_HOMEPAGE_template,${L})))
define PKGTXT_template
.PHONY: pkgtxt-${1}
pkgtxt-${1}:: ${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt ${PKGNAME}-${VERSION}/README-${1}.txt ${PKGNAME}-${VERSION}/README-BURNING-ISOS-${1}.txt
$(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt ${PKGNAME}-${VERSION}/README-${1}.txt ${PKGNAME}-${VERSION}/README-BURNING-ISOS-${1}.txt)
${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt:: ${DOCBASE}-${1}.txt
mkdir -p ${PKGNAME}-${VERSION}
cp ${DOCBASE}-${1}.txt $$@
### README is hacked in until we have more control here...
${PKGNAME}-${VERSION}/README-${1}.txt:: README-${1}.txt
mkdir -p ${PKGNAME}-${VERSION}
cp README-${1}.txt $$@
${PKGNAME}-${VERSION}/README-BURNING-ISOS-${1}.txt:: README-BURNING-ISOS-${1}.txt
mkdir -p ${PKGNAME}-${VERSION}
cp README-BURNING-ISOS-${1}.txt $$@
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGTXT_template,${L})))
define PKG_template
.PHONY: release-pkg-${1}
release-pkg-${1}:: ${PKGFILES-${1}}
showvars::
@echo "PKGFILES-${1}=${PKGFILES-${1}}"
endef
$(foreach L,${LANGUAGES},$(eval $(call PKG_template,${L})))
${PKGNAME}-${VERSION}/about-gnome.desktop:: about-gnome.desktop.in \
$(foreach LN,${OTHERS},${LN}/about-fedora.xml)
$(eval NAME_L10N=Name=$(shell ${XSLTPROC} \
about-title.xsl ${PRI_LANG}/about-fedora.xml))
$(eval COMMENT_L10N=Comment=$(shell ${XSLTPROC} \
about-title.xsl ${PRI_LANG}/about-fedora.xml))
$(eval EXEC_L10N=Exec=yelp file:///usr/share/doc/${PKGNAME}-${VERSION}/about/C/about-fedora.xml)
$(foreach L,${LANGUAGES},$(eval \
NAME_L10N+=\nName[${L}]=$(shell ${XSLTPROC} \
about-title.xsl ${L}/about-fedora.xml)))
$(foreach L,${LANGUAGES},$(eval \
COMMENT_L10N+=\nComment[${L}]=$(shell ${XSLTPROC} \
about-title.xsl ${L}/about-fedora.xml)))
$(foreach L,${LANGUAGES},$(eval \
EXEC_L10N+=\nExec[${L}]=yelp file:///usr/share/doc/${PKGNAME}-${VERSION}/about/${L}/about-fedora.xml))
sed -e 's!@NAME-L10N@!${NAME_L10N}!' -e 's!@COMMENT-L10N@!${COMMENT_L10N}!' -e 's!@EXEC-L10N@!${EXEC_L10N}!' $< > $@
.PHONY: release-pkg
release-pkg:: ${PKGNAME}-${VERSION}.tar.gz
${PKGNAME}-${VERSION}.tar.gz:: $(foreach L,${LANGUAGES},${PKGFILES-${L}}) \
${PKGNAME}-${VERSION}/about-gnome.desktop
cp -a --parents css/*css fedora.css ${HOMEPAGE_CSS} img/*png stylesheet-images/*png ${PKGNAME}-${VERSION}
mkdir -p ${PKGNAME}-${VERSION}/about/C && \
cp ${PRI_LANG}/about-fedora.xml ${PKGNAME}-${VERSION}/about/C
$(foreach LN,${OTHERS},$(eval \
$(shell mkdir -p ${PKGNAME}-${VERSION}/about/${LN})))
$(foreach LN,${OTHERS},$(eval \
$(shell cp ${LN}/about-fedora.xml ${PKGNAME}-${VERSION}/about/${LN})))
cp -a README-Accessibility ${PKGNAME}-${VERSION}
tar czf ${PKGNAME}-${VERSION}.tar.gz ${PKGNAME}-${VERSION}
clean::
${RM} -rf ${PKGNAME}-${VERSION}.tar.gz
${RM} -rf ${PKGNAME}-${VERSION}
help::
@printf ${TFMT} 'release-pkg' 'Make a tarball suitable for import to Core'
.PHONY: release-srpm
release-srpm:: ${PKGNAME}-${VERSION}-${RELEASE}.src.rpm
${PKGNAME}-${VERSION}-${RELEASE}.src.rpm:: ${SPECFILE} ${PKGNAME}-${VERSION}.tar.gz
rpmbuild -bs ${PKGRPMFLAGS} ${SPECFILE}
clean::
${RM} -rf ${PKGNAME}-${VERSION}-${RELEASE}.src.rpm
help::
@printf ${TFMT} 'release-srpm' 'Make a SRPM suitable for import to Core'
--- NEW FILE README-Accessibility ---
Linux Accessibility Solutions
=============================
Copyright © 2003 by Red Hat, Inc.
Abstract
========
There are approximately 500 million people worldwide with some kind of
visual, hearing, or mobility impairment. There are currently over 54
million people with disabilities in the US alone and that number is
significantly increasing as the baby boomer generation continues to
age. People with disabilities often find it extremely difficult to
effectively use existing and emerging technologies designed without regard
to their needs. Websites with inaccessible content can also be problematic
for screen readers and other specialized devices used by the disabled
community.
Accessible features have been voluntarily integrated into operating
systems, Web interfaces and other technologies because of marketing
potential or because it was "the right thing to do." Equal access to
educational, professional and recreational technologies is rapidly becoming
a legal requirement. Federal agencies in numerous countries are formulating
accessibility standards. Federal requirements in the United States went
into effect in June 2001.
There are specialized hardware devices, applications and utilities
available that considerably increase the usability of Linux for individuals
with special needs.
This document covers the following topics:
==========================================
* Why should people choose Fedora Core as an accessibility solution?
* The Section 508 Mandate
* The Voluntary Product Accessibility Template (VPAT)
* Available open source tools, utilities and drivers
* Using Speakup with Fedora Core
* Using Emacspeak and Festival with Fedora Core
* Reading news using Fedora Core and Emacspeak
* Sending and reading email using Fedora Core and Emacspeak
* Browsing the Web using Fedora Core and Emacspeak
* Using Emacspeak to execute Fedora Core shell commands
* Using BRLTTY with Fedora Core
* Finding more information on Linux accessibility
Why should people choose Fedora Core as an accessibility solution?
==================================================================
Linux offers an inexpensive and efficient solution for the disabled
community. Open source software costs far less compared to tools that run
on other operating systems and Linux tools are often freely downloadable.
While the Graphic User Interface (GUI) is convenient for sighted users, it
is often inhibiting to those with visual impairments because of the
difficulty speech synthesizers have interpreting graphics. Linux is a great
OS for users with visual limitations because the GUI is not required by the
kernel. Most modern tools including email, news, Web browsers, calendars,
calculators and much more can run on Linux without the GUI. The working
environment can also be customized to meet the hardware or software needs
of the user.
Fedora Core (and its predecessor Red Hat Linux) is an extremely popular
Linux distribution; most industry professionals are familiar with it,
making it relatively straightforward to find assistance if necessary.
Red Hat provides the up2date client and Red Hat Network. These services
simplify file management and make it easier to effortlessly keep their
computers secure and up to date.
The Section 508 Mandate
=======================
The Section 508 Mandate is an addendum to the Rehabilitation Act of 1998
that requires federal agencies to use accessible electronic and information
technologies so that people with special needs have the same opportunities
as everyone else.
For detailed information about the requirements of the Section 508 Mandate,
visit this link:
http://www.section508.gov/
The Voluntary Product Accessibility Template (VPAT)
===================================================
The VPAT template details how a particular product or service conforms to
Section 508 criteria. The VPAT helps federal personnel adhere to Section
508 by helping them determine whether they are buying the most accessible
IT products and services available. The VPAT template participation by
private vendors is voluntary. These templates are hosted on the individual
vendor websites. The vendors maintain their own information and the
government does not endorse this information in any way. For more
information on these templates, contact the legal department at Red Hat
Inc.
Available open source tools, utilities and drivers
==================================================
Current development is focusing on visual and mobility impairments. There
are both software and hardware based solutions available. There are also
both console and graphic solutions available, however, the graphic
solutions are limited at this time. The GNOME Accessibility Project is
making great progress bringing the Gnome desktop up to speed.
For more information about the GNOME Accessibility Project, visit:
http://developer.gnome.org/projects/gap/
The KDE Accessibility Project is simultaneously working to make sure the
KDE desktop is accessible as well.
For more information about the KDE Accessibility Project, visit:
http://accessibility.kde.org/
Hardware
==========
The biggest advantage of the hardware speech solutions is that speech is
available before the OS loads (makes it easier to install). Hardware
solutions include speech synthesizers, braille terminals, braille printers,
sip and puff systems, eye gaze pointing devices, etc. These devices are
usually very expensive and it is difficult to find drivers for
them. Drivers are being written (mostly for speech synthesizers) for Linux
but they need to be tested and integrated by the community into "upstream"
software projects before becoming part of Fedora Core.
Jim Van Zandt has also written several servers that work with
Emacspeak. These servers can be found in a package called Emacspeak-ss on
Jim Van Zandt's website or linked within the Emacspeak HOWTO
The Emacspeak HOWTO is available online at:
http://www.mv.com/ipusers/vanzandt/Emacspeak-HOWTO.html
For more information on Emacspeak, visit:
http://emacspeak.sf.net/
Software
==========
This document focuses mostly on software tools and utilities that work with
Linux. Most of these tools have been developed by the Open Source community
and many have not yet been tested by Red Hat, Inc. Speakup, Emacspeak,
Festival and BRLTTY have been tested by Red Hat. Festival and Emacspeak
ships with Red Hat Linux 7.3 and later releases (including Fedora
Core). The following list of downloadable tools provide various functions:
* Software Speech Synthesizers:
IBM ViaVoice Outloud
Festival
MBROLA
Emacspeak
* Magnification Tools:
xzoom
SVGATextMode
* Speech Recognition Software:
IBM ViaVoice
cvoicecontrol
Xvoice
* Screen Readers:
Screader
Speakup
BRLTTY
Visual Bells
Keyboard Tools
AccessX
StickyKeys
GTKeyboard
Using Speakup with Fedora Core
================================
Speakup is a GPL screen review package written by Kirk Reiser and Andy
Berdan. Speakup gives users with visual or mobility impairments the ability
to have audible console feedback using a speech synthesizer. Red Hat
recommends Speakup for blind users because it provides an audible
installation and is fully supported by the blind open source community.
William F. Acker currently maintains the Speakup packages for the Red Hat
distribution. His contributions to the open source community and to blind
Linux users have been outstanding.
Speakup works with the following hardware synthesizers:
DoubleTalk PC/LT
LiteTalk
Accent PC/SA
Speakout
Artic Transport
Audapter
Braille 'N Speak / Type 'N Speak
Dectalk External and Express
Apollo2
For instructions on using Speakup with Fedora Core, visit:
http://www.linux-speakup.org/ftp/disks/redhat/HOWTO_INSTALL.html
For more information about Speakup, or to contribute to the Speakup project
visit:
http://www.linux-speakup.org
Using Emacspeak with Fedora Core
==================================
Before using Emacspeak, you should familiarize yourself with some
documentation. Start with "A Gentle Introduction to Emacspeak" by Gary
Lawrence Murphy, which is available online at:
http://emacspeak-guide.sourceforge.net/
The Emacspeak HOWTO written by Jim Van Zandt is also a very good resource,
although the document is limited to the Slackware distribution. The
Emascspeak HOWTO is available online at:
http://www.mv.com/ipusers/vanzandt/Emacspeak-HOWTO.html
Reading news using Fedora Core and Emacspeak
===============================================
Gnus is the news reader included with Emacspeak. Gnus gets the appropriate
data from the ~/.newsrc file in the user's home directory. To post and read
news through Emacspeak, refer to http://www.gnus.org/ for manuals,
tutorials, HOWTOs, and more. To start Gnus, type the following command.
Note that "M-x" means to hold down the [Meta] key (often labeled [Alt])
while simultaneously pressing the [x] key:
M-x gnus
This command displays all the newsgroups you are subscribed to. To select a
newsgroup, highlight your selection and press the space bar. Next, specify
how many articles you would like to open. Type the number you desire and
press [Enter]. This splits the screen into two buffers. The top section is
the summary buffer, the bottom section is the article buffer. You should
now be able to read your news. For a detailed overview of this tool, visit:
http://www.mv.com/ipusers/vanzandt/Emacspeak-HOWTO.html
Sending and reading email using Fedora Core and Emacspeak
===========================================================
There are several email clients available in Emacspeak. The Gnus
utility can actually be used for both email and news. Type:
M-x gnus
to start Gnus, then type:
M
to use the mail client.
The easiest tool to use is RMAIL. To send a message using RMAIL, type the
following command. Note that "C-x" means to hold down the [Ctrl] key while
simultaneously pressing the [x] key:
C-x m
Fill in the To: and Subject: fields. Put the body of the message below the
line that reads -text follows this line-. You can send the message when you
are finished by typing:
C-c C-c
To read a message using RMAIL type:
M-x rmail
For more information on using RMAIL visit:
http://www.gnu.org/manual/emacs-20.3/html_chapter/emacs_31.html
Browsing the Web using Fedora Core and Emacspeak
==================================================
You must download William Perry's w3 browser:
ftp://people.redhat.com/jlamb/
You can install the package from the FTP site (after you log in as root)
and type:
rpm -ivh ftp://people.redhat.com/jlamb/w3-4.0pre.44-1.i386.rpm
Once the package is installed, restart Emacspeak and type the following
command:
M-x w3
This starts the browser and opens the default homepage. For more
information on w3 including a tutorial and command explanation, read
through the information on the default home page, available online at:
http://www.cs.indiana.edu/elisp/w3/docs.html
Using Emacspeak to execute Linux shell commands
===============================================
You do not have to leave Emacspeak to execute a Linux command. To
execute a command within Emacspeak, type
ESC !
and then enter the name of the command you would like to run when
Emacspeak prompts you. To exit the command output window type:
C-x 1
This functionality is extremely useful. You can even print and compile
files you are working on within Emacspeak. For more information on Linux
shell commands refer to Josh's Linux Guide or any other comparable command
resource.
Josh's Linux Guide is available online at:
http://jgo.local.net/LinuxGuide/linux-commands.html
Using BRLTTY with Fedora Core
===============================
BRLTTY provides access to the Linux command line for blind people using
refreshable braille displays. The tool provides complete screen review
functionality and minimal speech capability. BRLTTY has been tested by Red
Hat Inc. and is available in RPM format. For information and documentation
on BRLTTY, visit the following link:
http://mielke.cc/brltty/
Finding more information on Linux accessibility
===============================================
The following documents offer helpful suggestions for making Linux
more accessible:
Linux Accessibility HOWTO
http://tldp.org/HOWTO/Accessibility-HOWTO/index.html
Keyboard-and-Console-HOWTO
http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO.html
Additional links which may be helpful include:
The Speakup Homepage
http://www.braille.uwo.ca/speakup/
Trace Center
http://trace.wisc.edu/
Blinux
http://leb.net/blinux/
--- NEW FILE README.fedora-release ---
==========================================
NOTES FOR PACKAGING FEDORA-RELEASE-NOTES
==========================================
If you want to turn the current release notes into a SRPM package for
import to Core, do the following:
1. Make sure you have the release-notes/ module and the docs-common/
module -- also in Docs CVS -- in the same location.
2. Edit the fedora-release-notes.spec file and edit the "Release" tag
and make a new entry in the %changelog. There is no need to use
%{?dist} since this is a single-release package.
3. Run 'make release-srpm' to build the SRPM. The contents of the
source tarball -- the ones not already in the top-level directory --
remain in the "fedora-release-notes-<version>/" directory if you want to
review them. The tarball is there as well.
-- PWF, rev. 18 July 2006
--- NEW FILE about-gnome.desktop ---
[Desktop Entry]
Encoding=UTF-8
Name=About Fedora
Comment=Learn more about Fedora
Exec=yelp file:///usr/share/doc/fedora-release-notes-@RELEASE@/about/C/about-fedora.xml
Icon=fedora-logo-icon
Terminal=false
Type=Application
Categories=X-Fedora-About;
StartupNotify=true
OnlyShowIn=GNOME;
--- NEW FILE about-gnome.desktop.in ---
[Desktop Entry]
Encoding=UTF-8
@NAME-L10N@
@COMMENT-L10N@
@EXEC-L10N@
Icon=fedora-logo-icon
Terminal=false
Type=Application
Categories=X-Fedora-About;
StartupNotify=true
OnlyShowIn=GNOME;
--- NEW FILE about-kde.desktop ---
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=About Fedora
GenericName=About Fedora
Comment=Learn more about Fedora
Exec=khelpcenter
Icon=
Path=
Terminal=false
Type=Application
DocPath=khelpcenter/plugins/about.html
Categories=Qt;KDE;Application;Core;
X-KDE-StartupNotify=true
OnlyShowIn=KDE;
GenericName[en_US]=About Fedora
--- NEW FILE about-kde.desktop.in ---
[Desktop Entry]
Version=1.0
Encoding=UTF-8
#Name=About Fedora
#GenericName=About Fedora
#Comment=Learn more about Fedora
#Exec=khelpcenter
@NAME-L10N@
@GENERICNAME-L10N@
@COMMENT-L10N@
@EXEC-L10N@
Icon=
Path=
Terminal=false
Type=Application
DocPath=khelpcenter/plugins/about.html
Categories=Qt;KDE;Application;Core;
X-KDE-StartupNotify=true
OnlyShowIn=KDE;
--- NEW FILE about-title.xsl ---
<?xml version="1.0" encoding="UTF-8"?>
<!-- Pull title from about-fedora.xml article -->
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output omit-xml-declaration="yes" preserve-space="no" encoding="UTF-8"
indent="no" method="text"/>
<xsl:template match="*">
<xsl:value-of select="/article/title"/>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE fedora-release-notes.spec ---
Name: fedora-release-notes
Version: 6
Release: 3
Summary: Release Notes for Fedora Core %{version}
URL: http://fedoraproject.org/wiki/Docs/Beats
Group: System Environment/Base
License: Distributable
Source0: fedora-release-notes-%{version}.tar.gz
#Source1: indexhtml-head
#Source2: indexhtml-foot
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: desktop-file-utils
Provides: indexhtml = %{version}-%{release}
Obsoletes: indexhtml < 9-3
%description
These are the official Release Notes for Fedora Core %{version},
written and edited by the Fedora community. For more
information on the Release Notes process or how you can
contribute, refer to the Release Notes HOWTO located at
http://fedoraproject.org/wiki/Docs/Beats/HowTo.
%prep
%setup -q
%build
#cat %{SOURCE1} > index.html
#sed 's/.*<div class="article"/<div class="article"/g' \
# RELEASE-NOTES-en_US.html >> index.html
#cat %{SOURCE2} >> index.html
sed -i 's/@RELEASE@/%{version}/g' about-gnome.desktop
%install
rm -rf $RPM_BUILD_ROOT
install -m 755 -d $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 fedora.css $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 homepage/* $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 homepage/index-en_US.html $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/index.html
install -m 644 README-Accessibility $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 README-BURNING-ISOS*.txt $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
for DIR in css img stylesheet-images ; do
install -m 755 -d $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$DIR
find $DIR -type f -exec install -m 644 {} $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$DIR \;
done
for F in RELEASE-NOTES-*.html; do
install -m 755 -D $F $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$F
done
find about/ -type f -exec install -m 644 -D {} $RPM_BUILD_ROOT%{_defaultdocdir}/fedora-release-notes-%{version}/{} \;
install -m 755 -d $RPM_BUILD_ROOT%{_datadir}/omf/fedora-release-notes
install -m 644 fedora-release-notes-*.omf $RPM_BUILD_ROOT%{_datadir}/omf/fedora-release-notes/
install -m 755 -d $RPM_BUILD_ROOT%{_datadir}/omf/about-fedora
install -m 644 about-*omf $RPM_BUILD_ROOT%{_datadir}/omf/about-fedora/
install -m 644 -D about-gnome.desktop $RPM_BUILD_ROOT%{_datadir}/applications/about-fedora.desktop
%clean
rm -rf $RPM_BUILD_ROOT
%post
if [ -x /usr/bin/scrollkeeper-update ]; then scrollkeeper-update -q -o %{_datadir}/omf/{%{name},about-fedora}; fi
if [ -x /usr/bin/update-desktop-database ]; then update-desktop-database &> /dev/null; fi
%postun
if [ -x /usr/bin/scrollkeeper-update ]; then scrollkeeper-update -q; fi
if [ -x /usr/bin/update-desktop-database ]; then update-desktop-database &> /dev/null; fi
%files
%defattr(-,root,root,-)
%{_defaultdocdir}/HTML
%{_defaultdocdir}/fedora-release-notes-%{version}/about
%{_datadir}/applications/about-fedora.desktop
%{_datadir}/omf/fedora-release-notes/
%{_datadir}/omf/about-fedora/
%changelog
* Sun Oct 15 2006 Paul W. Frields <stickster at gmail.com> - 6-3
- Fix IG publication URL
- Amend CSS to respect font selections and restore icons
* Sun Oct 8 2006 Paul W. Frields <stickster at gmail.com> - 6-2
- Localize About Fedora menu item (somewhat)
* Thu Oct 05 2006 Jesse Keating <jkeating at redhat.com> - 6-1
- Build for FC6, lots of new translations
* Sat Sep 30 2006 Paul W. Frields <stickster at gmail.com> - 5.92-7
- Include new i18n browser home page
* Mon Sep 25 2006 Jesse Keating <jkeating at redhat.com> - 5.92-6
- Bump for lang fixes
* Tue Sep 12 2006 Paul W. Frields <stickster at gmail.com> - 5.92-5
- Update scrollkeeper data for about-fedora
* Mon Sep 11 2006 Paul W. Frields <stickster at gmail.com> - 5.92-4
- Update about-fedora
* Wed Sep 6 2006 Paul W. Frields <stickster at gmail.com> - 5.92-3
- Make sure we package README-BURNING-ISOS files
* Tue Sep 5 2006 Jesse Keating <jkeating at redhat.com> - 5.92-1
- Bump for 5.92
* Fri Sep 1 2006 Paul W. Frields <stickster at gmail.com> - 5.91-8
- Handle i18n OMF files
* Sat Aug 26 2006 Paul W. Frields <stickster at gmail.com> - 5.91-7
- Add README-BURNING-ISOS.txt for inclusion in mirrors
- Put About document in proper directory
* Wed Aug 2 2006 Jesse Keating <jkeating at redhat.com> - 5.91-6
- bump
* Wed Aug 2 2006 Paul W. Frields <stickster at gmail.com> - 5.91-5
- Add README-Accessibility (moved from fedora-release)
* Wed Jul 26 2006 Paul W. Frields <stickster at gmail.com> - 5.91-4
- Process paths correctly (#200266)
- Package standalone HTML
* Sun Jul 23 2006 Jesse Keating <jkeating at redhat.com> - 5.91-3
- Only use tabs
- Version the indexhtml provides/obsoletes
- Cleanup post and postun scriptlets
- Don't require fedora-release, fedora-release requires us.
- Add a URL tag
* Sun Jul 16 2006 Paul W. Frields <stickster at gmail.com> - 5.91-1
- Initial release for Fedora Core 6 test2.
--- NEW FILE indexhtml-foot ---
</div></div>
<div class="fedora-corner-br"> </div>
<div class="fedora-corner-bl"> </div>
</div>
<!-- content END -->
<!-- footer BEGIN -->
<div id="fedora-footer">
Copyright © 2006 Red Hat, Inc. All rights reserved.
<br>
Fedora is a trademark of Red Hat, Inc.
<br>
The Fedora Project is not a supported product of Red Hat, Inc.
<br>
Red Hat, Inc. is not responsible for the content of other sites.
</div>
<!-- footer END -->
</body></html>
--- NEW FILE indexhtml-head ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><html><head><title>Fedora Project, sponsored by Red Hat</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" type="text/css" media="print" href="css/print.css">
<style type="text/css" media="screen">
@import url("css/layout.css");
@import url("css/content.css");
@import url("css/docbook.css");
</style>
<!-- <script src="offsite.js" type="text/javascript"></script> -->
<meta name="MSSmartTagsPreventParsing" content="TRUE">
<link rel="shortcut icon" href="http://fedora.redhat.com/images/favicon.ico">
<link rel="icon" href="http://fedora.redhat.com/images/favicon.ico"></head>
<body onload="OffSite();">
<!-- header BEGIN -->
<div id="fedora-header">
<div id="fedora-header-logo">
<a href="http://fedora.redhat.com/" id="link-internal"><img src="img/header-fedora_logo01.png" alt="Fedora Project"></a>
</div>
<div id="fedora-header-items">
<span class="fedora-header-icon">
<a href="http://fedora.redhat.com/Download/" id="link-internal"><img src="img/header-download.png" alt=" ">Download</a>
<a href="http://fedora.redhat.com/About/Projects/" id="link-internal"><img src="img/header-projects.png" alt=" ">Projects</a>
<a href="http://fedoraproject.org/wiki/FAQ/" id="link-internal"><img src="img/header-faq.png" alt=" ">FAQ</a></span>
</div>
</div>
<div id="fedora-nav"></div>
<!-- header END -->
<!-- leftside BEGIN -->
<div id="fedora-side-left">
<div id="fedora-side-nav-label">Site Navigation:</div> <ul id="fedora-side-nav">
<li><a href="http://fedora.redhat.com/" id="link-internal">Home</a></li>
<li><a href="http://fedora.redhat.com/Download/" id="link-internal">Download</a></li>
<li><a href="http://fedora.redhat.com/docs/" id="link-internal">Documentation</a><ul>
<li><strong><a href="http://fedora.redhat.com/docs/release-notes/" id="link-internal">Release Notes</a></strong></li>
</ul></li>
<li><a href="http://fedora.redhat.com/About/Projects/" id="link-internal">Projects</a></li>
<li><a href="http://fedora.redhat.com/Contribute/" id="link-internal">Contribute</a></li>
<li><a href="http://fedora.redhat.com/About/" id="link-internal">About</a></li>
<li><a href="http://fedoraproject.org/" id="link-internal">FedoraProject.org</a></li>
<li><a href="http://fedoraproject.org/wiki/FAQ" id="link-internal">Fedora Project FAQ</a></li>
<li><a href="http://fedoraforum.org/" id="link-internal">Fedora End-User Support Forum</a></li>
</ul>
</div>
<!-- leftside END -->
<!-- content BEGIN -->
<div id="fedora-middle-two">
<div class="fedora-corner-tr"> </div>
<div class="fedora-corner-tl"> </div>
<div id="fedora-content">
--- NEW FILE main.xsl ---
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:exsl="http://exslt.org/common"
version="1.0"
exclude-result-prefixes="exsl">
<xsl:import href="readmes.xsl"/>
<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets/html/chunk-common.xsl"/>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl"/>
<!-- Why is chunk-code now xsl:included?
Suppose you want to customize *both* the chunking algorithm used *and* the
presentation of some elements that may be chunks. In order to do that, you
must get the order of imports "just right". The answer is to make your own
copy of this file, where you replace the initial import of "docbook.xsl"
with an import of your own base.xsl (that does its own import of docbook.xsl).
Put the templates for changing the presentation of elements in your base.xsl.
Put the templates that control chunking after the include of chunk-code.xsl.
Voila! (Man I hope we can do this better in XSLT 2.0)
-->
<!-- don't show TOC for article because html viewer in anaconda doesn't support the dt and dl tags -->
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/profile-docbook.xsl"/>
<xsl:param name="onechunk" select="1"/>
<xsl:output method="html" encoding="utf-8" indent="no"/>
</xsl:stylesheet>
--- NEW FILE readmes.xsl ---
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
version='1.0'>
<xsl:output method="html" encoding="UTF-8" indent="no"/>
<!-- This sets the extension for HTML files to ".html". -->
<!-- (The stylesheet's default for XHTML files is ".xhtm".) -->
<xsl:param name="html.ext" select="'.html'"/>
<!-- This sets the filename based on the ID. -->
<xsl:param name="use.id.as.filename" select="'0'"/>
<xsl:param name="suppress.navigation" select="'1'"/>
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:param name="chapter.autolabel" select="'0'"/>
<xsl:template match="command">
<xsl:call-template name="inline.monoseq"/>
</xsl:template>
<xsl:template match="application">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guibutton">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guiicon">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guilabel">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guimenu">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guimenuitem">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guisubmenu">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="filename">
<xsl:call-template name="inline.monoseq"/>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE sources ---
### This describes the various package repositories (repos) that up2date will
### query for packages. It currently supports apt-rpm, yum, and "dir" repos.
### Format is one repository (repo) entry per line, # starts comments, the
### first word on each line is the type of repo.
### The default RHN (using "default" as the url means use the one in the
### up2date config file).
#up2date default
### Note: when a channel label is required for the non up2date repos,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repos.
### An apt style repo (the example is arjan's 2.6 kernel repo).
### The format is:
### type channel-label service:server path repo name
#apt arjan-2.6-kernel-i386 http://people.redhat.com ~arjanv/2.5/ kernel
### Note: for apt repos, there can be multiple repo names specified (space
### seperated).
### A yum style repo. The format is:
### type channel-label url
yum fedora-core-3 http://download.fedora.redhat.com/pub/fedora/linux/core/3/$ARCH/os/
yum updates-released-fc3 http://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/$ARCH/
yum-mirror fedora-core-3 http://fedora.redhat.com/download/up2date-mirrors/fedora-core-3
yum-mirror updates-released-fc3 http://fedora.redhat.com/download/up2date-mirrors/updates-released-fc3
#yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/3/$ARCH/
#yum-mirror updates-testing http://fedora.redhat.com/download/up2date-mirrors/updates-testing-fc3
#yum development http://download.fedora.redhat.com/pub/fedora/linux/core/development/$ARCH/
#yum-mirror development http://fedora.redhat.com/download/up2date-mirrors/fedora-core-rawhide
### A local directory full of packages (a "dir" repo). For example:
#dir my-favorite-rpms /var/spool/RPMS/
# Multiple versions of all repos except "up2date" can be used. Dependencies
# can be resolved "cross-repo" if need be.
More information about the Fedora-docs-commits
mailing list