This sounds like a great idea; 'Work smarter, not harder'. Perhaps we could set-up a test using a couple of non-English languages.
Chris. On 13 May 2010 16:46, "Guillaume Rosaire" <[email protected]> wrote: Hi, I've just had a look at android2po (http://github.com/miracle2k/android2po) which helps converting android translations (values-XX/strings.xml) to and from gettext .po files. That way, we could have these .po templates imported into launchpad and all the translation part done directly on the web with launchpad by any contributor. What that would change: No more manual updating of the language specific strings.xml except for the main English one (values/strings.xml) At the moment, I'm not sure what would happen of the current untranslated keys in the language specific files for which we rely on the default English one. e.g: <string name="app_name">OpenSatNav</string> <string name="bug_report_mail_address">[email protected] </string> <string name="about_website_label">OpenSatNav.org</string> <string name="about_website_url">http://www.opensatnav.org/</string> etc... I guess we would have an entry in each po template that would need to be copied from the english one by each translator. android2po generates also a language specific file for arrays.xml but I guess we can just import it to keep OSN as it is now (only one arrays.xml in values/). _______________________________________________ Osn-dev mailing list [email protected] https://lists.kentgeek.org/mailman/listinfo/osn-dev
_______________________________________________ Osn-dev mailing list [email protected] https://lists.kentgeek.org/mailman/listinfo/osn-dev
