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

Show better mappings between base and annotation in figures #275

Closed
r12a opened this issue Mar 6, 2017 · 4 comments

Comments

Projects
None yet
6 participants
@r12a
Copy link

commented Mar 6, 2017

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.

@r12a

This comment has been minimized.

Copy link
Author

commented Mar 6, 2017

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

@r12a r12a added the i18n-comment label Mar 6, 2017

@dae-kim dae-kim self-assigned this May 8, 2017

@dae-kim dae-kim removed their assignment Sep 8, 2017

@tmichel07 tmichel07 added the WR-pending label Oct 2, 2017

@skynavga skynavga removed the WR-pending label Jan 11, 2018

cconcolato added a commit that referenced this issue Jan 18, 2018

skynavga added a commit that referenced this issue Jan 25, 2018

@cconcolato cconcolato self-assigned this Jan 30, 2018

@cconcolato cconcolato added the pr open label Jan 31, 2018

@cconcolato

This comment has been minimized.

Copy link
Contributor

commented Jan 31, 2018

There are 2 comments in this issue:

#246 is about the second example and will be addressed there.
The above PR fixes the problem of the first example and should close this issue.

@cconcolato

This comment has been minimized.

Copy link
Contributor

commented Feb 14, 2018

@r12a Can you confirm that you are satisfied with the response and approve the PR?

cconcolato added a commit that referenced this issue Feb 16, 2018

Merge pull request #618 from w3c/issue-0275-ruby-example-2
Use mono ruby in example of rubyPosition (#275).
@r12a

This comment has been minimized.

Copy link
Author

commented Feb 23, 2018

The i18n WG has closed its tracker for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.