This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
Error behaviour not defined for Add Likely Subtags algorithm #42
Comments
|
Let's discuss this in the Intl meeting; maybe we will choose between one of these three options. |
The ICU function could return a warning (that it was not able to find a match) , probably changing to file a bug and link it here? |
littledan
added a commit
that referenced
this issue
Jul 14, 2018
When Intl.Locale.prototype.maximize() and minimize() are called on locales which don't appear in CLDR's database of known locales with likely subtags, the semantics were previously unclear. With this patch, a new, identical Locale object is returned. These semantics encode the conclusion of the discussion in the June 2018 Intl meeting. Closes #42
littledan
added a commit
that referenced
this issue
Jul 28, 2018
When Intl.Locale.prototype.maximize() and minimize() are called on locales which don't appear in CLDR's database of known locales with likely subtags, the semantics were previously unclear. With this patch, a new, identical Locale object is returned. These semantics encode the conclusion of the discussion in the June 2018 Intl meeting. Closes #42
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://www.unicode.org/reports/tr35/#Likely_Subtags has under step 3:
FWIW ICU's
uloc_addLikelySubtagsseems to perform neither of the two options from above, instead it returns the input language tag.The text was updated successfully, but these errors were encountered: