- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Sat, 28 Jun 2014 22:05:32 -0700
- To: kawabata taichi <kawabata.taichi@gmail.com>, www-style@w3.org
On 09/09/2013 12:10 AM, kawabata taichi wrote: > Dear CSS people, > > Recently, I've come up with several interesting Ruby use cases that > might need to be supported with Current CSS Ruby Level 1 [1] > specification. > > These cases are "Very long ruby lines", that have been rarely seen in > the past, but it has recently become more and more popular > (especially among Japanese novels for young ages.) > > I attach two sample pictures. > > Current CSS Ruby spec [1] do not consider forced line breaking on such > case. When ruby segment with too long ruby (or base) text appeared, > they may be overhang to the display box, thus it may cause the loss of visible > textual information to people who read the text. > > To cope with such ruby use, we might need to consider the "forced line > breaking" rule for too long ruby segment, though JLREQ[2] clearly > prohibits line breaking (Section 3.3.1 Usage of Ruby). Kawabata-san, I do not consider WebKit renderings to be any use as a reference for what ruby layout *should* do. JLREQ and printed materials are acceptable. Wrt how to handle such long annotations, IIRC WebKit does not know how to break ruby across lines. If breaking were implemented as specified in CSS Ruby, these examples would not be a problem. http://www.w3.org/TR/css-ruby/#break-within I will add some more examples and pictures to that section to help implementers understand how best to balance text; but fundamentally the problem of such long annotations is solved already in the spec, and authors can just add rb, rt { white-space: normal; } to enable breaking of group ruby across lines. ~fantasai
Received on Monday, 30 June 2014 08:10:20 UTC