As you can see on http://colincooper.net/?p=238, android is using two odd locale codes in their scheme, 'iw' instead of 'he', and 'in' instead of 'id'. We need to map our locale codes with special case for this, http://hg.mozilla.org/projects/birch/file/f069ffc41471/embedding/android/Makefile.in#l173 should be the right spot. Tested that that works with my AllLocales dummy app from https://github.com/Pike/android-l10n.
assigned to email@example.com. Not really sure how to fix this.
At least half of this is in bug 702302 now. Not sure if we need some tweaks to matchOS logic, notably: if you set the OS language to hebrew or indonesian, and that sends the java locale codes to nsPosixLocale.cpp, map them to the gecko versions, probably in that file.
My tests show that hebrew isn't picked up in the multi-locale build so far. Need to investigate further.
Axel, since we are working on 'he' folder for localization and not 'iw', should it make any change in our current workflow?
LANG: iw_IL shows my debugging in http://mxr.mozilla.org/mozilla-central/source/intl/locale/src/nsLocaleService.cpp#167. Simon, any recommendation on where we should make iw -> he again? Same for in->id. In nsLocaleService, or in nsPosixLocale? (And no, the mapping is done on build time now)
I think in nsLocaleService. What about other deprecated language codes? From the IANA registry, there are also ji->yi jw->jv mo->ro and a bunch of deprecated three-letter codes. <rant> It's so annoying that we have to deal with this: in and iw were deprecated in *1989*, probably before the majority of users of Android devices were even born. </rant>
http://colincooper.net/?p=238 claims that only Yiddish is affected, too. Blames java for that, and whatever I find on the web isn't really authoritative but also only mentions the three of he, id, ji.
Pike, what needs to be done here?
Pike, of this needs to track a given release, please renom and say which one
Not gonna work on this any time soon, unassigning.
Comment 6 seems to be the remaining work item here.