search

w3c / ttml3

Timed Text Markup Language 3 (TTML3)
http://w3c.github.io/ttml3/
Other
6 stars 6 forks source link

rubyOffset and line-spacing #8

Closed r12a closed 5 years ago

r12a commented 7 years ago

10.2.35 tts:rubyOffset https://www.w3.org/TR/2016/WD-ttml2-20161117/#style-attribute-rubyOffset

How does ruby offset interact with line spacing? Are we all covered there?

cconcolato commented 6 years ago

Linked to #373

nigelmegitt commented 6 years ago

@cconcolato does resolving #373 make the answer to @r12a 's question "yes"?

cconcolato commented 6 years ago

@nigelmegitt I don't think so. IIUC, during the meeting with the CSS WG at TPAC it was said that ruby annotations do not contribute to the line height. Also I don't understand what rubyOffset='auto' would mean. #373 does not give enough context.

Frankly, at this stage, I would be in favor of either deferring rubyOffset to the next version (when CSS has defined it) or of marking it at Risk.

nigelmegitt commented 6 years ago

@cconcolato if you don't think we need rubyOffset and you don't intend to implement it, or have insufficient confidence that your implementation will be interoperable (e.g. with CSS), I have no objection to deferring it.

css-meeting-bot commented 6 years ago

The Working Group just discussed rubyOffset and line-spacing ttml2#252, and agreed to the following resolutions:

The full IRC log of that discussion <nigel> Topic: rubyOffset and line-spacing ttml2#252
<nigel> github: https://github.com/w3c/ttml2/issues/252
<nigel> Glenn: I can accept deferring rubyOffset to the next version
<nigel> RESOLUTION: Remove rubyOffset and defer it to ttml.next
<nigel> Glenn: I put it in for thoroughness, not because I knew a particular use case in subtitling and captioning.
<nigel> .. Since CSS doesn't have ruby offset either we can wait.
r12a commented 6 years ago

Removal seems to void the original question. I have recommended to the i18n WG that we close our tracker for this issue.

nigelmegitt commented 6 years ago

Thank you, I'm going to label this as commenter agreed; @r12a if your recommendation to i18n is not accepted please could you let us know? Otherwise we'll assume there's no further action to take.

r12a commented 6 years ago

The i18n WG has closed its tracker for this issue.

skynavga commented 5 years ago

Closing this issue as tts:rubyOffset is no longer present, and no strong use case for it has appeared. If someone wishes to add it, file a new issue to that end and reference this (and other now closed issues related to tts:rubyOffset).