Edgewall Software

Version 104 (modified by Christian Boos, 9 years ago) ( diff )

updated make help text after r9764 and a word about eol-style property

Localization (L10N) of Trac

Trac uses Babel for localization. Trac trunk now contains the i18n framework and L10N files.

The Preferences ' Language panel can be used to select the language from the list of available translations, otherwise the web browsers' language preferences will be honored, if possible.

If you're only interested in using a localized version of Trac, then refer to the simpler 0.12/TracInstall instructions. The more complete installation instructions below are aimed at developers and translators.


Getting the Tool Chain

Python Tools

  1. Install Babel version 0.9.5
    Read the detailed installation instructions for Babel if you want to build it from source, but you should also be able to install it with a simple easy_install or by using one of the packages in the Download page linked above.
  2. Likewise, install Genshi version 0.6, using easy_install or by using one of the packages available for download.
  3. Get a svn checkout from the Trac trunk, e.g. svn checkout http://svn.edgewall.org/repos/trac/trunk trac-0.12dev

Translation Workflow

Using Python tools

  1. Run python setup.py extract_messages.
    This will generate the catalog template file: source:trunk/trac/locale/messages.pot
    You should never have to edit that file manually.
    Note: this step is for committers only. If you're not a Trac svn committer, you have to use the available messages.pot, or bug us to update that file (though we do it on a regular basis).
  2. Run python setup.py update_catalog.
    This will regenerate the various string catalogs (trac/locale/*_*/LC_MESSAGES/messages.po), preserving the previously translated strings and merging the new translations found in the messages.pot file. Translations that are no longer needed are commented out (#~) and moved at the bottom of the .po file.
    Usually, you will be interested in working on one locale only, so you can pass the -l option to specify which catalog should be updated. For example:
    python setup.py update_catalog -l nl_NL.
  3. Now, open your favorite editor and add or modify translations for the extracted strings in the messages.po file for your language.
  4. Once you're done, you should test your translations:
    1. Run python setup.py update_catalog -l again, for normalizing the manual edits. For example:
      python setup.py update_catalog -l nl_NL.
      This step is also quite useful for spotting the possible mistakes, like accidental changes of msgid strings. Look for lines beginning with #~, they are indicative of such errors. Note that the comments corresponding to translations which are no longer present in the messages.pot file (as discussed in step 2. above) have been discarded by this second update_catalog run.
    2. Run python setup.py compile_catalog -f.
      This will generate one compiled catalog (message.mo file) for each (or each specified) messages.po file. You don't need to do anything with those files, they'll get installed automatically.
      You will most probably need to use the force option (-f) in order to compile catalogs marked "fuzzy". It is fine to have fuzzy translations but try to never contribute a translation still containing those markers, as they mean that a given translation has not been reviewed by a human but were machine generated. Fuzzy translations should be either cleared when they are wrong, or validated when they are correct, by removing the fuzzy tag or even the whole line iff fuzzy was the only keyword on that line
      You can also use the -l option here to specify the locale for which the messages.po has to be compiled.
    3. Run python setup.py install for installing Trac and locale data. Alternatively you can use python setup.py develop once for all, if you want to be able to run Trac from your working copy.

Note that you could stop at step 3, but then you risk to submit incomplete or, worse, buggy messages.po files. Going through the 4th step will ensure a better quality standard. Finally, seeing your translations "live" in Trac is not only a great way to realize if the translation still makes sense once put in context, but also quite gratifying when you see that you picked the correct wording ;-)

Using msgfmt tools

Although Babel is Python specific and is the tool which is advised to use, the traditional msgfmt toolset can also be used. In particular, the following command is quite useful:

$ msgfmt --statistics --check trac/locale/pl/LC_MESSAGES/messages.po
979 translated messages, 85 fuzzy translations, 32 untranslated messages.

All is well, except for some fuzzy and missing translations ;-)

