Closed
Bug 1609585
Opened 6 years ago
Closed 6 years ago
Migrate all possible uses from AppLocalesAsLangTag(s) to AppLocale(s)AsBCP47
Categories
(Core :: Internationalization, task, P2)
Core
Internationalization
Tracking
()
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: zbraniecki, Assigned: zbraniecki)
References
Details
Attachments
(1 file)
Except of physically loading the ja-JP-mac
path from the omni.ja/hard drive, there's no reason to circulate ja-JP-mac
over BCP47-compilant ja-JP-macos
.
Let's unify around it and keep the override just for the chrome:// resource:// where needed.
Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Assignee: nobody → gandalf
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•6 years ago
|
||
I left:
- https://searchfox.org/mozilla-central/source/chrome/nsChromeRegistryChrome.cpp#336
- https://searchfox.org/mozilla-central/source/intl/l10n/L10nRegistry.jsm#625
which should be sufficient to handle ja-JP-mac
as tested locally.
If that lands successfully, I'll wait a couple of releases and remove AsLangTags
, rename AppLocalesAsBCP47
to AppLocales
and make the converter a specific ja-JP-mac
->ja-JP-macos
on input, and keep the two output paths as is.
Assignee | ||
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Priority: -- → P2
Pushed by zbraniecki@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c94bd2834efa
Migrate all possible uses from AppLocalesAsLangTag(s) to AppLocale(s)AsBCP47. r=marionette-reviewers,jfkthame,whimboo
Comment 5•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•