-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Using qualified language names instead of language code #1631
Comments
Yes, all true. In fact I thought I had an issue for tracking this but I don't see it. I suppose this comment is what I was thinking of. The next step is probably to figure out if changing document.language to a region qualified language identifier by default is going to be a breaking change. |
Breaking for the user? No, it shouldn't. |
I'd love for you to be right here, but I'm having trouble visualizing it. Using fully qualified names like |
By the way, that would be
But we don't necessarily have to upgrade documents, In most cases, the 2-letter code is the canonical form of the "main language", e.g. In other terms, it seems to me that the crux of the matter is not to enforce fully qualified names (you wouldn't want to enforce the use of the very qualified but cumbersome There are only a few cases where the non-qualified name is ambiguous ( Or did I misunderstand your question? |
Most of the code (and the manual also states it) assumes
document.language
is an ISO 639 language code (e.g.fr
,en
...). There are a number of cases where this is not sufficient for actual typography.fluent
and friends)This also indirectly relates to #1367 and #1157.
Near duplicate of #1368.
The text was updated successfully, but these errors were encountered: