Closed
Bug 1319829
Opened 8 years ago
Closed 8 years ago
migration module should take locale instead of language code
Categories
(L20n :: Python Library, defect)
L20n
Python Library
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: stas)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Right now, the migration code takes a language code. It's use-case is to get the plural rule categories from cldr, which are defined for some combination of language and region tags.
We should make the conversion between the locale code we have and what cldr knows about inside cldr.py.
We should fix that before we land the migration mach command in bug 1315005.
|
Assignee | |
Comment 1•8 years ago
|
||
Do you think we should run some kind of a language negotiation here, or just hard-code the mapping from codes used at Mozilla to codes known by CLDR?
|
Reporter | |
Comment 2•8 years ago
|
||
I'd fallback in the sense of ja-JP-mac -> ja-JP -> ja. Nothing fancier than that.
I think that's easier than hard-coding 20+ entries.
|
|
Assignee | |
Comment 3•8 years ago
|
||
|
|
Reporter | |
Comment 4•8 years ago
|
||
Comment on attachment 8814464 [details] [review]
Pull request
r=me
Attachment #8814464 -
Flags: review?(l10n) → review+
|
|
Assignee | |
Comment 5•8 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•