[css-ruby] Add more explanation for ruby-merge: auto, and check in missing image.

--HG--
extra : rebase_source : 19e57434c064bcda03a20345fa6e4615a2f4f8fa

Author: fantasai

css-ruby/Overview.html

@@ -21,7 +21,7 @@
 
   <meta content="CSS Ruby Module Level 1" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2013-09-11 name=dcterms.date>
+  <meta content=2013-09-13 name=dcterms.date>
   <meta content="Elika J. Etemad" name=dcterms.creator>
   <meta content="Koji Ishii" name=dcterms.creator>
   <meta content="Richard Ishida" name=dcterms.creator>
@@ -42,8 +42,8 @@
    <h1 class=p-name>CSS Ruby Module Level 1</h1>
 
    <h2 class="no-num no-toc" id=longstatus-date->Editor's Draft <time
-    class=dt-updated datetime=20130911>11 September 2013</time>
-    <!-- for HTML4 doctype: <span class="value-title" title="20130911">11 September 2013</span></span> --></h2>
+    class=dt-updated datetime=20130913>13 September 2013</time>
+    <!-- for HTML4 doctype: <span class="value-title" title="20130913">13 September 2013</span></span> --></h2>
 
    <dl>
     <dt>This version:
@@ -1392,15 +1392,20 @@ <h3 id=collapsed-ruby><span class=secno>3.2. </span> Collapsed Ruby
 
    <dd>
     <p> The user agent may use any algorithm to determine how each ruby
-     annotation box is rendered to its corresponding base box.
+     annotation box is rendered to its corresponding base box, with the
+     intention that if all annotations fit over their respective bases, the
+     result is identical to “mono ruby”, but if some annotations are
+     wider than their bases the space is shared in some way to avoid forcing
+     space between bases.
 
     <div class=example>
-     <p> One possible algorithm is described as Jukugo-ruby in <a
+     <p> One possible algorithm is described as “jukugo ruby” in <a
       href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>.
 
-     <p> Another, more simplified algorithm of Jukugo-ruby is to render as
-      Mono-ruby if all ruby annotation boxes fit within advances of their
-      corresponding base boxes, and render as Group-ruby otherwise.
+     <p> Another, more simplified algorithm of “jukugo ruby” is to render
+      as ‘<code class=css>separate</code>’ if all ruby annotation boxes
+      fit within the advances of their corresponding base boxes, and render
+      as ‘<code class=css>collapse</code>’ otherwise.
     </div>
   </dl>
 

css-ruby/Overview.src.html

@@ -952,15 +952,20 @@ <h3 id="collapsed-ruby">
 		<dd>
 			<p>
 				The user agent may use any algorithm to determine how each ruby annotation box
-				is rendered to its corresponding base box.
+				is rendered to its corresponding base box,
+				with the intention that if all annotations fit over their respective bases,
+				the result is identical to “mono ruby”,
+				but if some annotations are wider than their bases
+				the space is shared in some way
+				to avoid forcing space between bases.
 			<div class="example">
 			<p>
-				One possible algorithm is described as Jukugo-ruby in [[JLREQ]].
+				One possible algorithm is described as “jukugo ruby” in [[JLREQ]].
 			<p>
-				Another, more simplified algorithm of Jukugo-ruby is
-				to render as Mono-ruby if all ruby annotation boxes fit within
-				advances of their corresponding base boxes,
-				and render as Group-ruby otherwise.
+				Another, more simplified algorithm of “jukugo ruby” is
+				to render as ''separate'' if all ruby annotation boxes fit
+				within the advances of their corresponding base boxes,
+				and render as ''collapse'' otherwise.
 			</p>
 			</div>
 		</dd>