-
Notifications
You must be signed in to change notification settings - Fork 715
[css-ruby] Incorrect language tags in the source file? #3292
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
Comments
Yeah... I see no reason why they need to be marked that way. |
They are not really English, though. Strictly speaking they are romanization of words in those languages. Not sure how they should be marked. |
You could use |
(For the first one, at least. I didn't look up in http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry what script names to use in the other languages.) |
I believe |
I think this is one of the scenarios where language tagging is not clear-cut, and very much falls back on the question: "What effect are you hoping to achieve by tagging for language?" (Or, actually, here perhaps what effect do you not want to produce?) Here's my 2p: If you label these terms as described above you'll find that the browser applies different CJK fonts to the text unless overridden by styling (not the case here), which to me looks quite odd because they aren't usually written that way in the native language either. For myself, i see these as technical terms used in English that happen to be derived from CJK terms. I wouldn't put any language tag on them, because: |
Arguably, UAs ought to be responding to the full language tag, including the writing-system, and not switch to Chinese if it sees So I agree with @r12a: these are better seen technical terms used in English that happen to be derived from CJK terms, best left without a language tag. |
In the glossary of css-ruby, the terms are marked as
lang="zh/ko/ja"
, although they're written in English.Source file:
csswg-drafts/css-ruby-1/Overview.bs
Lines 1487 to 1529 in c5115ea
The text was updated successfully, but these errors were encountered: