-
Notifications
You must be signed in to change notification settings - Fork 16
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
Show better mappings between base and annotation in figures #275
Comments
A particularly problematic instance of this, for me, is the example of complex ruby at http://w3c.github.io/ttml2/spec/ttml2.html#style-attribute-ruby-example-2 What makes complex ruby complex is not just that ruby text appears on both sides, but that there are multiple mappings between base an annotation. I believe that the example should show that とう maps to 東 and なん maps to 南, while たつみ maps to 東南. This is the correct semantic mapping for those items. Again, i think that lumping とうなん sets a bad example for content authors. (Note, btw, that lumping several annotations with several base characters in this way can cause wrapping issues in simple ruby, since it creates group ruby.) |
There are 2 comments in this issue:
#246 is about the second example and will be addressed there. |
@r12a Can you confirm that you are satisfied with the response and approve the PR? |
Use mono ruby in example of rubyPosition (#275).
The i18n WG has closed its tracker for this issue. |
10.2.39 tts:rubyPosition
http://w3c.github.io/ttml2/spec/ttml2.html#style-attribute-rubyPosition
Example Fragment – Ruby Position
The example sets a bad example imho by combining two base characters with two annotations. Content authors ought to properly associate base characters with the annotations that are specific to them, and i think the example should do the same.
The text was updated successfully, but these errors were encountered: