Closed
Bug 1349377
Opened 9 years ago
Closed 6 years ago
Consider exposing locale ID parsing code in LocaleService
Categories
(Core :: Internationalization, enhancement, P3)
Core
Internationalization
Tracking
()
RESOLVED
FIXED
People
(Reporter: zbraniecki, Unassigned)
References
(Blocks 1 open bug)
Details
We have an internal class Locale in LocaleService that allows us to chunkify locale/language ID into components.
There's client side code in Firefox that tries to, for example, just take the language part and verify if it's "ja".
We could either expose the Locale, or we could expose some function like:
let locale = LocaleService::ParseLocaleID("en-Latn-US");
locale.language = "en";
locale.script = "Latn";
locale.region = "US";
locale.variant = undefined;
Not a high priority, but would be nice to tackle when we have time.
Updated•9 years ago
|
Priority: -- → P3
| Reporter | ||
Comment 1•8 years ago
|
||
Bug 1428698 implements that for C++ code, bug 1433303 will do the same for JS.
| Reporter | ||
Comment 2•6 years ago
|
||
Intl.Locale is now exposed!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•