- From: Jet Villegas W3C <w3c@junglecode.net>
- Date: Mon, 10 Nov 2014 15:11:59 -0800
- To: Xidorn Quan <quanxunzhen@gmail.com>
- Cc: "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>, www International <www-international@w3.org>
- Message-ID: <CAP82YM4Nx2NyfF0kbnF6SJQ+UAis726ZhQWB47B-58Y=fR4LwA@mail.gmail.com>
I'm not seeing any objections here, but maybe the weekend e-mail fell through the cracks? If there really are no objections, we'll proceed with implementation as proposed earlier and file the spec bug. Thanks, --Jet On Sun, Nov 9, 2014 at 3:58 PM, Xidorn Quan <quanxunzhen@gmail.com> wrote: > On Sun, Nov 9, 2014 at 9:25 AM, Xidorn Quan <quanxunzhen@gmail.com> wrote: > >> >> On Sun, Nov 9, 2014 at 5:42 AM, L. David Baron <dbaron@dbaron.org> wrote: >> >>> http://dev.w3.org/csswg/css-ruby/#base-annotation-pairing says: >>> # If there are not enough ruby annotations in a ruby annotation >>> # container, the last one is paired with (spans across) any excess >>> # ruby bases. (If there are not any in the ruby annotation >>> # container, an anonymous empty one is assumed to exist.) >>> >>> Is there actually a use case for this behavior, or is it really just >>> defining error handling? >>> >> >> I guess they have, for example, an English word spans several kanji along >> with their kana. Or a multi-kanji word with two different pronunciation, >> one for kun'yomi, the other for on'yomi. >> >> I ask because I think it adds substantial extra complexity, >>> especially around line-breaking of ruby. If there isn't a good use >>> case for it, I would prefer if ruby annotation containers that do >>> not have enough annotations simply not provide annotations for the >>> final bases, instead of having their final annotation span all the >>> remaining bases. >> >> >> I want to add that, the spanning rule here not only increases the >> complexity on line-breaking, but also make it difficult to define space >> distribution behavior for alignment. You can see issue 9 in the current >> draft. >> > > In addition to the issues mentioned above, I suspect that it would also > affect 'ruby-position: inter-character', which does not support any > spanning when the directions are orthogonal. > > - Xidorn >
Received on Monday, 10 November 2014 23:12:28 UTC