Author: pfrields
Update of /cvs/docs/release-notes/F-7 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15203/F-7
Added Files: Makefile README-Accessibility README.fedora-release fedora-release-notes.spec indexhtml-foot indexhtml-head main.xsl readmes.xsl Log Message: Branch F-7 as of release date 2007-05-31
--- 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 fi it pa pt_BR pt sr sv uk zh_CN # bn_IN ca cs da de fr gu hr hu ja ml ms nb nl pl ru ta
# 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}/Entertainment.xml \ ${1}/Feedback.xml \ ${1}/FileSystems.xml \ ${1}/I18n.xml \ ${1}/Installer.xml \ ${1}/Java.xml \ ${1}/Kernel.xml \ ${1}/Legacy.xml \ ${1}/Live.xml \ ${1}/MailServers.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
endef
# ######################################################################## define find-makefile-common for d in docs-common ../docs-common ../../docs-common; do \ if [ -f $$d/Makefile.common ]; then echo "$$d/Makefile.common"; break; fi; done endef include $(shell $(find-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 ########################################################################
######### # # 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 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 PKGXML_template .PHONY: pkgxml-${1} pkgxml-${1}:: ${PKGNAME}-${VERSION}/ghelp/${1}/${DOCBASE}.xml $(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/ghelp/${1}/${DOCBASE}.xml) ${PKGNAME}-${VERSION}/ghelp/${1}/${DOCBASE}.xml:: ${XMLFILES-${1}} \ ${XMLDEPFILES-${1}} mkdir -p ${PKGNAME}-${VERSION}/ghelp/${1} ${XMLLINT} ${XMLLINTOPT} ${1}/${DOCBASE}.xml > $$@ endef
$(foreach L,${LANGUAGES},$(eval $(call PKGXML_template,${L})))
define PKGTXT_template .PHONY: pkgtxt-${1} pkgtxt-${1}:: ${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt $(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt) ${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt:: ${DOCBASE}-${1}.txt mkdir -p ${PKGNAME}-${VERSION} cp ${DOCBASE}-${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})))
# This could be combined with OMFVAR_template later... define PKGOMFVAR_template $(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}}"" endef
$(foreach L,${LANGUAGES},$(eval $(call PKGOMFVAR_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})))
.PHONY: release-pkg release-pkg:: ${PKGNAME}-${VERSION}.tar.gz ${PKGNAME}-${VERSION}.tar.gz:: $(foreach L,${LANGUAGES},${PKGFILES-${L}}) cp -a --parents css/*css fedora.css img/*png stylesheet-images/*png ${PKGNAME}-${VERSION} 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'
# To build the SRPM, you must build "make release-pkg" in the following # modules and copy the resulting tarball to this module: # about-fedora/ # homepage/ # readme/ # readme-burning-isos/ # Make sure that each external module's Makefile defines VERSION the # same as in this module's specfile.
# THE FOLLOWING IS A NASTY HACK TO MAKE LIFE EASIER FOR REL-ENG. FDPCVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/docs homepage-${VERSION}.tar.gz:: test -d homepage && (cd homepage ; cvs up) || \ cvs -d ${FDPCVSROOT} co homepage-devel-dir (cd homepage ; make release-pkg) cp -u homepage/$@ . clean:: rm -f homepage-${VERSION}.tar.gz distclean:: rm -rf homepage
about-fedora-${VERSION}.tar.gz:: test -d about-fedora && (cd about-fedora ; cvs up) || \ cvs -d ${FDPCVSROOT} co about-fedora-devel-dir (cd about-fedora ; make release-pkg) cp -u about-fedora/$@ . clean:: rm -f about-fedora-${VERSION}.tar.gz distclean:: rm -rf about-fedora
README-${VERSION}.tar.gz:: test -d readme && (cd readme ; cvs up) || \ cvs -d ${FDPCVSROOT} co readme-devel-dir (cd readme ; make release-pkg) cp -u readme/$@ . clean:: rm -f README-${VERSION}.tar.gz distclean:: rm -rf readme
README-BURNING-ISOS-${VERSION}.tar.gz:: test -d readme-burning-isos && (cd readme-burning-isos ; cvs up) || \ cvs -d ${FDPCVSROOT} co readme-burning-isos-devel-dir (cd readme-burning-isos ; make release-pkg) cp -u readme-burning-isos/$@ . clean:: rm -f README-BURNING-ISOS-${VERSION}.tar.gz distclean:: rm -rf readme-burning-isos
.PHONY: release-srpm release-srpm:: ${PKGNAME}-${VERSION}-${RELEASE}.src.rpm ${PKGNAME}-${VERSION}-${RELEASE}.src.rpm:: ${SPECFILE} \ ${PKGNAME}-${VERSION}.tar.gz \ homepage-${VERSION}.tar.gz \ about-fedora-${VERSION}.tar.gz \ README-${VERSION}.tar.gz \ README-BURNING-ISOS-${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 - 2007 by Red Hat, Inc. and others. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
== 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 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 * Using Emacspeak and Festival with Fedora * Reading news using Fedora and Emacspeak * Sending and reading email using Fedora and Emacspeak * Browsing the Web using Fedora and Emacspeak * Using Emacspeak to execute Fedora shell commands * Using BRLTTY with Fedora * Finding more information on Linux accessibility
== Why should people choose Fedora 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 (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:
== 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:
== 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.
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:
== 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). 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 ===
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, 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:
=== Using Emacspeak with Fedora ===
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 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 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 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 ===
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:
=== 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 that may be helpful include:
The Speakup Homepage:
http://www.braille.uwo.ca/speakup/
Trace Center:
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:
SHORT VERSION --------------
#/bin/bash cd /build/dir export CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/docs cvs co release-notes-<branch> # <branch> = F-7, devel... cd release-notes make release-srpm
LONG VERSION -------------
A lie. There is no long version.
-- PWF, rev. 2007-05-21
--- NEW FILE fedora-release-notes.spec --- Name: fedora-release-notes Version: 7.0.0 Release: 1 Summary: Release Notes for Fedora %{version} URL: http://fedoraproject.org/wiki/Docs/Beats
Group: System Environment/Base License: Distributable Source0: fedora-release-notes-%{version}.tar.gz Source1: homepage-%{version}.tar.gz Source2: about-fedora-%{version}.tar.gz Source3: README-%{version}.tar.gz Source4: README-BURNING-ISOS-%{version}.tar.gz 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 7, 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 %setup -D -q -a 1 %setup -D -q -a 2 %setup -D -q -a 3 %setup -D -q -a 4
%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 README-Accessibility $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 644 -D $F $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$F done pushd README-BURNING-ISOS-%{version}/ install -m 644 README-BURNING-ISOS*.txt $RPM_BUILD_ROOT%{_defaultdocdir}/HTML popd pushd homepage-%{version} install -m 644 homepage/* $RPM_BUILD_ROOT%{_defaultdocdir}/HTML install -m 644 homepage/index-en_US.html $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/index.html popd pushd about-fedora-%{version} find about-fedora/ -type f -exec install -m 644 -D {} $RPM_BUILD_ROOT%{_datadir}/gnome/help/{} ; 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 popd pushd ghelp find -type f -exec install -m 644 -D {} $RPM_BUILD_ROOT%{_datadir}/gnome/help/fedora-release-notes/{} ; popd install -m 755 -d $RPM_BUILD_ROOT%{_datadir}/omf/fedora-release-notes install -m 644 fedora-release-notes-*.omf $RPM_BUILD_ROOT%{_datadir}/omf/%{name}/
%clean rm -rf $RPM_BUILD_ROOT
%post if [ -x /usr/bin/scrollkeeper-update ]; then scrollkeeper-update -q -o %{_datadir}/omf/%{name}:%{_datadir}/omf/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 %{_datadir}/gnome/help/about-fedora/ %{_datadir}/gnome/help/fedora-release-notes/ %{_datadir}/applications/about-fedora.desktop %{_datadir}/omf/fedora-release-notes/ %{_datadir}/omf/about-fedora/
%changelog * Thu May 10 2007 Paul W. Frields stickster@gmail.com - 7.0.0-1 - Fix fedora-release-notes to use yelp ghelp facility - Fix post script to properly update scrollkeeper - Build for F7
* Fri Apr 27 2007 Paul W. Frields stickster@gmail.com - 6.93-3 - Relocate about-fedora and use yelp's ghelp: facility (#208220) - Fix distro name in OMF and document metadata
* Mon Apr 23 2007 Jesse Keating jkeating@redhat.com - 6.93-2 - Updated translations and bits from wiki
* Sun Apr 15 2007 Paul W. Frields stickster@gmail.com - 6.93-1 - Update for Fedora 7 test4
* Fri Mar 23 2007 Paul W. Frields stickster@gmail.com - 6.92-5 - Bump release to include fixes in homepage module
* Fri Mar 23 2007 Paul W. Frields stickster@gmail.com - 6.92-4 - Add temporary community help notice to Release Notes for F7 test3
* Thu Mar 22 2007 Paul W. Frields stickster@gmail.com - 6.92-3 - Bump release for rebuild
* Thu Mar 22 2007 Paul W. Frields stickster@gmail.com - 6.92-2 - Use content from all supplemental modules in Docs CVS
* Mon Mar 19 2007 Paul W. Frields stickster@gmail.com - 6.92-1 - Update for Fedora 7 test3
* Sat Jan 27 2007 Paul W. Frields stickster@gmail.com - 6.91-1 - Update for Fedora 7 test2
* Sun Oct 15 2006 Paul W. Frields stickster@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@gmail.com - 6-2 - Localize About Fedora menu item (somewhat)
* Thu Oct 05 2006 Jesse Keating jkeating@redhat.com - 6-1 - Build for FC6, lots of new translations
* Sat Sep 30 2006 Paul W. Frields stickster@gmail.com - 5.92-7 - Include new i18n browser home page
* Mon Sep 25 2006 Jesse Keating jkeating@redhat.com - 5.92-6 - Bump for lang fixes
* Tue Sep 12 2006 Paul W. Frields stickster@gmail.com - 5.92-5 - Update scrollkeeper data for about-fedora
* Mon Sep 11 2006 Paul W. Frields stickster@gmail.com - 5.92-4 - Update about-fedora
* Wed Sep 6 2006 Paul W. Frields stickster@gmail.com - 5.92-3 - Make sure we package README-BURNING-ISOS files
* Tue Sep 5 2006 Jesse Keating jkeating@redhat.com - 5.92-1 - Bump for 5.92
* Fri Sep 1 2006 Paul W. Frields stickster@gmail.com - 5.91-8 - Handle i18n OMF files
* Sat Aug 26 2006 Paul W. Frields stickster@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@redhat.com - 5.91-6 - bump
* Wed Aug 2 2006 Paul W. Frields stickster@gmail.com - 5.91-5 - Add README-Accessibility (moved from fedora-release)
* Wed Jul 26 2006 Paul W. Frields stickster@gmail.com - 5.91-4 - Process paths correctly (#200266) - Package standalone HTML
* Sun Jul 23 2006 Jesse Keating jkeating@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@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>
docs-commits@lists.fedoraproject.org