Easier tool for managing translations

[GoogleCodeExporter]

We should start looking at some tool to use for managing the translation 
efforts. 

Preferably, translators should be able to work in a user-friendly UI that 
should allow them to view what strings are translated and which are not. 
Translators should not have to work in the raw resource files to translate the 
game, since the resource files also contain the stats for monsters and items 
(which potentially could make the stats differ depending on the localization of 
the game).

One suggestion so far has been http://crowdin.net/ , and there may be other 
tool available. We should investigate what options we have.

Original issue reported on code.google.com by oskar.wi...@gmail.com on 15 May 2011 at 8:23

[GoogleCodeExporter]

Why not use the online editor ?

Make a new grouping "Translate".
Have the main section separated into two columns, one original (English) and 
one to translate. Original column has a read-only input field with the text to 
translate and the other column has the translated text, or empty if no earlier 
translation exist.

Filtering options to show text groups (items, dialog, strings etc) and a 
dropdown with available languages will be needed. If "new language" option is 
selected two input field is shown to input the full and short language names.
A field to input translators name(s) should always be visible.

Original comment by kims...@gmail.com on 15 May 2011 at 9:42

[GoogleCodeExporter]

Another way to do it is to put all translatable strings in the strings.xml file 
and use the good old gettext way to manage all translations (as used in many 
open source projects).

There is a tool to convert android strings.xml file to po file and back.
https://github.com/miracle2k/android2po

And once you have po files, there are many ways to edit them: 
launchpad/rosetta, transifex, poedit, ...

The first step is probably to extract translatable strings from the different 
resource files into one central file.

Original comment by oli.sa...@gmail.com on 16 May 2011 at 10:51

[GoogleCodeExporter]

re comment 2: That's a great idea! Keeping it more standardised is a good 
thing, less code for us to write and maintain. It would still mean quite a big 
change to the resource files, but I guess that would be for the better.

I think this is the best suggestion of a way forward with the translation 
efforts. We should look into this for a future release.

Original comment by oskar.wi...@gmail.com on 16 May 2011 at 6:31

[GoogleCodeExporter]

We should also separate item stats and conversation logic from the translation 
files.

Original comment by SamuelPl...@gmail.com on 21 Jul 2011 at 8:45