|Docs translators no longer require membership 'cvsdocs' (except maybe the case for starting a new translation). Please refer to on instructions on how to become a member of the L10N Project and gain membership to the 'cvsl10n' group. Also, see this email to -trans-list . Please note that some of our guides might still reflect the old way.|
|We highly recommend that you refer to the Translation Quick Start Guide . If you are using Windows, you can still participate in translation; refer to Translating Fedora in Microsoft Windows for more information.|
This process is only for translating Fedora Docs Project files. If you prefer to help with translating programs in Fedora, visit the Translation Project page .
This process is temporary until tool improvements are complete. The future tools are going to be nice to use. Until then, we are doing this the hard way.
The schedule for documentation includes all the freeze dates for translation.
How To Get Started
- Follow the instructions on to become a member of the L10N Project. Once you have a Fedora Account and have become a member of the group 'cvsl10n', you'll be able to contribute translations to Docs. You don't need to be also a member of 'cvsdocs'.
- To checkout a module from CVS:
export CVSROOT=:ext:email@example.com:/cvs/docs cvs co docs-common
- A Fedora Core 4 or later system with these packages installed:
gnome-doc-utils // Provides xml2po xmlto // For testing build make // For testing build
To install these packages, use the following command:
su -c 'yum install gnome-doc-utils xmlto make'
- Subscriptions to fedora-docs-list , where all announcements and discussions take place, and fedora-docs-commits , so you can collaborate with other translators and toolmakers.
- Patience with the toolmakers as we learn about and build a good translation toolchain.
What to translate
The most important docs modules/directories for each release are the following:
To see all documents available in our repo, run:
export CVSROOT=:ext:firstname.lastname@example.org:/cvs/docs cvs co -c
See: DocsProject/Translation/Statistics . In general,
make postat and
make postat-<lang> should work.
Translating Documents Into English
If you have original content in a language other than English, you are welcome to contribute it to Fedora. It must follow the same processes that other contributions follow. You must have an editor who is not one of the writers, and who can read the language well enough to edit for grammar and style. You also may need a technical edit in the native language.
Once you have a document accepted in the native language, follow the DocsProject/WorkFlow#GettingADocumentTranslated usual process to get it translated.
#!html <!-- == Translation Process for Fedora Docs Project == This process covers translating XML-based documentation. Refer to [[Languages| Languages]] if you are interested in translating formal, static parts of the Wiki. You want to join [http://www.redhat.com/mailman/listinfo/fedora-websites-list fedora-websites-list] for discussions about the Wiki. 1. To list the available modules run these commands: <pre> export CVSROOT=:ext:email@example.com:/cvs/docs cvs co -c
To download a module to translate, list the current modules in the repository and then check out that module. You must also check out the docs-common module.
cvs co example-tutorial docs-common
1. OPTIONAL: This step is usually handled by the document author, so you will probably not have to perform it. If you have questions, ask on the fedora-docs-list. If no
po/ folder exists, you may need to add one to the CVS repository and create a POT template:
mkdir po cvs add po/ make pot
1. Change the
OTHERS macro in the Makefile to include your translation language:
OTHERS = it pt_BR
1. Make a new PO file for your locale:
1. Perform your translation using a tool like
lokalize on Fedora, or
poEdit on Windows, and save the PO file when done.
1. Test your build with the Makefile, try HTML output:
1. Commit your translation (PO file only) into CVS. For the message string (
-m option), you can use translation statistics or any other appropriate message. Remember these are emailed across the fedora-docs-commits mailing list. It is perfectly acceptable to do additional commits as you add to your translation.
cvs ci -m 'My message about translation' po/it.po
1. DO NOT commit any change to the Makefile until your translation is completely finished and ready for publication. If you have questions, ask on the fedora-docs-list. When your translation is finished, and builds correctly, then commit the Makefile change:
cvs ci -m 'Locale "it" translation finished' Makefile