ok im over on this list now (from anaconda-devel-list)
a few of us from the anaconda-devel list are interested in helping out
putting together some form of documentation for anaconda.
whether it be a FAQ, a HOW-TO, a general guide or whatever it needs to
be - we don't have much of an idea about how to get things rolling
and/or what type of topics to cover in the doc.
i'm hoping here we can get some advice and find a common meeting place
for getting some stuff down on 'paper'.
(p.s. - i hope no-one else posted a similar message b4 me - my mail is
still playing up)
-----BEGIN PGP SIGNED MESSAGE-----
I've been trying this all today, and I really like it. I was chatting to Tim
Waugh on our #fedora-devel irc channel today and has been using for ages and
also has rpms for it.
I think we should update the docs guide to include this as an alternative to
Trying to be a RHCE...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
-----END PGP SIGNATURE-----
Apologies to all those people who have showed interests in Fedora
Translation Project for responding so late. We have been quite busy
trying to clear out the last release.
To become a translator, you first need to sign up an account on
The steps to generate ssh key pair need by the sign up process are:
* open a terminal window
* [username@host homedirectory]$ cd .ssh
* [username@host .ssh]$ ls
* If you see "id_dsa" and "id_dsa.pub", you can skip the following
steps. However, you must remember the password you have used to generate
* If you do not see the above two files, do the following:
* [username@host .ssh]$ssh-keygen -t dsa
* You will be requested to enter your password twice to generate the key
* Once the keys are generated, copy the "id_dsa.pub" content and paste
it into the account sign up page. (you can use "cat id_dsa.pub" to
display the key content.)
Once you have submitted account request, and got it approved, you can
start to check out the modules.
The CVSROOT for the software translation module is
":ext:firstname.lastname@example.org:/usr/local/CVS". You can add aliases in
your ~/.bashrc file to make life easier. The alias name can be changed
using your own preference. And don't forget to substitute the "username"
with your user name. eg:
Now, you are ready to check out modules. The module name for software po
files is "translate". e.g.
[username@host homedirectory]$ cvs-software
[username@host homedirectory]$ cvs -z9 co translate
You should be able to find all software package names under ~/translate/
directory. Under each package, there are a number of po files such as
"de.po" or "zh_CN.po". The name represents the language code.
It's strongly advised that you coordinate with other translators in your
language group to avoid possible file conflicts or overwriting each
This is just a rough outline. We will post more detailed information on
the website as soon as we can.
Thanks for your contribution!
I really like the design of the fedora webpage. Just a minor remark,
when I read the page with a browser or on the other OS that does not
support anti aliased fonts the font looks quite bad. www.mozilla.org
uses a very similar font (maybe it's even the same :-) ) but the font
looks OK on the other OS. So maybe it's quite easy to fix this.
I subscribed to this list after reading a message in fedora-devel list
telling that here is the place for people willing to contribute to
Fedora translating software and docs to some language. Is this right? I
ask because I see this in the page:
The place to discuss the translation of software is fedora-devel-list.
I just want a place to start, so if anyone can point me something... Oh
yeah, and my language is Brazilian Portuguese.
It looks like we have some regular questions on this list. If we can
gather together some questions and answers, perhaps Tammy can post a FAQ
on fedora.redhat.com, and/or we can include the FAQ in the Mailman
"Welcome" email. I'm happy to maintain it for now.
Below is what I've thought of so far. Let's use this thread to gather
the questions and answers. These are my proposed answers, please feel
free to "fix" them:
## begin FAQ (draft) ##
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.
In the future, if small teams want to work on larger works similar
to the manuals for Red Hat products, we can work on adding that in.
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?
There is currently no defined process. We are waiting for the
participation of the ever-busy Red Hat docs translation team.
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
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
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. In the meantime, you
can contact the docs project leader Tammy Fox (tfox(a)redhat.com) with
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 Enterprise Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --