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] Not all jukugo ruby is like group ruby #9

Closed
r12a opened this issue Mar 25, 2020 · 3 comments
Closed

[simple-ruby] Not all jukugo ruby is like group ruby #9

r12a opened this issue Mar 25, 2020 · 3 comments

Comments

@r12a
Copy link
Contributor

r12a commented Mar 25, 2020

3.4 Placement of Jukugo-ruby
https://w3c.github.io/jlreq/docs/simple-ruby/#placement-of-jukugo-ruby

BP w3c/jlreq#2

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).

Not always, as described in JLREQ. If you have an example such as the following, my understanding is that there are limits to the amount of overlap allowed, which leads to gaps in the annotations (there would be no gaps for group ruby).

Screenshot 2020-03-25 at 17 29 52

This seems like an oversimplification (which also doesn't help implementers understand how jukugo is different from mono- and group-ruby).

@frivoal
Copy link

frivoal commented Apr 3, 2020

This looks like an example of Jukugo processing for kata-tsuki ruby, but simple ruby only deals with naka-tsuki ruby. In that context, the proposed rule is still a simplification over the full range of possibilities, but a much less radical one.

@frivoal
Copy link

frivoal commented Apr 3, 2020

(also, the aspect of this issue that this is not specific to kata-tsuki ruby seems to be a duplicate, or at least a close relative of #4)

@r12a
Copy link
Contributor Author

r12a commented Apr 3, 2020

Closing as duplicate of #4.

@r12a r12a closed this as completed 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

No branches or pull requests

2 participants