create localization roadmap

[plata]

Create a roadmap for the localization of Phoenicis. This includes:

• this application
• scripts (see PlayOnLinux/Scripts#49)
• website? (see #557)

For the Phoenicis application:

• decide how to do localization with Java(FX) (e.g. this tutorial, or with GNU gettext)
• decide where to store the localization files in a way that people can provide localization files in an easy way
  • Transifex (nice but expensive)
  • Weblate (free, integrates with git/GitHub)
  • Pootle
  • Rosetta (as in #4; often slow and buggy)

[plata]

I'm currently looking at gettext commons which looks promising. However, I could not get it running yet.

[madoar]

What problems did you meet? I would like a solution for this, that can be updates via the web. This would enable us to update the language files more often that the software itself, which would make sense when we fix some typos or want to add new languages

[plata]

With the explanations from the gettext commons wiki, it's quite easy to add the Maven dependencies. Running mvn gettext:gettext will then give you a pot file with the extracted keys. I don't currently understand how to generate po files per language (if that can be done with Maven as well or not etc.) and how the generated classes/properties should be accessed from Java.

[plata]

Here are some other tutorials: http://blogs.igalia.com/dpino/2009/08/30/setting-up-gettext-commons-for-i18n-java-files/ http://blogs.igalia.com/dpino/2009/09/05/using-gettext-commons-from-java-files/

[plata]

Ok. Getting closer:

• use msginit to create a po (msginit -i keys.pot -o de.po)
• call mvn gettext:merge
• call mvn gettext:dist (this creates a Messages_de.properties)

[plata]

see #822

[plata]

Translations are working. Translation service to be handled in #898.