Create a translatable properties file (messageBundle)

[Kristian K]

i18n process is introduced on http://docs.oracle.com/javase/tutorial/i18n/index.html

Basically all strings should be made into functions that fetches localized strings from a translated messageBundle.properties file.

This task can be considered ready when there is a properties file for the current language of the program (english) and the program loads the strings from it.

[Andrjus Frantskjavitsius]

Done!

https://bitbucket.org/andrjus/minoritytranslate/src/master/src/main/resources/messages_en.properties

Definetly not a 15min job!

[Andrjus Frantskjavitsius]

https://bitbucket.org/andrjus/minoritytranslate/src/master/src/main/resources/messages_en.properties

[Federico Leva]

You also need a qqq file with message documentation or this is not really translatable. https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation

[Kristian K]

TranslateWiki needs also a qqq-file

[Kristian K]

As a short summary: 'qqq' is a nonce languagecode used to convey application private messages. We need to make a "translation" of the "messages_en.properties" file into "messages_qqq.properties" where the "translated" strings tells the translators at TranslateWiki.net (or any other translation program) about the context where the string is shown. For example which string is shown as the title and so on.

[Andrjus Frantskjavitsius]

Updated the qqq file. Tell me if there are problems with it.

[Nikerabbit]

Translatewiki.net will exports translations in unescaped UTF-8 encoding. Can your code read those? I think you need to add few lines extra code as by default Java excepts properties files to be ASCII.

[Andrjus Frantskjavitsius]

It seems I need to manually read UTF-8. http://stackoverflow.com/questions/4659929/how-to-use-utf-8-in-resource-properties-with-resourcebundle

[Andrjus Frantskjavitsius]

Should be UTF-8 now!

[Andrjus Frantskjavitsius]

@keeleleek Can I resolve this?

[Andrjus Frantskjavitsius]

Resolved!