On Wed, Feb 25, 2009 at 02:07:12PM +1000, Ruediger Landmann wrote:
just letting you know that the Installation Guide is now fully
I can confirm that every language version of the guide builds in html,
html-single, and PDF, with only one exception -- Chinese Simplified. I
/can/ confirm that Chinese Simplified builds in html and html-single, but
I haven't been able to confirm that it builds in PDF .
RPM building also works.
I've placed the publicanized version of the guide in the master branch of
the repo, and the f10 version in its own branch.
Superb! Great news Ruediger -- thank you for your work on this.
There are small structural changes between the f10 version of the
and the files in the current master branch, specifically:
* I've removed most of the entities that were used in the
only were they a real mess, but they were going to create significant
problems when positioning the guide upstream of the RHEL Installation
Really? Isn't using &DISTRO; a pretty good way to go, as opposed to
doing manual search and replace on "Fedora"? On the other hand, I'm
sure the usage wasn't consistent throughout which is surely a problem
Some urgent action is now needed on the localization front:
* f10 needs to be presented as a valid branch in the Transifex system;
and the separate .po files of the Publicanized version need to be made
available to translators
* Publican includes two "Common Content" files that need translation into
languages that Red Hat doesn't support. They are "Conventions" (which
explains the document conventions) and "Feedback" . The great news here
is that once these have been translated into any given language, they will
be available for /all/ Publicanized Fedora docs produced in that language,
since the .po files can be built into the Fedora brand that installs with
Publican. I've generated .pot files for these three sections. Other than
approaching translators directly, is there another way to bring these to
I'd say this is something to bring to fedora-trans-list, which is the
mailing list for the global Fedora L10n team.
On the RPM front:
* What needs to happen to get an RPM of this document approved for
inclusion in Fedora?
Probably the regular stuff -- produce a spec file and SRPM, and file a
bug for package review. There's more information on the package
maintainers site, but I believe Eric is going through (has been
through?) this process too.
What I'm doing next:
* working out how content can be merged between the Fedora and Red Hat
Enterprise Linux Installation Guides, which will allow the Fedora version
to be positioned upstream
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
- - - - http://pfrields.fedorapeople.org/
: stickster @ #fedora-docs, #fedora-devel, #fredlug