Right.
Yeah I'm translating and it's going well. I can translate, download .po save it to .mo in PoEdit and check in game. Which is cool.
What is different for me is that it's the translators job to do that. But otoh, is quicker to check in game. Still if you had e.g. 10 languages (updated frequently) I think some trigger (or script) to download all .po files from transifex (is that possible ?), make all .mo and put into game would be faster.
Next stuff, from my (programmer's) point of view: I think some translations are just redundant. Mostly what I already mentioned.
But I really see no point in having all the numbers translated. What for ? Chinese traditional or are there other languages that don't have the digits ? Digits seem to be present on such websites anyway. So single game numbers like 1..12,16,32 etc.
Also resolution. Why is it translated at all ? You don't eg. have 1024 x 600 or other weird ones.
http://en.wikipedia.org/wiki/Display_resolution
It's pointless to add all of them to translations. IMO just in code, read the height and width numbers and format to strings, that's all.
And same goes for 'Options / Controls / Button / Edit' like strings, I'm ok for translating Options, Controls etc. But not for translating every combination of them too. So IMO, just replace all single strings with translations in code and combine with /.
If I e.g. wanted to change 'Controls' translation I now have to update it in 12 strings.
Given all that, I think about 80 or more translations would be not needed.
Lastly, I'm not familiar with it but why is the .mo file needed. Isn't .po sufficient ? I know it's bigger but seems like an unnecessary step to always convert it.
Next, why is codepage needed ? Isn't that some stupidity that came with the Windows disease, ekhm I mean OS. Utf-8 everywhere, IMO the only solution.
Sorry for so much text. I guess it's mostly relevant for new languages.
