- From: Koji Ishii <kojiishi@gluesoft.co.jp>
- Date: Fri, 19 Sep 2014 14:03:38 +0000
- To: Richard Ishida <ishida@w3.org>
- CC: (wrong string) Åd <bobbytung@wanderer.tw>, David Hyatt <hyatt@apple.com>, www-style list <www-style@w3.org>, Xiaoqian Wu <xiaoqian@w3.org>, 奕钧 陈 <ethantw@me.com>, "font@but.tw" <font@but.tw>
> For more years than I care to remember the assumption has been that CSS would indicate that right-sided ruby needs to be used, but that the browser implementations would take care of the details. I don't think that will take long to spec. > > It's also what the current ruby layout spec says. : > I'd like to step back and check what it is we are talking about here. > > We could be talking about the positioning of all elements of bopomofo ruby to the right side of a base character being handled by opentype (once some indication is given that right-sided ruby is actually required, rather than above), or we could be talking just about the positioning of tone marks relative to the 'base' bopomofo characters (which is the context in which I had previously heard that 'oh, the font should take care of that'). I meant use CSS to put ruby on the right side, but better to use OpenType to position tone marks. Sorry if I sounded otherwise. > I also think that it's incongruous to expect to do bopomofo ruby using opentype features, but not, say, Japanese mono ruby, other than for the specific case of aligning the tone mark with the bopomofo letters. I assume the above answers this question ¡ª i agree that in regards to positioning ruby, it¡¯s CSS and layout engine. > We have been looking for bopomofo support for many years with basically no progress. For more than the 12 years I've been at the W3C various folks have been working on CSS and wondering how to handle bopomofo but never coming up with any concrete plans. I strongly disagree with the idea of stopping the progress that Dave is now making in favour of something that may possibly happen some time in the undefined future, if we're lucky. And by the way, that would be a solution that would only work for a handful of new fonts where opentype is supported - people won't be able to produce bopomofo for the fonts they currently have or prefer. > > I think Dave is on the right track. I think the CSS spec doesn't need to specify in detail how to arrange the bopomofo letters and tones relative to themselves - I think however the Chinese layout requirements document which is in preparation probably should. > > I propose we carry on. Again, I completely agree with you to appreciate supporting ruby-position:inter-character. The original question of this thread was: > For the tone marks, though, I don't do anything special yet. You can control the position of the tone marks with a nested ruby, but this is obviously not ideal. I am looking for guidance regarding how to position the tone marks automatically, but I am unclear on what the rules for positioning them are. I see different positioning rules in various examples¡ and this is what I thought we were discussing. Can we get back to this topic now? /koji
Received on Friday, 19 September 2014 14:04:14 UTC