- From: Stefan Pöschel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 May 2018 09:03:08 +0000
- To: public-tt@w3.org
spoeschel has just created a new issue for https://github.com/w3c/ttml2: == Ruby nesting: no preceding (text) sibling case on ruby delimiter == The issue of #787 also affects the "delimiter" case i.e. the following constraint (as TTML2 also allows delimiters with complex ruby, while the W3C ruby recommendation only allows delimiters when simple ruby is used): "If the computed value of tts:ruby is delimiter, then the computed value of tts:ruby of its preceding sibling is base or text." In addition ruby text content must not occur before a ruby delimiter, so the value "text" has to be removed from the constraint, too. Proposal to change to: "If the computed value of tts:ruby is delimiter, then its preceding sibling is either null (i.e., no preceding sibling) or the computed value of tts:ruby of its preceding sibling is base." Please view or discuss this issue at https://github.com/w3c/ttml2/issues/788 using your GitHub account
Received on Wednesday, 23 May 2018 09:03:17 UTC