On 23 October 2010 21:32, Maarten Dammers <maarten@mdammers.nl> wrote:

1. Gettext: http://en.wikipedia.org/wiki/GNU_gettext

I have very bad experiences with gettext in python. I forgot what the issues were exactly, but I know it was annoying enough not to use it. I think it had something to do with actually switching languages, but I'm not 100% sure.

2. Big python dictionary: Easy to implement in pywikipedia but isn't
really a standard so translatewiki needs to be modified. You can see a
test in r8684

OK as far as I am concerned, but if TW does not support it, probably not the best option.

3. Properties files: http://en.wikipedia.org/wiki/.properties
4. YAML : http://en.wikipedia.org/wiki/YAML .

These two are equal as far as I am concerned. I have more experience with YAML than with properties-based stuff, but I think for translations the only difference is the usage of : (YAML) instead of = (properties).

The big advantage of getting TW to export into the currently used format is obvious: it requires less changes at our end. However, in the long run, it would make sense to split off translations from the scripts and import them. The format we use at that point is pretty much irrelevant, as there will be some intermediate layer to read the translations.

Best regards,

Merlijn