Translating Fedora

Fedora Core is the community version of Red Hat Linux. They are both popular Linux distributions.

What to Translate First

Fedora uses the PO format for translation which makes it quite standard. For your language to be included you need to reach 90% on the essential files. The essential file list includes these packages:

  • anaconda/anaconda-online-help/gui (help-screens-C)
  • anaconda/anaconda-po (anaconda)
  • comps-po
  • firstboot
  • rhgb
  • redhat-config-packages (It seems that this has been removed from the essential file list)
  • redhat-artwork
  • redhat-menus

Also look at the Direction setting based on the installation and bootup process process to see other packages that might be important.

Release Schedule

Fedora follows a six monthly release schedule which can be viewed here.

Red Hat releases are more conservative and will draw on translations found in the Fedora Core files.

Starting

As usual check on the mailing list to see if anyone is translating your language. If someone is then work out a way to combine forces. If not you will probably become the translation coordinator for your language. Either way you might want CVS access. In order to translate you don’t need CVS access. But you will as soon as you want the data in the applications.

Getting CVS access

Browse to http://i18n.redhat.com/cgi-bin/i18n-signup where you will have to supply your ssh public key. Use:

$ sh-keygen -t dsa

if you don’t have one. This key is found in

$HOME/.ssh/id_dsa.pub

just copy and paste it into the form.

Getting the files via CVS

To check out the translate module

$ cvs -d :ext:YOURUSERNAME@elvis.redhat.com:/usr/local/CVS  co translate

Note: the CVS directory is structured in the GNU way. Ie you have a POT file and all of the $LANG.po files in one directory. You may want to make a few scripts to allow PO and TEMPLATE directories per language if that is the way you are used to.

All files are in HEAD except system-config-packages which uses the redhat-config-packages-1_1_x branch for Fedora Core 3.

Per Language Checkout and Update scripts

Tools use to update POT and PO files for Fedora on a per langauge basis which is nicer as otherwise everything is thrown at you.

The tools look like they are from the early days of the Fedora so they might need updating to be relevant to the latest layout in CVS.

Enabling installation in your language

Once you’ve completed about 90% of the essential modules you can ask for your language to be included in the installation process.

File an enhancement request to get your language accepted as an anaconda install language.

Here is an example: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118028

You need to make changes to lang-table and lang-name

Checking

Red Hat treats translations as part of a component not as a global resource. So you will probably have to check that each item you have translated is included in the final RPM. You can either install the application and validate or download the beta SRPMS and check. Installing is easier but requires a large amount of bandwidth. Downloading the SRPM requires some RPM building experience or at least the ability to read an RPM spec file to check the contents or the ability to check the tarball within the SRPM to validate that your languages are included.

Additional

You might want to check on the following items which relate to localisation: