Fri, 13 Sep 2013 13:34:40 -0700
[css-ruby] Add more explanation for ruby-merge: auto, and check in missing image.
1.1 --- a/css-ruby/Overview.html Thu Sep 12 04:27:54 2013 -0700 1.2 +++ b/css-ruby/Overview.html Fri Sep 13 13:34:40 2013 -0700 1.3 @@ -21,7 +21,7 @@ 1.4 1.5 <meta content="CSS Ruby Module Level 1" name=dcterms.title> 1.6 <meta content=text name=dcterms.type> 1.7 - <meta content=2013-09-11 name=dcterms.date> 1.8 + <meta content=2013-09-13 name=dcterms.date> 1.9 <meta content="Elika J. Etemad" name=dcterms.creator> 1.10 <meta content="Koji Ishii" name=dcterms.creator> 1.11 <meta content="Richard Ishida" name=dcterms.creator> 1.12 @@ -42,8 +42,8 @@ 1.13 <h1 class=p-name>CSS Ruby Module Level 1</h1> 1.14 1.15 <h2 class="no-num no-toc" id=longstatus-date->Editor's Draft <time 1.16 - class=dt-updated datetime=20130911>11 September 2013</time> 1.17 - <!-- for HTML4 doctype: <span class="value-title" title="20130911">11 September 2013</span></span> --></h2> 1.18 + class=dt-updated datetime=20130913>13 September 2013</time> 1.19 + <!-- for HTML4 doctype: <span class="value-title" title="20130913">13 September 2013</span></span> --></h2> 1.20 1.21 <dl> 1.22 <dt>This version: 1.23 @@ -1392,15 +1392,20 @@ 1.24 1.25 <dd> 1.26 <p> The user agent may use any algorithm to determine how each ruby 1.27 - annotation box is rendered to its corresponding base box. 1.28 + annotation box is rendered to its corresponding base box, with the 1.29 + intention that if all annotations fit over their respective bases, the 1.30 + result is identical to “mono ruby”, but if some annotations are 1.31 + wider than their bases the space is shared in some way to avoid forcing 1.32 + space between bases. 1.33 1.34 <div class=example> 1.35 - <p> One possible algorithm is described as Jukugo-ruby in <a 1.36 + <p> One possible algorithm is described as “jukugo ruby” in <a 1.37 href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.38 1.39 - <p> Another, more simplified algorithm of Jukugo-ruby is to render as 1.40 - Mono-ruby if all ruby annotation boxes fit within advances of their 1.41 - corresponding base boxes, and render as Group-ruby otherwise. 1.42 + <p> Another, more simplified algorithm of “jukugo ruby” is to render 1.43 + as ‘<code class=css>separate</code>’ if all ruby annotation boxes 1.44 + fit within the advances of their corresponding base boxes, and render 1.45 + as ‘<code class=css>collapse</code>’ otherwise. 1.46 </div> 1.47 </dl> 1.48
2.1 --- a/css-ruby/Overview.src.html Thu Sep 12 04:27:54 2013 -0700 2.2 +++ b/css-ruby/Overview.src.html Fri Sep 13 13:34:40 2013 -0700 2.3 @@ -952,15 +952,20 @@ 2.4 <dd> 2.5 <p> 2.6 The user agent may use any algorithm to determine how each ruby annotation box 2.7 - is rendered to its corresponding base box. 2.8 + is rendered to its corresponding base box, 2.9 + with the intention that if all annotations fit over their respective bases, 2.10 + the result is identical to “mono ruby”, 2.11 + but if some annotations are wider than their bases 2.12 + the space is shared in some way 2.13 + to avoid forcing space between bases. 2.14 <div class="example"> 2.15 <p> 2.16 - One possible algorithm is described as Jukugo-ruby in [[JLREQ]]. 2.17 + One possible algorithm is described as “jukugo ruby” in [[JLREQ]]. 2.18 <p> 2.19 - Another, more simplified algorithm of Jukugo-ruby is 2.20 - to render as Mono-ruby if all ruby annotation boxes fit within 2.21 - advances of their corresponding base boxes, 2.22 - and render as Group-ruby otherwise. 2.23 + Another, more simplified algorithm of “jukugo ruby” is 2.24 + to render as ''separate'' if all ruby annotation boxes fit 2.25 + within the advances of their corresponding base boxes, 2.26 + and render as ''collapse'' otherwise. 2.27 </p> 2.28 </div> 2.29 </dd>
3.1 Binary file css-ruby/images/furigana-separate.png has changed