map he->iw and id->in in nsLocaleService
Categories
(Firefox for Android Graveyard :: Locale switching and selection, defect, P2)
Tracking
(blocking-fennec1.0 -, fennec-)
People
(Reporter: Pike, Unassigned)
References
()
Details
Updated•14 years ago
|
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Reporter | ||
Comment 3•14 years ago
|
||
Comment 4•14 years ago
|
||
Reporter | ||
Comment 5•14 years ago
|
||
Comment 6•14 years ago
|
||
Reporter | ||
Comment 7•14 years ago
|
||
Updated•14 years ago
|
Updated•13 years ago
|
Updated•13 years ago
|
Updated•13 years ago
|
Updated•13 years ago
|
Comment 9•13 years ago
|
||
Reporter | ||
Comment 10•11 years ago
|
||
Updated•11 years ago
|
Updated•11 years ago
|
Updated•11 years ago
|
Comment 11•11 years ago
|
||
Comment 12•6 years ago
|
||
can we close it now? We don't have nsILocaleService, Android migrated to BCP47 and it seems like we haven't hear about any issues around it in a long time.
Reporter | ||
Comment 13•6 years ago
|
||
I'm resolving this, there's a few caveats though:
Android is far from BCP47. There's some junk they do with script tags in resources, but that's not BCP47 either. They just namedrop that. IIRC, the non-standard language codes are actually java related (and no idea if kotlin exposes that).
For Fennec, we've got work-arounds in the build and in the gecko-java wrappers. For geckoview, I honestly don't know. I didn't find anything in mobile/android/geckoview, but there's some in telemetry in a-c. I just don't know where to look. We'll need to test and find bugs in Fenix once we start localizing that.
Comment 14•6 years ago
|
||
That sounds reasonable! Let's handle that in Intl::Core for LocaleService once we start investigating. I'd also prefer to keep the platform specific quirks per-platform, so I hope that some equivalent of gecko-java wrappers will handle those outliers.
Updated•5 years ago
|
Description
•