Quote:
Originally Posted by eureka
.properties for locale identification could be generated automatically. Locale code (i.e. locale and locales.supported) could be extracted from localized resource file name and locale's name (i.e. display.name) could be extracted from mapping "locale code -> locale name" which is certainly located somewhere in Internets (and should be small enough for storing it in Git repo). UPD: found it. Common Locale Data Repository (or direct link to right file: http://unicode.org/Public/cldr/2.0.1/core.zip). Whole file content is too big, information could be extracted from 'common/main/en.xml'. |
It's not as easy as that, because there are some quirks with the Kindle. In fact, the KT is extremely picky about those .properties. Nearly everything that I assumed should work did not actually work... and that was only while editing that one file. Here's the usual output if it's not happy with something:
Code:
120117:222533 blanket[1140]: E langpicker:GET_LOCALE_POSIX_ID_FAILED:locale=de:getLocalePosixId() called on a locale ID that isn't installed on the system
120117:222533 blanket[1140]: E langpicker:LOCALE_NOT_INSTALLED:locale=(null):changeLocale to non-installed locale-- locale not changed
... at least, it doesn't crash and burn, but silently stays at en_US
In the last hours, I have thought of a different way, namely of having a special resource on transifex which will allow translators to provide the necessary information. I have temporarily uploaded it (but locked it for translation after making a sample one).
As translators are probably not following this thread closely, and don't need to understand all details, I'll just confront you with my idea:
https://www.transifex.net/projects/p.../l/ru_RU/view/
This is essentially what you'd get to see as a translator. A "completed" sample is here:
https://www.transifex.net/projects/p...ORE/l/de/view/
Do you think that this makes sense to translators, or is it too confusing? From these files, individual .properties could be extracted.