Closed
Bug 854042
Opened 12 years ago
Closed 6 years ago
Import IANA Language Subtag Registry
Categories
(Core :: JavaScript: Internationalization API, defect)
Core
JavaScript: Internationalization API
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mozillabugs, Unassigned)
References
Details
(Whiteboard: [bcp47])
Bug 769872 added data derived from the IANA Language Subtag Registry (http://www.iana.org/assignments/language-subtag-registry) to the implementation of the ECMAScript Internationalization API. As noted in bug 769872 comment 110, the registry file itself should be included in the Mozilla sources.
Comment 1•12 years ago
|
||
I don't know what this entails for the Intl implementation specifically, but keep in mind the existence of bug 356038, bug 666662, and bug 716321.
Also, there are a number of resources for parsing the Registry available here:
https://github.com/GPHemsley/BCP47
Whiteboard: [bcp47]
Reporter | ||
Comment 2•12 years ago
|
||
Gordon, this bug is just about adding the language subtag registry itself - the script extracting the data from it that the ECMAScript internationalization API needs, and the extracted data itself, have already landed:
https://hg.mozilla.org/mozilla-central/rev/095782b51013
The bugs you mention seem to be about extracting subtag lists for localization; I needed mapping tables between obsolete and preferred tags, so there didn't seem to be much overlap.
Comment 3•12 years ago
|
||
(In reply to Norbert Lindenberg from comment #2)
> Gordon, this bug is just about adding the language subtag registry itself -
> the script extracting the data from it that the ECMAScript
> internationalization API needs, and the extracted data itself, have already
> landed:
> https://hg.mozilla.org/mozilla-central/rev/095782b51013
Ah, right.
> The bugs you mention seem to be about extracting subtag lists for
> localization; I needed mapping tables between obsolete and preferred tags,
> so there didn't seem to be much overlap.
Well, yes, the lists will ultimately be localized in order to be displayed in the UI, but I do think that there should only be one centralized list of the full contents of the Registry. (The localization discussion was such that the full list would be pared down so as to not overburden the localizers with uncommonly-used language/etc. names. In an ideal world, such difference between the lists would not exist.)
It's still unclear to me what the importation of the Registry would entail, as the commit you linked to seems to already handle the mapping between obsolete and preferred tags. What else will the Registry be used for?
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Gordon P. Hemsley [:gphemsley] from comment #3)
> It's still unclear to me what the importation of the Registry would entail,
> as the commit you linked to seems to already handle the mapping between
> obsolete and preferred tags. What else will the Registry be used for?
See https://bugzilla.mozilla.org/show_bug.cgi?id=769872#c110
Comment 5•12 years ago
|
||
(In reply to Norbert Lindenberg from comment #4)
> (In reply to Gordon P. Hemsley [:gphemsley] from comment #3)
> > It's still unclear to me what the importation of the Registry would entail,
> > as the commit you linked to seems to already handle the mapping between
> > obsolete and preferred tags. What else will the Registry be used for?
>
> See https://bugzilla.mozilla.org/show_bug.cgi?id=769872#c110
So, it's just the text file that would be imported? Is that text file simply an unadulterated copy of the Registry at the time?
Reporter | ||
Comment 6•12 years ago
|
||
(In reply to Gordon P. Hemsley [:gphemsley] from comment #5)
> So, it's just the text file that would be imported? Is that text file simply
> an unadulterated copy of the Registry at the time?
Yes.
Comment 7•12 years ago
|
||
(In reply to Norbert Lindenberg from comment #6)
> (In reply to Gordon P. Hemsley [:gphemsley] from comment #5)
> > So, it's just the text file that would be imported? Is that text file simply
> > an unadulterated copy of the Registry at the time?
>
> Yes.
I don't know why I thought this was much more complex than it is. Thanks for putting up with my incessant questions.
Assignee | ||
Updated•11 years ago
|
Assignee: general → nobody
Comment 9•8 years ago
|
||
(In reply to Zibi Braniecki [:gandalf][:zibi] from comment #8)
> Andre, I think this is fixed now, right?
No, I don't think so. IIUC this bug is about checking the language-subtag-registry.txt file itself into the source tree, so if we ever need to regenerate the data, we don't need to download it again from https://www.iana.org/assignments/language-subtag-registry.
Flags: needinfo?(andrebargull)
Updated•7 years ago
|
Component: JavaScript Engine → JavaScript: Internationalization API
Comment 10•6 years ago
|
||
Obsoleted by bug 1522070.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•