- From: Stefan Pöschel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 May 2018 08:32:10 +0000
- To: public-tt@w3.org
spoeschel has just created a new issue for https://github.com/w3c/ttml2: == Ruby nesting: no preceding sibling case on ruby text content == The ruby nesting constraints contain the following constraint: "If the computed value of tts:ruby is text, then the computed value of tts:ruby of its preceding sibling is base, text, or delimiter" This however will not work when complex ruby is used, as the first child of a ruby text container is ruby text content, but has no preceding sibling. See e.g. "Example Fragment – Double-sided Ruby", So in line with the respective constraint related to ruby base content, the mentioned constraint should be changed to: "If the computed value of tts:ruby is base, 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, text, or delimiter." Please view or discuss this issue at https://github.com/w3c/ttml2/issues/787 using your GitHub account
Received on Wednesday, 23 May 2018 08:32:13 UTC