$ msgfmt --statistics --check trac/locale/zh_CN/LC_MESSAGES/messages.po
trac/locale/zh_CN/LC_MESSAGES/messages.po:2155: a format specification for argument 'unit', as in 'msgstr[0]', doesn't exist in 'msgid'
trac/locale/zh_CN/LC_MESSAGES/messages.po:2162: a format specification for argument 'unit', as in 'msgstr[0]', doesn't exist in 'msgid'
trac/locale/zh_CN/LC_MESSAGES/messages.po:2169: a format specification for argument 'unit', as in 'msgstr[0]', doesn't exist in 'msgid'
msgfmt: found 3 fatal errors
1058 translated messages.

Some errors were detected with format specifications.

This is a useful additional check, as python setup.py compile_catalog -l zh_CN wouldn't have detected that issue.

Using Transifex

The web-based collaborative site for translations Transifex has a project page for Trac.

From there, it is easy to download an always up to date messages.po file and start translating right away.

Your translation can then be uploaded and will for now be sent back to us by mail, but in the future they will be directly committed in a dedicated i18n repository clone of Trac.

It is important however to keep the messages.po files free from fatal errors as reported by msgfmt --check, as this might confuse Transifex and prevent it to report correct statistics or merge the messages.pot.

The easy way using make and l10n targets

You'll find a Makefile in the toplevel directory of the Trac source. If you're lucky enough to have the GNU make tool, you can benefit from some automation for these translation tasks.

$ make help
 ---------------- L10N tasks

  init-xy             create catalogs for given xy locale

  extraction          regenerate the catalog templates

  update              update all the catalog files from the templates
  update-xy           update the catalogs for the xy locale only

  compile             compile all the catalog files
  compile-xy          compile the catalogs for the xy locale only

  check               verify all the catalog files
  check-xy            verify the catalogs for the xy locale only

  stats               detailed translation statistics for all catalogs
  stats-pot           total messages in the catalog templates
  stats-xy            translated, fuzzy, untranslated for the xy locale only

  summary             display percent translated for all catalogs
  summary-xy          display percent translated for the xy locale only
                      (suitable for a commit message)

  diff                show relevant changes after an update for all catalogs
  diff-xy             show relevant changes after an update for the xy locale

  [locale=...]        variable for selecting a set of locales

Example usage:

$ make stats-pot update check compile stats locale='fr de'
translation statistics for messages.pot:
stats-pot: 0 translated messages, 1096 untranslated messages.
python setup.py update_catalog -l fr
running update_catalog
updating catalog 'trac/locale\\fr\\LC_MESSAGES\\messages.po' based on 'trac/locale/messages.pot'
python setup.py update_catalog -l de
running update_catalog
updating catalog 'trac/locale\\de\\LC_MESSAGES\\messages.po' based on 'trac/locale/messages.pot'
checking catalogs for fr de...
check-fr: OK
check-de: OK
All catalogs checked are OK
python setup.py compile_catalog -l fr
running compile_catalog
compiling catalog 'trac/locale\\fr\\LC_MESSAGES\\messages.po' to 'trac/locale\\fr\\LC_MESSAGES\\messages.mo'
python setup.py compile_catalog -l de
running compile_catalog
compiling catalog 'trac/locale\\de\\LC_MESSAGES\\messages.po' to 'trac/locale\\de\\LC_MESSAGES\\messages.mo'
translation statistics for fr de...
stats-fr: 1096 translated messages.
stats-de: 932 translated messages, 164 untranslated messages.


The various catalog files (messages.po) can be found in the repository under source:trunk/trac/locale. The messages.pot is the template file from which the various locale-specific files get created.

Adding translations for a new language

If you need to create a catalog for a new locale (e.g. et), do:

$ ./setup.py init_catalog -l et

Use ISO:639-1 language codes, only use national variant when there's a real need.

Then proceed through the steps listed above starting at step 2.



Kindly provided by http://sw.transifex.net/1/images/tx-logo-micro.png

Note that if the statistics for a language suddenly drop to 0%, this is indicative of the presence of fatal errors (as reported by msgfmt --check) in the corresponding messages.po file.

If you want to generate those statistics by yourself, do make summary. Be aware that those statistics can only be accurate if the catalogs are actually up to date with respect to the catalog template, so you should do a make update before. As this is quite expensive, you may want to do only make update summary locale="..." for the locales you're interested in.

