W3C home > Mailing lists > Public > www-style@w3.org > November 2014

Re: [css-ruby] spanning of ruby annotations across excess bases

From: Xidorn Quan <quanxunzhen@gmail.com>
Date: Wed, 12 Nov 2014 13:01:30 +1100
Message-ID: <CAMdq69-mzBC7Qd=8FcxBW0bmGRe0X2PoSLAu-JiBV0qnd3eE0Q@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: kawabata taichi <kawabata.taichi@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, "www-style@w3.org" <www-style@w3.org>
On Wed, Nov 12, 2014 at 12:04 PM, fantasai <fantasai.lists@inkedblade.net>

> On 11/11/2014 05:52 PM, Xidorn Quan wrote:
>> Yes, we have that in W3C HTML5, but we don't have it in WHATWG HTML5.
>> I think the behavior defined in W3C HTML5 is just a simplified version
>> of that in Ruby Anotation spec for XHTML http://www.w3.org/TR/ruby/ .
>> Given the use cases proposed in XHTML spec, I think nested ruby is even
>> better in semantics for many of them.
> No, Xidorn, it is not. WHATWG Ruby and HTML5 Ruby Ruby are significantly
> different in how they handle <ruby><rb/><rt/><rt/></ruby>, and the CSS
> spec is intentionally designed to handle the HTML5 Ruby model (because
> I don't agree with the WHATWG model).

I don't agree with that model as well, but I don't think HTML5 model is
perfect either. Back to spanning, IMHO, it introduces much complexity with
nearly no benefits, hence I suggest that we should get rid of it.

- Xidorn
Received on Wednesday, 12 November 2014 02:02:38 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:26 UTC