W3C home > Mailing lists > Public > public-tt@w3.org > February 2017

[ttml2] Why not use elements for ruby?

From: r12a via GitHub <sysbot+gh@w3.org>
Date: Thu, 16 Feb 2017 17:22:04 +0000
To: public-tt@w3.org
Message-ID: <issues.opened-208189320-1487265723-sysbot+gh@w3.org>
r12a has just created a new issue for https://github.com/w3c/ttml2:

== Why not use elements for ruby? ==
10.2.34 tts:rubyAlign [and other sections]
https://www.w3.org/TR/2016/WD-ttml2-20161117/#style-attribute-rubyAlign

> The tts:ruby attribute is used to specify the application of ruby 
styling.
> This attribute may be specified by any element type that permits use
 of attributes in the TT Style Namespace; however, this attribute 
applies as a style property only to those element types indicated in 
the following table.
>  ...
> Applies to:   span

It's not clear to me why ruby markup is specified using 
spans-with-attributes, especially when the attribute significantly 
constrains the expected behaviour of the span.  It seems more logical 
to use inline elements to establish the semantic mappings between 
items that constitute a base text with ruby.  I understand that very 
few elements are used with TTML, but i think that using `ruby`, `rb`, 
and `rt` in this case would make life much simpler for  both user and 
spec editor, and since they are inline elements, they reflect semantic
 mappings rather than styling, and that seems it could be squeezed 
into the current model without too much pain(?).

Please view or discuss this issue at 
https://github.com/w3c/ttml2/issues/245 using your GitHub account
Received on Thursday, 16 February 2017 17:22:11 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:37 UTC