This is a spin-off from bug 1353337 comment 9. Once bug 1348042 lands, Gecko's LocaleService will be able to operate in client/server architecture. In case of Fennec, Gecko should always be in the client mode, and Fennec needs to provide some equivalent of the LocaleService in the Java code. I'm working on the Gecko side to provide the correct APIs and behavior, and need someone to write the Fennec side. The service should: - collect available locales from: - java resources - Gecko's ChromeRegistry - Gecko's L10nRegistry (bug 1333980) - get user requested locales - negotiate between those two lists - feed Gecko's LocaleService with the correct list of locales via SetAppLocales - react to changes in the requested locales or in L10nRegistry locales (DLC) by renegotiating locale list and updating Gecko's LocaleService with the new locales The behavior and API will probably be very similar to http://searchfox.org/mozilla-central/source/intl/locale/LocaleService.cpp although probably simplified at least initially. I'd recommend porting the language matching algorithm as we put a lot of work to design it for our needs and it would be safer to maintain the same negotiation strategy between Gecko and Fennec.
See Also: → bug 1360596
You need to log in before you can comment on or make changes to this bug.