Fixed
Details
Details
Priority
Assignee
Steven R. Loomis
Steven R. LoomisReporter
Steven R. Loomis
Steven R. LoomisReviewer
Mark Davis
Mark DavisFix versions
Components
Time tracking
9m logged
Created September 24, 2021 at 7:01 PM
Updated October 11, 2022 at 8:18 PM
Resolved October 13, 2021 at 4:43 PM
Some code/spec/data archeology here…
While working on https://unicode-org.atlassian.net/browse/CLDR-14642#icft=CLDR-14642 (bcp47 for cldr-json) I ran into this issue.
TR35 says that the `<hours regions=…/>` attribute is a list of regions.
However, the data actually has a mismash of regions and locale IDs.
How did we get here?
https://unicode-org.atlassian.net/browse/CLDR-10120#icft=CLDR-10120 updated the DTD metadata to allow region or locale
https://github.com/unicode-org/cldr/commit/5402171414f7af02bb97a2807f83bae2494acf23#diff-0c05fb67bed20d205660988e57e8438014bcde6954263c6f66e1b9fc535e6850R340
https://unicode-org.atlassian.net/browse/CLDR-8959#icft=CLDR-8959 has a comment (and added the initial data)
> Also change spec to allow for locales, which must have an underbar in them, eg fr_CA. (Could extend in future to subregions.)
however the spec was not updated.
This structure will make it challenging for implementations. It might be better to have 'locales=…' instead, or perhaps, to promote all regions to locales, as in `und_TF ca_ES gl_ES`.
At least, the spec should be updated.