[css-ruby] Clarifications & fixes to nested ruby rules.

--HG--
extra : rebase_source : c182ca9b68e4c89cb7918b1035e42aaaf27ec407

Author: fantasai

css-ruby/Overview.html

@@ -136,7 +136,7 @@ <h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class
 			<ul class=toc>
 			<li><a href=#segment-pairing><span class=secno>2.3.1</span>  Segment Pairing</a>
 			<li><a href=#base-annotation-pairing><span class=secno>2.3.2</span>  Unit Pairing</a>
-			<li><a href=#nested-pairing><span class=secno>2.3.3</span>  Nested Ruby</a></ul>
+			<li><a href=#nested-pairing><span class=secno>2.3.3</span>  Complex Spanning and Nested Ruby</a></ul>
 		<li><a href=#autohide><span class=secno>2.4</span>  Autohiding Annotations</a>
 		<li><a href=#white-space><span class=secno>2.5</span>  White Space</a>
 		<li><a href=#ruby-layout><span class=secno>2.6</span>  Ruby layout</a>
@@ -459,11 +459,16 @@ <h3 class="heading settled heading" data-level=2.2 id=box-fixup><span class=secn
 			Alternatively we could try to define some kind of acceptable behavior for them.
 	</ol>
 
+	<p>For the purpose of the rules above,
+	a <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a> directly parented by a <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
+	is considered to be a <a data-link-type=dfn href=#ruby-base-container-box title="ruby base container">ruby base container</a>.
+	See <a data-link-type=dfn href=#nested-ruby title="nested ruby">nested ruby</a>, below.
+
 	<p class=issue id=issue-f2086090><a class=self-link href=#issue-f2086090></a>Make this into an example:
 		<img src=http://lists.w3.org/Archives/Public/www-archive/2014Jun/att-0027/PastedGraphic-1.png style="display: block; width: 100%">
 
-	<p>At this point, all ruby layout structures are properly parented,
-	and the UA can start to associate bases with their annotations.
+	<p>Once all ruby layout structures are properly parented,
+	the UA can start to associate bases with their annotations.
 
 	<p class=note>
 	Note that the UA is not required to create any of these anonymous boxes
@@ -571,21 +576,28 @@ <h4 class="heading settled heading" data-level=2.3.2 id=base-annotation-pairing>
 	<p class=issue id=issue-0230a91a><a class=self-link href=#issue-0230a91a></a>Insert diagram</p>
 
 <h4 class="heading settled heading" data-level=2.3.3 id=nested-pairing><span class=secno>2.3.3 </span><span class=content>
-Nested Ruby</span><a class=self-link href=#nested-pairing></a></h4>
+Complex Spanning and Nested Ruby</span><a class=self-link href=#nested-pairing></a></h4>
 
-	<p>When <a data-link-type=dfn href=#ruby-container title="ruby containers">ruby containers</a> are nested,
+	<p><dfn data-dfn-type=dfn data-noexport="" id=nested-ruby title="nested ruby"><a class=self-link href=#nested-ruby></a></dfn>When <a data-link-type=dfn href=#ruby-container title="ruby containers">ruby containers</a> are nested,
 	pairing begins with the deepest <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>,
