(08-11-2014, 04:17 AM)GunChleoc Wrote: (08-10-2014, 05:23 AM)CrystalH Wrote: 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.
We could use boost::format with numbered placeholders in case some RTL languages need to reverse the order: %1$d x %2$d
(08-10-2014, 05:23 AM)CrystalH Wrote: 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.
We could do something like %1$s / %2$s / %3$s so people can reverse it and also shorten it if they run out of screen space. Translations of 1-word strings can easily be 3x as long as the original string, so for the deeper menus, some languages might run into space problems.
....
I know there are a few annoying bits. They are there, due to certain constraints in the gui implementation. Getting rid of them is not trivial, else they would have been fixed already. For larger edits I recommend using a text editor (doesn't have to be poedit), even the most basic ones should have search and replace functionality.
There are 38 title strings of the A / B / C kind. Most of them are of the group Options / Controls / ... They should be a simple copy & paste job, not take more than 5 minutes really.
These strings (page titles, numbers, resolution strings) are not generated by the game. The game gui has no concept of page titles eg, they are simply text labels in the gui skin files.
