Please accept this humble FAQ. Please direct comments to the list,
harsh criticism to me where I shall file it in its proper location. If
we like this (which means no one says they don't like it?), then I'll
propose either XML inclusion in the Doc Guide, or posting on the
FAQ originally proposed in
http://www.redhat.com/archives/fedora-docs-list/2003-November/msg00029.html, now brought to you in living email color:
## begin FAQ
Does Fedora Project need writers/editors?
Yes! Writers are needed right now more then editors, until we have
something to edit.
What documents does FP need?
FP documents are going to be of the tutorial/HOWTO variety. This is
the most useful information we can gather at this time, and it works
well with the distributed project. Currently, the only full-length
guide is the Installation Guide.
How is the docs project organized?
Rather loosely right now. Tammy Fox (tfox(a)redhat.com) is the
project leader. It has been proposed that translators can work in
teams by languages.
We may want to organize so that every writer has two-editors, and
contributors can work in either or both roles. This makes for a
more cumbersome process, but the quality control is higher.
What is the process/procedure for translating documents?
Details are currently outlined in this email:
What are PO files?
PO files are textual, editable files used in translation.
What are some of the tutorial/HOWTOs currently proposed?
From the mailing list:
* Installing an SSH server with public/private key authentication
* Configuring and using digital cameras
* Anaconda documentation (in process)
* Security considerings in installation
* Security other (by topic, i.e. filesystems, host, etc.)
* Configuring PDA
Can I translate the legal notice?
The legal notice page can be translated, but a statement that the
translation is provided for convenience only and that the English
language version takes precedence must be on the top of the page.
What are the tools for writing documents?
http://fedora.redhat.com/projects/docs details how to get the
Documentation Guide source and tools. The toolchain is explained on
that page, with the exception of PO files (see What are PO files?).
Currently, there is a problem with PDF production (refer to
you have TeX experience and can help us resolve that one, please
I have a tutorial in HTML, how do I convert it to DocBook?
Grab html2db from http://www.cise.ufl.edu/~ppadala/tidy/ .
What are some resources for learning DocBook?
The definitive DocBook reference written and maintained by Norm
Walsh is available at http://docbook.org/tdg/en/html/docbook.html .
A combination tutorial and reference book is available at
Dave Pawson maintains a DocBook FAQ at
Can I have CVS write access?
Eventually, we intend for full contributors to have write access to
CVS, as well as access to other build environments. This is being
worked out across the entire Fedora Project, and is due to be
completed by the end of calendar year 2003. In the meantime, you
can contact the docs project leader Tammy Fox (tfox(a)redhat.com) with
If you wish to setup your own CVS repository, or join one that
others are using while waiting for the main Fedora Project CVS to be
set up, please see the mail thread starting at:
What else is can I do to help?
Have ideas for admonition graphics?
## 30 ##
Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664
kwade(a)redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995
Red Hat Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Do we need a block of additional ENTITY declarations as a standard in
the templates, or are they up to the tutorial authors to use? I have
been removing the existing block of Red Hat-specific declarations, and
replacing them with more Fedora-specific ones, such as:
<!ENTITY FEDORA "The Fedora Project">
<!ENTITY FEDORA-URL "<ulink url='http://fedora.redhat.com/'>http://fedora.redhat.com/</ulink>">
<!ENTITY DISTRO "Fedora Core">
<!ENTITY DOCS "The Fedora Documentation Project">
<!ENTITY DOCS-URL "<ulink url='http://fedora.redhat.com/projects/docs/'>http://fedora.redhat.com/projects/docs/</ulink>">
I don't see a need to standardize just for the sake of it; if this is
something that authors are expected to do for themselves, that's ducky
by me. I just don't want to step on any toes since I'm new to this part.
Paul W. Frields, RHCE
-----BEGIN PGP SIGNED MESSAGE-----
I'm new to this list as a subscriber, but I checked with the archives and
saw that you need docs more than reviewers. So I wanted to offer a work
in progress, which you can see evolve at
It's in Dutch, and I was maybe hoping to find volunteers to help me finish
this quicker? It's just that I started on a RedHat9 doc on the same
lines, but Fedora was released before that one was finished. I want to go
quicker this time. Maybe have a complete draft ready by Chrismas to give
to my parents or that sort of thing.
My Penguin, my freedom. http://tille.soti.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----
In Japan, Fedora JP Project started up and
activity is begun.
There are about 20 staff with an activity.
First, we are beginning to translate the document.
Developer's Guide and Doucumentation guide.
software po etc.
Now, when Red Hat Linux was released,
Japanese Documents were translated in Australia.
This time, does the schedule exist?
I was revising the pt_BR.po file from the anaconda-po translation, and
noticed that I still see many Red Hat Linux names instead of Fedora. We
should leave it? For example...
"You have chosen to use a pre-existing partition for this installation "
"without formatting it. Red Hat recommends that you format this
partition to "
"make sure files from a previous operating system installation do not
"problems with this installation of Linux. However, if this partition "
"contains files that you need to keep, such as a users home directories,
"you should continue without formatting this partition."
"The rescue environment will now attempt to find your Red Hat Linux "
"installation and mount it under the directory %s. You can then make any "
"changes required to your system. If you want to proceed with this step "
"choose 'Continue'. You can also choose to mount your file systems
"instead of read-write by choosing 'Read-Only'.\n"
"If for some reason this process fails you can choose 'Skip' and this step "
"will be skipped and you will go directly to a command shell.\n"
"This system appears to have third party packages installed that overlap
"packages included in Red Hat Linux. Because these packages overlap, "
"continuing the upgrade process may cause them to stop functioning
"or may cause other system instability. Please see the release notes for "
"Do you wish to continue the upgrade process?"
Call the developers? Change and commit the changes to CVS? Or just leave
The latest release of xmlto (0.0.17) uses w3m, if it is available, to
convert from DocBook XML to (HTML to) text. Previously it used lynx
or else links.
Let me know if it causes any problems.