-	then expands out,
-	treating each <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a> nested within another <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
-	essentially as a single <a data-link-type=dfn href=#ruby-base-box title="ruby base">ruby base</a> in the outer <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>,
-	and associating each <a data-link-type=dfn href=#ruby-annotation-box title="ruby annotation">ruby annotation</a>
-	paired with the nested <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
-	as being associated with (spanning) all of its <a data-link-type=dfn href=#ruby-base-box title="ruby bases">ruby bases</a>.
-
-	<p>Using nested <a data-link-type=dfn href=#ruby-container title="ruby containers">ruby containers</a> thus allows the representation
+	then expands out.
+	From the pairing perspective of the outer <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>,
+	each <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a> nested within another <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
+	counts as representing a single <a data-link-type=dfn href=#ruby-base-box title="ruby base">ruby base</a>/<a data-link-type=dfn href=#ruby-annotation-box title=annotation>annotation</a> per level.
+	The outer <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>’s <a data-link-type=dfn href=#ruby-annotation-box title="ruby annotations">ruby annotations</a> paired to the <a data-link-type=dfn href=#nested-ruby title="nested ruby">nested ruby</a>
+	are therefore paired with (and <a data-link-type=dfn href=#span title=span>span</a>) all of the nested <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>’s <a data-link-type=dfn href=#ruby-base-box title="ruby bases">ruby bases</a>.
+	Each <a data-link-type=dfn href=#ruby-annotation-container-box title="ruby annotation container">ruby annotation container</a> in the nested <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
+	occupies the same <a data-link-type=dfn href=#annotation-level title="annotation level">annotation level</a> in the outer <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
+	as it does in the inner one
+	and participates in its layout as if it were directly contained in the outer <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>.
+
+	<p>This process is recursive.
+	Thus, using nested <a data-link-type=dfn href=#ruby-container title="ruby containers">ruby containers</a> allows the representation
 	of complex spanning relationships.
 
-	<p class=issue id=issue-2f9c28f2><a class=self-link href=#issue-2f9c28f2></a>This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
+	<p class=issue id=issue-05f90a82><a class=self-link href=#issue-05f90a82></a>This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
+	(Also, if we’re ever going to support it, it has to be designed into level 1
+	or authors will depend on whatever degenerate behavior falls out.)
 
 <h3 class="heading settled heading" data-level=2.4 id=autohide><span class=secno>2.4 </span><span class=content>
 Autohiding Annotations</span><a class=self-link href=#autohide></a></h3>
@@ -1564,6 +1576,7 @@ <h2 class="no-num no-ref heading settled heading" id=index><span class=content>
 <li>intra-ruby white space, <a href=#intra-ruby-white-space title="section 2.2">2.2</a>
 <li>left, <a href=#valdef-ruby-position.left title="section 3.1">3.1</a>
 <li>level, <a href=#annotation-level title="section 2.3.1">2.3.1</a>
+<li>nested ruby, <a href=#nested-ruby title="section 2.3.3">2.3.3</a>
 <li>over, <a href=#valdef-ruby-position.over title="section 3.1">3.1</a>
 <li>pairing, <a href=#pairing title="section 2.3">2.3</a>
 <li>right, <a href=#valdef-ruby-position.right title="section 3.1">3.1</a>
@@ -1611,8 +1624,10 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 	<a href=#issue-f2086090> ↵ </a></div><div class=issue>Insert diagram<a href=#issue-0230a91a> ↵ </a></div>
 
 <div class=issue>This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
+	(Also, if we’re ever going to support it, it has to be designed into level 1
+	or authors will depend on whatever degenerate behavior falls out.)
 
-<a href=#issue-2f9c28f2> ↵ </a></div><div class=issue>Specify how these anonymous white space boxes impact layout.
+<a href=#issue-05f90a82> ↵ </a></div><div class=issue>Specify how these anonymous white space boxes impact layout.
 
 	<a href=#issue-1851041e> ↵ </a></div><div class=issue>Or should it become a quasi-base between two bases?<a href=#issue-029133da> ↵ </a></div>
 	A spanning <div class=issue>

css-ruby/Overview.src.html

@@ -302,11 +302,16 @@ <h3 id="box-fixup">
 			Alternatively we could try to define some kind of acceptable behavior for them.
 	</ol>
 
+	<p>For the purpose of the rules above,
+	a <i>ruby container</i> directly parented by a <i>ruby container</i>
+	is considered to be a <i>ruby base container</i>.
+	See <i>nested ruby</i>, below.
+
 	<p class="issue">Make this into an example:
 		<img src="http://lists.w3.org/Archives/Public/www-archive/2014Jun/att-0027/PastedGraphic-1.png" style="display: block; width: 100%">
 
-	<p>At this point, all ruby layout structures are properly parented,
-	and the UA can start to associate bases with their annotations.
+	<p>Once all ruby layout structures are properly parented,
+	the UA can start to associate bases with their annotations.
 
 	<p class="note">
 	Note that the UA is not required to create any of these anonymous boxes
@@ -414,21 +419,28 @@ <h4 id="base-annotation-pairing">
 	<p class="issue">Insert diagram</p>
 
 <h4 id="nested-pairing">
-Nested Ruby</h4>
+Complex Spanning and Nested Ruby</h4>
 
-	<p>When <i>ruby containers</i> are nested,
+	<p><dfn title="nested ruby"></dfn>When <i>ruby containers</i> are nested,
 	pairing begins with the deepest <i>ruby container</i>,
-	then expands out,
-	treating each <i>ruby container</i> nested within another <i>ruby container</i>
-	essentially as a single <i>ruby base</i> in the outer <i>ruby container</i>,
-	and associating each <i>ruby annotation</i>
-	paired with the nested <i>ruby container</i>
-	as being associated with (spanning) all of its <i>ruby bases</i>.
-
-	<p>Using nested <i>ruby containers</i> thus allows the representation
+	then expands out.
+	From the pairing perspective of the outer <i>ruby container</i>,
+	each <i>ruby container</i> nested within another <i>ruby container</i>
+	counts as representing a single <i>ruby base</i>/<i>annotation</i> per level.
+	The outer <i>ruby container</i>’s <i>ruby annotations</i> paired to the <i>nested ruby</i>
+	are therefore paired with (and <i>span</i>) all of the nested <i>ruby container</i>’s <i>ruby bases</i>.
+	Each <i>ruby annotation container</i> in the nested <i>ruby container</i>
+	occupies the same <i>annotation level</i> in the outer <i>ruby container</i>
+	as it does in the inner one
+	and participates in its layout as if it were directly contained in the outer <i>ruby container</i>.
+
+	<p>This process is recursive.
+	Thus, using nested <i>ruby containers</i> allows the representation
 	of complex spanning relationships.
 
 	<p class="issue">This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
+	(Also, if we're ever going to support it, it has to be designed into level 1
+	or authors will depend on whatever degenerate behavior falls out.)
 
 <h3 id="autohide">
 Autohiding Annotations</h3>