cldr-json should use bcp47 for filenames (en_US_POSIX)
Description
blocks
is blocked by
relates to
Activity
Show:
Steven R. Loomis October 20, 2021 at 9:20 PM
I don’t think we need to omit POSIX from data, the rule I followed was: exclude locale(s) which require variants for their filename which would only be en-US-u-va-posix
(there’s a command line switch for this)
Shane Carr October 20, 2021 at 3:28 PM
Doing a textual search in the CLDR JSON release, I find the POSIX variant in cldr-localenames, such as:
"PINYIN": "i-Pinyin Romanization",
"POLYTON": "i-Polytonic",
"POSIX": "Ikhompyutha",
"PROVENC": "i-PROVENC",
"PUTER": "i-PUTER",
Meanwhile, en has the following data but not any other languages:
"va": {
"posix": "POSIX Compliant Locale"
}
Probably okay but just pointing it out.
Shane Carr October 19, 2021 at 12:25 AM
I will review this when I pull CLDR 40 JSON into ICU4X, which is tracked by https://github.com/unicode-org/icu4x/issues/1187
Steven R. Loomis September 29, 2021 at 4:22 PM
Need pr review of https://github.com/unicode-org/cldr/pull/1506
Kip Cole September 22, 2021 at 3:55 PM
grammaticalFeatures.json
currently generates a root
locale rather than the BCP47 und
locale name. I believe this is also expected to be BCP47?
Fixed
Details
Priority
mediumAssignee
Steven R. LoomisSteven R. LoomisReporter
Steven R. LoomisSteven R. LoomisReviewer
Shane CarrShane CarrFix versions
Components
Time tracking
6h logged
Details
Details
Priority
Assignee
Steven R. Loomis
Steven R. LoomisReporter
Steven R. Loomis
Steven R. LoomisReviewer
Shane Carr
Shane CarrFix versions
Components
Time tracking
6h logged
Created April 5, 2021 at 5:41 PM
Updated October 11, 2022 at 8:19 PM
Resolved October 20, 2021 at 9:22 PM
Related to the discussion around https://unicode-org.atlassian.net/browse/CLDR-14487#icft=CLDR-14487:
cldr-json outputs for example:
`cldr-json/cldr-dates-full/main/ca-ES-VALENCIA`
`cldr-json/cldr-dates-full/main/en-US-POSIX`
Valencia is OK because it's a registered bcp47 variant, however en-US-POSIX is problematic here. Perhaps it should be `en-US-u-va-posix`, but see discussion at the linked issue.