Editing Guidelines

There are tons of good guidelines on the web about how to write good translations. See for example: PO_Odyssey and step-by-step, and other resources from http://l10n.kde.org. (The references also applies to translators using Windows, though the set of translation editors seems to be narrower. However, see Poedit for a multiplatform dedicated PO editor.)

In short, a translation unit is typically something like:

#: trac/ticket/templates/milestone_delete.html:41
#: trac/ticket/templates/milestone_view.html:105
msgid "Delete milestone"
msgstr "Supprimer le jalon"
  • the "#:" lines are comments indicating the locations of the message in the source.
  • msgid "..." is the message itself, this should never be changed
  • msgstr is your translation; you should keep there the same structure, as in the msgid. In particular the presence of "\n" at the beginning or the end of the msgid should be mirrored in msgstr
  • right after an automatic catalog update you'll see lots of:
    • # fuzzy comments: this identifies translations that are only approximated (the msgid has changed)
    • msgstr "" translations: those are newly added translations

There are a few more complex situations.

Here's a message containing parameters:

#: trac/ticket/templates/milestone_view.html:26
#, python-format
msgid ""
"Completed %(duration)s ago\n"
"              (%(date)s)"
msgstr ""
"Atteint il y a %(duration)s\n"
"                (%(date)s)"

