Philippe Normand wrote:
*snip*
I wrote a little script to ease .po files generation, as they are
widespread in the plugins. This script takes 3 arguments:
- the operation you want to do on the translation: init or update
- your email
- the 3-letters code corresponding to your locale
You can find the script in data/translate_mgmt.py. Example:
$ python data/translate_mgmt.py init [EMAIL PROTECTED] cat
To start the catalan translation of Elisa :) Paths to po files are
printed, you just only need to edit these files with a po editor or a
standard editor and send us the po files (ideally attached to a new
ticket in trac)
Don't forget to change po files encoding from ASCII to UTF-8 if needed
by your language.
Hi,
I'm glad to see that Elisa is getting i18n support again. Have you guys
considered using Babel[1] instead of "just" the stock gettext module? I
might be a bit biased but I think it provides a few interesting
advantages:
* Not only for message translation. Babel gives access to most of the
CLDR[2] locale data database. This include things like
date/number/currency formatting, locale specific names for currencies,
countries, languages etc.
* A pure python implementation. Does not require GNU gettext for
message
extraction or catalog compilation. Which is usually not available on
non-linux platforms.
* gettext compatible api.
* Supports message extraction from python, genshi and glade by default
but more formats can be added easily using plugins.
[1]: http://babel.edgewall.org/
[2]: http://unicode.org/cldr/
Btw, why are you using a 3-letter language code instead of the more
common
language_TERRITORY? Will this not make it impossible to have different
translations for for example UK and American English (en_UK, en_US)?
Cheers,
Jonas
