New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Definition of Unicode Locale #25
Comments
The need to introduce the extensions may swamp that message, but it's important to note that several specifications (most importantly ECMA-402) have adopted Unicode locale identifiers as a term. It's the rules, not the extensions, that are important in most cases. As usual, you make a good point about the visibility of the text I emphasized above. You have to read all the way past the next definition and the mustard to reach:
... and this still fails to emphasize that most language tags are good enough without extensions. The extensions exist to provide finer tailoring if and only if the user needs it. Perhaps split this bit of text off the second paragraph quoted above to emphasize it?
I think we could then clear up the confusion by adding one more mustard item with explanation:
|
- Added material adapted from my comment to @r12a about the historical link between language tags and locales.
https://w3c.github.io/ltli/#ref-for-dfn-unicode-locale-1
This appears to me to say that language tags without -u or -t extensions are not Unicode Locale identifiers, and therefore not suitable for locale identification. It then goes on to say that
and
Which to me implies that any time anyone uses a language tag, it should include -u and/or -t tags. Which doesn't sound right.
It seems to me that the definition is problematic, and could be changed to say one of the following (i'm being deliberately open here to possibilities):
Whichever is chosen, i think the mustard needs to be crafted way that is a little more subtle.
Btw, it may be useful to briefly expand on "the additional processing rules defined by [CLDR] in UTR#35 [LDML]."
The text was updated successfully, but these errors were encountered: