Archive:Translating documentation

= DocsProject/Translation =

Introduction
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'.

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs cvs co docs-common
 * To checkout a module from CVS:

gnome-doc-utils   // Provides xml2po xmlto             // For testing build make              // For testing build
 * A Fedora Core 4 or later system with these packages installed:

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:

1. 1.  1.  1.  1.  1.  1.  1.

To see all documents available in our repo, run:

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs cvs co -c

Translation statistics
See: DocsProject/Translation/Statistics. In general,  and   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 to get it translated.


 * 1) !html