Re: [css-ruby] Should CSS Ruby be consistent with HTML5 Ruby?

Dear fantasai,

2014/1/9 fantasai <fantasai.lists@inkedblade.net>
>
> As far as current spec (http://darobin.github.io/html-ruby/) is
>> concerned, <rbc> element does not exist. (It does exists in XHTML Ruby,
>> though.)
>>
>>  Note also that for double-sided ruby, <rbc> is still required in HTML5
>>> Ruby, to delineate the two sides.
>>>
>>
>> For double-sided ruby, I think not <rbc>, but <rtc> is necessary, as
>> follows.
>>
>> <ruby>Base<rtc>text A</rtc><rtc>text B</rtc></ruby>
>>
>
> Sorry, you're right. I misread your email. :)
>
> I didn't remove the ruby-base-container element because
> a) it simplifies the layout abstraction to have a box that is parallel
>    in construction to the ruby-text-container
> b) it allows a UA directly support XHTML ruby markup with only this
>    one addition
>
> For HTML5 markup, the ruby-base-container is automatically generated
> and need never show up in the source as an element.


My point is that, as long as HTML5's categorization algorithm is
applied, we no longer need ruby-text-container. The role of <rbc> of
XHTML can safely be ignored.

"Display" property is originally for non-HTML XML documents to apply
the role of ruby to their element names, but if we nolonger need
ruby-text-container as its role can be complemented by an algorithm,
do we really need its value for "display" property?

One problem of HTML5 Ruby is that it can specify Ruby Bases and Texts
in an implicit way (unlike XHTML ruby). This means that we no longer
be able to select Ruby Bases by simply selecting the <rb> or <rbc>
node, or Ruby Texts by <rt> or <rtc>.  This may cause some problem on
accessibility, and we may need to consider to device the new selector
to select Ruby Bases even if they are implicity defined.

-- 
---------------------------------------------------------------------
KAWABATA, Taichi E-mail: kawabata.taichi@gmail.com