Note that you need to keep the same set of parameters in msgid and msgstr, both for the name and the keyword (i.e. don't replace a %(id)s with a %(id)d), although you can reorder them as needed.

Another example, here's how a structured message looks like:

#: trac/ticket/templates/milestone_delete.html:45
msgid ""
"[1:Note:] See\n"
"      [2:TracRoadmap] for help on using\n"
"      the roadmap."
msgstr ""
"[1:Note :] consultez [2:TracRoadmap] pour obtenir de l'aide sur "
"l'utilisation de la feuille de route."

The [1: ...] groups are used when the message contains markup (this is Genshi specific). It is important to keep the same semantic structure. As with message parameters, the groups can be reordered but you should have the same groups in msgid and msgstr (see for example r9553).

Of course, you can have messages that combine markup groups and parameters names:

#: trac/ticket/templates/milestone_view.html:32
#, python-format
msgid ""
"[1:%(duration)s late]\n"
"              (%(date)s)"
msgstr ""
"[1:%(duration)s en retard]\n"
"                (%(date)s)"

Finally, there's the translation of sentences which have a singular and a plural form:

#: trac/ticket/templates/query.html:29
#: trac/ticket/templates/query_results.html:30
#: trac/ticket/templates/report_view.html:94
#, python-format
msgid "%(num)s match"
msgid_plural "%(num)s matches"
msgstr[0] "%(num)s résultat"
msgstr[1] "%(num)s résultats"
  • when such a message is newly added, you'll have
    #, fuzzy, python-format as the first comment. Be careful to remove only the fuzzy, part, but not the python-format keyword.
  • some languages (zh, ko, ja) don't have plural forms (plural == 1), so you only have to put a msgstr[0] line.
  • some other languages have more than 2 plural forms, so you need as many msgstr[] as needed.

Terms (Definitions)

Consistent and careful translation of terms like timeline, ticket, report is very important. These terms are used everywhere and must be easy to remember and comfortable to use.

The way to make up good translations of important terms is to discuss them before using everywhere. The easiest way to accomplish it is to set up wiki pages for different languages.

Look also at the various term definition pages: Am, Cy, Cz, De, El, Es, Fa, Fi, Fr, Gl, He, Hu, It, Ja, Ko, Lv, Nl, Pl, Pt, PtBr, Ru, Sv, Tr, ZhCn, ZhTw and TracTermTr (to be renamed once we have #1106).

Translation Coordination

For the various languages there are already various tickets logged in which the work on them is tracked:

Multi-language support in the wiki
Translation of Trac to Arabic/عربى [ar_EG]
Translation of Trac to Argentinian Spanish/español de Argentina [es_AR]
Translation of Trac to Armenian [hy_AM]
Translation of Trac to Catalan/Català [ca]
Translation of Trac to Chinese/中文 [zh_CN]
Translation of Trac to Czech/Česky [cs_CZ]
Translation of Trac to Dutch/Nederlands [nl_NL]
Translation of Trac to English [en_GB]
Translation of Trac to Estonian/eesti [et_EE]
Translation of Trac to Farsi/پارسی [fa_IR]
Translation of Trac to Finnish/suomi [fi_FI]
Translation of Trac to French/Français [fr_FR]
Translation of Trac to Galician/Galego [gl_ES]
Translation of Trac to German/Deutsch [de_DE]
Translation of Trac to Greek/Ελληνικά [el_GR]
Translation of Trac to Hebrew [he_HE]
Translation of Trac to Hungarian/Magyar [hu_HU]
Translation of Trac to Italian/Italiano [it_IT]
Translation of Trac to Japanese/日本語 [ja_JP]
Translation of Trac to Korean/한국어 [ko_KR]
Translation of Trac to Norwegian/bokmål [nb_NO]
Translation of Trac to Polish/Polski [pl_PL]
Translation of Trac to Portuguese/Português [pt_BR]
Translation of Trac to Portuguese/Português [pt_PT]
Translation of Trac to Romanian/Română [ro_RO]
Translation of Trac to Russian/Русский [ru_RU]
Translation of Trac to Slovene/Slovensko [sl_SI]
Translation of Trac to Spanish/Español [es_ES]
Translation of Trac to Swedish/Svenska [sv]
Translation of Trac to Traditional Chinese/正體中文 [zh_TW]
Translation of Trac to Turkish/Türkçe [tr_TR]
Translation of Trac to Vietnamese/Tiếng Việt [vi_VN]
Translations to Esperanto [eo]

This is a way by which translators for the same language can coordinate their work.

For Committers

If you have commit access to the translation catalogs in the SubversionRepository, then you should be careful to commit only error-less updates. Translations can be fuzzy or missing, that's not a problem, but the errors spotted by make check compile locale=<yourlocale> should really be fixed before committing. Please also take care of [n:...] nestings, as those mistakes are not detected by the above automated checks and are quite deadly (#9171).

The commit message should have the following format:

l10n/<yourlocale>: <some message> (<xy>%)

<additional text if needed>

The percentage being the ratio of:

# translated messages from make stats-<yourlocale>
# untranslated messages from make stats-pot

Note that you can now easily get a template for the above by issuing the following command:
make summary-yourlocale

When you're adding a new catalog (make init-...), be sure to set "native" line-endings before committing (svn pset svn:eol-style native trac/locale/.../LC_MESSAGES/....po).

For Developers

Here's a condensed list of a few things useful to know about i18n support when coding:

title attributes
those attributes are collected automatically (i.e. no need for explicit ${_('...')} expressions), but only when the message doesn't contain an expression. In the latter case, they need an explicit ${_('... %(param)s ...', param=...)} wrapping
typographical translation
some languages, like French, have special typographical rules (non breaking space before ":" or ";"), so don't consider that those signs can be left outside of translation scope when part of the text (e.g. _(";") when ";" is used as a separator, _("%(field)s:"))
messages consolidation
when adding new messages, always look if there's not already a very close message, and then reuse it (e.g. we now have 7 occurrences of "Repository '%(repo)s' not found", previously we had 7 variants of that message)

Open Issues

  • help us spot the MissingTranslations!
  • i18n infrastructure for Trac plugins (#7497)
  • translation of wiki pages (#1513) and help pages (TracDev/Proposals/NewHelp)
  • translation of text within Javascript source code
  • failure to start Trac (raw NullTranslations instance has no attribute 'add' error) when no .mo file is available
    Multi-language support in the wiki
    Component field sort order doesn't use locale
    Timeline shows incomplete information about status changes for customized workflow
    Workflow actions not translated
    TicketQuery groups without translation
    Created, Modified and Ticket columns are not translated in SQL reports
    Wrong label on wiki diff view between initial version and version 1
    Error message with untranslated text when removing no selected items

See also:

Note: See TracWiki for help on using the wiki.