-
Notifications
You must be signed in to change notification settings - Fork 711
[css-ruby-1] Proportional or fullwidth parens? #762
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
Agree it should be. |
Ruby is primarily meant for CJK, but it can be used for annotations in any languages, and only CJK uses full width parens. Should the selector be specialized by |
Why don't we default to CJK when the primary use is CJK? |
If we provide a switch, CJK is a finite set of language, while the rest isn't, is its easier to say I don't think it would be too bad if we just applied the styles CJK wants for all languages, and let authors override that if they're using it for something else, but I thought that as the |
I believe that we shouldn't emphasise the idea that ruby markup/styling can be used for non CJ languages, since it's really designed specifically with those in mind (which is why it's called 'ruby' rather than 'glossing' or 'annotation') and it lacks features needed for general glossing. Appendix A however is an odd beast. As i understand it, subsection A.1 is the default style sheet referred to in the heading of App A, but subsections A2 and A3 are really more akin to guides for content authors (not to mention the fact that they don't work for all markup). If i'm right, then it seems to me that it's best to use fullwidth parens for this example and we can leave it to the content author to adapt the code for other languages. (Note that the content author may also choose to use a different type of bracket altogether.) Also, perhaps we should split Appendix A? |
I agree that we shouldn't emphasize usage in non-CJK. Actually I believe ruby is more likely to be used on untagged / mistagged CJK content than any language else. |
Fair enough. |
…tyle sheet from author style sheets. #762
Thanks for the edits. I'm satisfied with this resolution. I'll check that the i18n WG agrees, and unless there's an objection, we'll just close our tracker. |
A.3 Generating Parentheses
https://drafts.csswg.org/css-ruby-1/#default-parens
The CSS code in this section applies ordinary parens '(' and ')' to inline ruby annotations. Shouldn't they be fullwidth parens?
The text was updated successfully, but these errors were encountered: