wiki:TracPluginTranslation

Version 6 (modified by hasienda, 21 months ago) (diff)

reduce size of Transifex logo used here

Trac plugin l10n project

Trac 0.12 was the first release providing Trac with message texts for various languages. Meanwhile current stable Trac 1.0 has been release, and even translations for TracIni options are possible by now:

Top translations: Trac » trunk

http://www.transifex.net/projects/p/trac/resource/1_0-stable-messages-pot/chart/image_png http://www.transifex.net/projects/p/trac/resource/1_0-stable-messages-js-pot/chart/image_png http://www.transifex.net/projects/p/trac/resource/1_0-stable-tracini-pot/chart/image_png

Charts kindly provided by https://ds0k0en9abmn1.cloudfront.net/static/charts/images/tx-logo-micro.646b0065fce6.png, based on the content of the catalogs uploaded there, which should correspond to the content of the catalogs in the repository.

Why

Translating plugin message texts as well is a somewhat logical consequence of Trac going the i18n/l10n way. But this is a big challenge for a Trac plugin maintainer. He/she might be able to

  1. internationalize the messages inside the plugin code (i18n) and even
  2. translations into message catalogs

for one or two language - that's all, at least in the common case.

Now, Trac supports much more languages. What to do? So here we go...

Who

'We', this is a team of volunteers using Transifex as part of our workflow. Coming from different places our work is dedicated to localization of Trac plugins. And you're welcome to join us. It doesn't matter, if you're a skilled translator or l10n newbie. Once registered with Transifex you've the chance to contribute to translations of lots of projects. The Trac plugin l10n project is just one of them.

What

There is a twofold offer: for maintainers of Trac plugins as well as for translators including Trac users in general that are willing to contribute.

Internationalization (I18N)

We'll support i18n efforts as well as do it on our own. If you're about to start on your own, fine. However this might still be a hard job, especially at the first try. Please have a look at the l10n cookbook page for Trac plugins.

We'd like to help with i18n issues, if requested and as much as our spare time permits. You could ask here, or write me directly.

Localization (L10N)

We'll pick existing message catalogs on our own. But maintainers are free to participate actively by sending in

  • current POT files for translation as well as
  • existing PO files for central distribution and review at Transifex.

To provide a uniform way for contributions to a bunch of Trac plugins there is a special Transifex project backed by a dedicated Mercurial repository at Bitbucket.org.

For announcing i18n capability as well as available translations and way to contribute via this project at Transifex please consider adding a dedicated i18n/l10n section to the plugin's wiki page. Consider SubticketsPlugin's page as a good and re-usable example.

A word of caution

It's not only a matter of quantity but quality as well. Good translations do respect a number of rules especially when it comes to Trac terms. These are part of agreements per language, and a agreements may be subject of discussion. A bunch of Trac tickets is dedicated to http://trac.edgewall.org/wiki/TracL10N#Translationcoordination translation coordination].

Additionally Trac plugin maintainers might provide their own hints like richard did for his TracTicketTemplatePlugin. See the translator section of the l10n cookbook page for Trac plugins for more details. And look at existing coordination pages for an number of languages here as well as other pages around the official Trac L10N wiki page.

Discussion

[add your questions here]