-
Notifications
You must be signed in to change notification settings - Fork 709
[css-ruby] Adjacent overhanging ruby text should not run together in scripts with spaces between words (e.g. Latin) #3498
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
The current level of spec doesn't have any normative requirement to overhanging, so maybe there's no much we can do for this case in the spec. It's probably more a implementation quality issue at this moment. Note that JLReq does mention that it is not recommended to have overhanging ruby to become consecutive even in Japanese, and in that case, it's generally recommended to add a space in-between. (See the note around Fig. 3.81) |
This is a very interesting problem, and the recently introduced ruby-overhang property does not solve it: even if you use ruby-overhang:none, if you're annotating in latin (or something that uses spaces) over Japanese (or something that doesn't use spaces), the words can run into each other and make an unreadable mess. It seems that maybe some extra value ( |
For Level 1, do we want to allow the UA to do something automatic, similar to how we handle ruby overhang and line-edge alignment?
|
It might be nice for users to control the minimum distance; I’m worried that separating two rubies by only a single U+0020 space would be too small of a distance for technical documents in Latin script, though it’s much better than nothing. |
Related text in clreq:
|
Should there always be a visible space between adjacent ruby text in Latin (or other scripts with spaces between words)? Since ruby text is often longer than its base, overhang can prevent awkward gaps in a sentence; however, overhang is not strictly necessary for ruby text to run together.
In the example in this JSFiddle, overhang is desired (ideally the comma should abut the previous word), but the annotations should not abut because they are two different words/belong to two different bases:
Chrome 71/Mac
Firefox 64/Mac
The text was updated successfully, but these errors were encountered: