CLDR Ticket #9300(accepted data)
Reduce the number of supported BCP47 variants
|Reported by:||mark||Owned by:||mark|
Description (last modified by mark) (diff)
There are very few BCP47 variants that are in use, and unfortunately the ietf-languages@… has followed a particular strategy that causes a pointless proliferation of variants. So I suggest that we winnow down the variants to a small number that we think are in reasonably widespread use, or have CLDR locales, and archive the rest of the data.
The beauty of languages is that a combination of two words can be used to denote a narrower concept than either one of them alone. We can say "red book", "red apple", "red heart" without having to have multiple words for "red": "redbk book", "redappl apple", "redhrt heart". Unfortunately, the ietf-languages@… has chosen to follow the latter approach is necessary for lstr variants, which is especially silly given that variant subtags are always used in conjunction with a primary language subtag.
Variants like "eastern" and "western" could have been defined: reusable variants with independent meaning, and then used generatively such as *hy-eastern for Eastern Armenian (rather than hy-arevela), but also *yi-eastern for Eastern Yiddish, and many others. Instead, we get single-use terms like hy-arevela and hy-arevmda, which require special translations in CLDR rather than simply "Armenian (Eastern)". (After all, where there is a single term in a language for a combination of subtags, CLDR does support having such translations.)
Given the current ietf-languages@… policies, it does not make sense for us to support non-generative variants, except in limited circumstances outlined above.
- Status changed from new to accepted
- Component changed from unknown to bcp47
- Priority changed from assess to medium
- Milestone changed from UNSCH to 30
- Owner changed from anybody to mark
- Type changed from unknown to data