Skip to content
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

[simple-ruby] 1-1-3 annotations in jukugo ruby #4

Closed
r12a opened this issue Feb 13, 2019 · 5 comments · Fixed by w3c/jlreq#207
Closed

[simple-ruby] 1-1-3 annotations in jukugo ruby #4

r12a opened this issue Feb 13, 2019 · 5 comments · Fixed by w3c/jlreq#207

Comments

@r12a
Copy link
Contributor

r12a commented Feb 13, 2019

3.4 Placement of Jukugo-ruby (bullet 2)
https://w3c.github.io/jlreq/docs/simple-ruby/#placement-of-jukugo-ruby-0

If even a single ruby string is longer than its corresponding base character when laid out without inter-letter spacing, the processing is identical to group-ruby (see Figure 17 and Figure 18).

What about when you have 3 base kanji with hiragana annotations of 1, 1, and 3 characters, respectively? In jlreq is shows a gap between the first hiragana character and the others. Are we countermanding that here, or omitting to mention it?

A third example would be useful, because this is one of the key cases that distinguished jukugo-ruby in previous discussions.

@macnmm
Copy link

macnmm commented Feb 15, 2019

Agreed more illustrations would be helpful. Jukugo ruby allows overhang to adjacent base glyphs (pushing their ruby if needed), and allows line breaking between base glyphs, but otherwise the normal ruby spacing rules apply with gaps between them when they are shorter than the width of base glyphs they annotate.

@frivoal
Copy link

frivoal commented Apr 3, 2020

Are we countermanding that here, or omitting to mention it?

My understanding is that we're countermanding it. Yes, richer models exist, but for a "simple model", this does the job.

@r12a
Copy link
Contributor Author

r12a commented Apr 3, 2020

Ouch. Seems to me that that makes the overall handling of ruby (for those who want to do more than simple stuff) much more difficult to implement and describe. I also think it will produce what some see as incorrect results, and some degree of confusion on top of the confusion that already exists around jukugo-ruby. If we want to propose simple solutions for authors that don't do what jukugo-ruby normally does, perhaps we should simply say: if this is the case, then use group ruby instead.

@r12a
Copy link
Contributor Author

r12a commented Apr 3, 2020

How about something like this:

For simple ruby implementations, if even a single ruby string is longer than its corresponding base character when laid out without inter-letter spacing the resulting layout would look identical to group-ruby.

And perhaps in bullet 3 also change 'processing' to 'resulting layout'.

@r12a
Copy link
Contributor Author

r12a commented Apr 3, 2020

If it doesn't take too much time, it would be nice to show an example that has the 1-1-3 arrangment too.

frivoal referenced this issue in frivoal/jlreq Apr 3, 2020
frivoal referenced this issue in w3c/jlreq Apr 3, 2020
@r12a r12a transferred this issue from w3c/jlreq Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants