Quote:
Originally Posted by Ackis
I've had to deal with localizations in the past... can you elaborate on what you mean by the amount of work to support them? Do you mean internat to CC, or getting a system to allow people to submit translations?
|
All of the above.
In CC we need to be sure that a) all translatable strings are in resources, b) all implicit word position and orders are made explicit, c) All singular and plural items are separated, especially when the English word is uncountable (e.g., series), d) that we do the same thing for words like "read" that in English are both present and past tense, and e) that the context of a string can be determined somehow. I am leaving aside the issue of RtL languages, as I have no idea what attempting one of those would entail. This will be an iterative process as we discover things we didn't do properly.
Next we need a tool that supports android string XML files and where people can do translations with a minimum of fuss. Perhaps something like Akuna or OneSky. We would need to set up the tool and set up the privilege system.
We need a way to test/verify the translations. I don't think it would happen, but it is very possible for a translator to drop "easter eggs" into the string, perhaps malicious, perhaps simply amusing.
Finally, and perhaps the most difficult, we need a way for translators to see their work in CC itself. This has to be a relatively quick process, but it must also be secure from our point of view. We can't construct unlicensed APK files or the pirates will have a field day, and we can't open our source for the same reason.