Using PO files for translations

[scootergrisen]

trafficstars

I suggest using PO files for the translations.

[Chrysostomus]

Seems like a lot of work to change transportation format, but I'm open to the idea. Could you describe the benefits of using PO files?

[scootergrisen]

If its a PO file you can use lots of translation software to translate it in a smarter way. Like Virtaal (http://virtaal.translatehouse.org/). The software can check for errors and stuff like that. And when a translator needs to update the translation you can supply a pot file that the translator can use to update the po file.

Then you would not need stuff like " # translate me !". I think if the translation is empty it is considered untranslated by the translation software. And if you change a string it can be marked with "fuzzy" so translators can see something have changed.

In the header of the po file you can have language codes etc. Files can be called "da.po", "en.po" etc. I don't know how to make a software use po files i just think its smart and makes it attractive for translators to translate because its a format they might already know and they can use the software they use to translate other stuff.

[Chrysostomus]

That seems to have some merit. Found this on how to use PO files:

http://www.pclinuxos.com/forum/index.php?topic=59145.0

In terms of code it would be

• easier to see exact messages right in the code
• more difficult to read the actual code, because translation strings would be much longer
• easier to add translatable strings
• much work to change every transation string in the code.

I'm not sure about if this would attract or alienate more translators. On one hand it would surely be easier for professional software translators, on the other hand it would seriously raise the bar for those contributors who lack such skills.

I think this is one of those features that might be added after 1.0 release