changeset
[css-ruby] Clean up wording, markup, issues for ruby properties.
Thu, 20 Jun 2013 15:32:56 -0700
- author
- fantasai <fantasai.cvs@inkedblade.net>
- date
- Thu, 20 Jun 2013 15:32:56 -0700
- changeset 8526
- eae28530e7d7
- parent 8525
- a3b77bd5adbe
- child 8527
- 47abcae337d2
[css-ruby] Clean up wording, markup, issues for ruby properties.
| css-ruby/Overview.html | file | annotate | diff | comparison | revisions | |
| css-ruby/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css-ruby/Overview.html Thu Jun 20 15:24:37 2013 -0700 1.2 +++ b/css-ruby/Overview.html Thu Jun 20 15:32:56 2013 -0700 1.3 @@ -1,3 +1,11 @@ 1.4 +<!-- 1.5 + 1.6 +Issues: 1.7 + white space 1.8 + line breaking 1.9 + bidi 1.10 + 1.11 +--> 1.12 <!DOCTYPE html> 1.13 1.14 <html lang=en> 1.15 @@ -11,7 +19,7 @@ 1.16 1.17 <meta content="CSS Ruby Module Level 1" name=dcterms.title> 1.18 <meta content=text name=dcterms.type> 1.19 - <meta content=2013-06-18 name=dcterms.date> 1.20 + <meta content=2013-06-20 name=dcterms.date> 1.21 <meta content="Elika J. Etemad" name=dcterms.creator> 1.22 <meta content="Koji Ishii" name=dcterms.creator> 1.23 <meta content="Richard Ishida" name=dcterms.creator> 1.24 @@ -32,8 +40,8 @@ 1.25 <h1 class=p-name>CSS Ruby Module Level 1</h1> 1.26 1.27 <h2 class="no-num no-toc" id=longstatus-date->Editor's Draft <time 1.28 - class=dt-updated datetime=20130618>18 June 2013</time> 1.29 - <!-- for HTML4 doctype: <span class="value-title" title="20130618">18 June 2013</span></span> --></h2> 1.30 + class=dt-updated datetime=20130620>20 June 2013</time> 1.31 + <!-- for HTML4 doctype: <span class="value-title" title="20130620">20 June 2013</span></span> --></h2> 1.32 1.33 <dl> 1.34 <dt>This version: 1.35 @@ -215,11 +223,13 @@ 1.36 <li><a href="#rubypos"><span class=secno>3.1. </span> Ruby positioning: 1.37 the ‘<code class=property>ruby-position</code>’ property</a> 1.38 1.39 - <li><a href="#rubymerge"><span class=secno>3.2. </span>Ruby merge: the 1.40 - ‘<code class=property>ruby-merge</code>’ property</a> 1.41 - 1.42 - <li><a href="#rubyalign"><span class=secno>3.3. </span> Ruby alignment: 1.43 - the ‘<code class=property>ruby-align</code>’ property</a> 1.44 + <li><a href="#collapsed-ruby"><span class=secno>3.2. </span> Collapsed 1.45 + Ruby Annotations: the ‘<code class=property>ruby-merge</code>’ 1.46 + property</a> 1.47 + 1.48 + <li><a href="#rubyalign"><span class=secno>3.3. </span> Ruby Text 1.49 + Distribution: the ‘<code class=property>ruby-align</code>’ 1.50 + property</a> 1.51 </ul> 1.52 1.53 <li><a href="#rubyover"><span class=secno>4. </span> Ruby Overhang and 1.54 @@ -258,6 +268,8 @@ 1.55 1.56 <li class=no-num><a href="#acknowledgments"> Acknowledgments</a> 1.57 1.58 + <li class=no-num><a href="#changes"> Changes</a> 1.59 + 1.60 <li class=no-num><a href="#references"> References</a> 1.61 <ul class=toc> 1.62 <li class=no-num><a href="#normative-references"> Normative 1.63 @@ -322,1038 +334,985 @@ 1.64 1.65 <dd>Narrow-cell glyph (e.g. Roman) which is the <var>n</var>th glyph in 1.66 the text run. 1.67 - <p>The orientation which the above symbols assume in the diagrams 1.68 - corresponds to the orientation that the glyphs they represent are 1.69 - intended to assume when rendered by the user agent. Spacing between 1.70 - these characters in the diagrams is incidental, unless intentionally 1.71 - changed to make a point. 1.72 - 1.73 - <h3 id=ruby-def><span class=secno>1.4. </span> What is ruby?</h3> 1.74 - 1.75 - <p><dfn id=ruby>Ruby</dfn> is the commonly-used name for a run of text 1.76 - that appears alongside another run of text (referred to as the 1.77 - “base”) and serves as an annotation or a pronunciation guide 1.78 - associated with that run of text. 1.79 - 1.80 - <p>The following figures show two examples of Ruby, a simple case and one 1.81 - with more complicated structure. 1.82 - 1.83 - <div class=example> 1.84 - <p>In this first example, a single annotation is used to annotate the 1.85 - base text. 1.86 - 1.87 - <div class=figure> 1.88 - <p><img alt="Example of ruby applied on top of a Japanese expression" 1.89 - src="images/licence.png"> 1.90 - 1.91 - <p class=caption>Example of ruby used in Japanese (simple case) 1.92 - </div> 1.93 - 1.94 - <p>In Japanese typography, this case is sometimes called <i 1.95 - lang=ja>taigo</i> ruby or group-ruby (per-word ruby), because the 1.96 - annotation as a whole is associated with multi-character word (as a 1.97 - whole). 1.98 - </div> 1.99 - 1.100 - <div class=example> 1.101 - <p>In this second example, two levels of annotations are attached to a 1.102 - base sequence: the hiragana characters on top refer to the 1.103 - pronunciation of each of the base kanji characters, while the words 1.104 - “Keio” and “University” on the bottom are annotations 1.105 - describing the English translation. 1.106 - 1.107 - <div class=figure> 1.108 - <p><img 1.109 - alt="Example showing complex ruby with annotation text over and under the base characters" 1.110 - src="images/ruby-univ.gif"> 1.111 - 1.112 - <p class=caption>Complex ruby with annotation text over and under the 1.113 - base characters 1.114 - </div> 1.115 - 1.116 - <p> 1.117 - 1.118 - <p>Notice that to allow correct association between the hiragana 1.119 - characters and their corresponding Kanji base characters, the spacing 1.120 - between these Kanji characters is adjusted. (This happens around the 1.121 - fourth Kanji character in the figure above.) To avoid variable spacing 1.122 - between the Kanji characters in the example above the hiragana 1.123 - annotations can be styled as a <i>collapsed annotation</i>, which will 1.124 - look more like the group-ruby example earlier. However because the 1.125 - base-annotation pairings are recorded in the ruby structure, if the 1.126 - text breaks across lines, the annotation characters will stay correctly 1.127 - paired with their respective base characters. 1.128 - </div> 1.129 - <a href="#ruby"><i>Ruby</i></a> formatting as used in Japanese is 1.130 - described in JIS X-4051 <a href="#JIS4051" 1.131 - rel=biblioentry>[JIS4051]<!--{{JIS4051}}--></a> (in Japanese) and in 1.132 - Requirements for Japanese Text Layout <a href="#JLREQ" 1.133 - rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> (in English and Japanese)]. 1.134 - In HTML, ruby structure and markup to represent it is described in the 1.135 - Ruby Markup Extension specification. This module describes the CSS 1.136 - rendering model and formatting controls relevant to ruby layout of such 1.137 - markup. 1.138 - <h2 id=ruby-model><span class=secno>2. </span> Ruby Formatting Model</h2> 1.139 - 1.140 - <p>The CSS ruby model is based on the <a 1.141 - href="http://darobin.github.io/html-ruby/">HTML Ruby Markup 1.142 - Extension</a> and <a href="http://www.w3.org/TR/ruby/">XHTML Ruby 1.143 - Annotation Recommendation</a> <a href="#RUBY" 1.144 - rel=biblioentry>[RUBY]<!--{{RUBY}}--></a>. In this model, a ruby 1.145 - structure consists of one or more <dfn id=ruby-base>ruby base</dfn> 1.146 - elements representing the base (annotated) text, associated with one or 1.147 - more levels of <dfn id=ruby-annotation>ruby annotation</dfn> elements 1.148 - representing the annotations. The structure of ruby is similar to that 1.149 - of a table: there are “rows” (the base text level, each annotation 1.150 - level) and “columns” (each <a href="#ruby-base-box"><i>ruby 1.151 - base</i></a> and its corresponding <a 1.152 - href="#ruby-annotation-box"><i>ruby annotations</i></a>). 1.153 - 1.154 - <p>Consecutive bases and annotations are grouped together into <dfn 1.155 - id=ruby-segments>ruby segments</dfn>. Within a <i>ruby segment</i>, a <a 1.156 - href="#ruby-annotation-box"><i>ruby annotation</i></a> may span multiple 1.157 - <a href="#ruby-base-box"><i>ruby bases<i>. </i></i></a> 1.158 - 1.159 - <p class=note>In HTML, a single <code><ruby></code> element may 1.160 - contain multiple <a href="#ruby-segments"><i>ruby segments</i></a>. (In 1.161 - the XHTML Ruby model, a single <code><ruby></code> element can 1.162 - only contain one <i>ruby segment</i>.) 1.163 - 1.164 - <h3 id=ruby-display><span class=secno>2.1. </span> Ruby-specific ‘<code 1.165 - class=property>display</code>’ property values</h3> 1.166 - 1.167 - <p>For document languages (such as XML applications) that do not have 1.168 - pre-defined ruby elements, authors must map document language elements 1.169 - to ruby elements; this is done with the ‘<code 1.170 - class=property>display</code>’ property. 1.171 - 1.172 - <table class=propdef> 1.173 - <tbody> 1.174 - <tr> 1.175 - <th>Name: 1.176 - 1.177 - <td>display 1.178 - 1.179 - <tr> 1.180 - <th><a href="#values">New Values</a>: 1.181 - 1.182 - <td>ruby | ruby-base | ruby-text | ruby-base-container | 1.183 - ruby-text-container 1.184 - </table> 1.185 - 1.186 - <p>The following new ‘<code class=property>display</code>’ values 1.187 - assign ruby layout roles to an arbitrary element: 1.188 - 1.189 - <dl> 1.190 - <dt>‘<a href="#ruby"><code class=css>ruby</code></a>’ 1.191 - 1.192 - <dd>Specifies that an element generates a <dfn id=ruby-container-box 1.193 - title="ruby container | ruby container box">ruby container box</dfn>. 1.194 - (Corresponds to HTML/XHTML <code><ruby></code> elements.) 1.195 - 1.196 - <dt>‘<code class=css>ruby-base</code>’ 1.197 - 1.198 - <dd>Specifies that an element generates a <dfn id=ruby-base-box 1.199 - title="ruby base box | ruby base">ruby base box</dfn>. (Corresponds to 1.200 - HTML/XHTML <code><rb></code> elements.) 1.201 - 1.202 - <dt>‘<code class=css>ruby-text</code>’ 1.203 - 1.204 - <dd>Specifies that an element generates a <dfn id=ruby-annotation-box 1.205 - title="ruby annotation box | ruby annotation">ruby annotation 1.206 - box</dfn>. (Corresponds to HTML/XHTML <code><rt></code> 1.207 - elements.) 1.208 - 1.209 - <dt>‘<code class=css>ruby-base-container</code>’ 1.210 - 1.211 - <dd>Specifies that an element generates a <dfn 1.212 - id=ruby-base-container-box 1.213 - title="ruby base container box | ruby base container">ruby base 1.214 - container box</dfn>. (Corresponds to XHTML <code><rbc></code> 1.215 - elements; always implied in HTML.) 1.216 - 1.217 - <dt>‘<code class=css>ruby-text-container</code>’ 1.218 - 1.219 - <dd>Specifies that an element generates a <dfn 1.220 - id=ruby-annotation-container-box 1.221 - title="ruby annotation container box | ruby annotation container">ruby 1.222 - annotation container box</dfn>. (Corresponds to HTML/XHTML 1.223 - <code><ruby></code> elements.) 1.224 - </dl> 1.225 - 1.226 - <h3 id=box-fixup><span class=secno>2.2. </span> Anonymous Ruby Box 1.227 - Generation</h3> 1.228 - 1.229 - <p>The CSS model does not require that the document language include 1.230 - elements that correspond to each of these components. Missing parts of 1.231 - the structure are implied through the anonymous box generation rules <a 1.232 - href="http://www.w3.org/TR/CSS21/tables.html#anonymous-boxes">similar to 1.233 - those used to normalize tables</a>. <a href="#CSS21" 1.234 - rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> 1.235 - 1.236 - <ol> 1.237 - <li>Any in-flow block-level boxes directly contained by a <a 1.238 - href="#ruby-container-box"><i>ruby container</i></a>, <a 1.239 - href="#ruby-base-container-box"><i>ruby base container</i></a>, <a 1.240 - href="#ruby-annotation-container-box"><i>ruby annotation 1.241 - container</i></a>, <a href="#ruby-base-box"><i>ruby base box</i></a>, 1.242 - or <a href="#ruby-annotation-box"><i>ruby annotation box</i></a> are 1.243 - forced to be inline-level boxes, and their ‘<code 1.244 - class=property>display</code>’ value computed accordingly. For 1.245 - example, the ‘<code class=property>display</code>’ property of an 1.246 - in-flow element with ‘<code class=css>display: block</code>’ 1.247 - parented by an element with ‘<code class=css>display: 1.248 - ruby-text</code>’ computes to ‘<code 1.249 - class=css>inline-block</code>’. This computation occurs after any 1.250 - intermediary anonymous-box fixup (such as that required by internal 1.251 - table elements). 1.252 - 1.253 - <li>Any consecutive sequence of <a href="#ruby-base-box"><i>ruby 1.254 - bases</i></a> not parented by a <a 1.255 - href="#ruby-base-container-box"><i>ruby base container</i></a> is 1.256 - wrapped in an anonymous <a href="#ruby-base-container-box"><i>ruby base 1.257 - container</i></a>. Similarly, any consecutive sequence of <a 1.258 - href="#ruby-annotation-box"><i>ruby annotations</i></a> not parented by 1.259 - a <a href="#ruby-annotation-container-box"><i>ruby annotation 1.260 - container</i></a> is wrapped in an anonymous <a 1.261 - href="#ruby-annotation-container-box"><i>ruby annotation 1.262 - container</i></a>. 1.263 - 1.264 - <li>Within each <a href="#ruby-base-container-box"><i>ruby base 1.265 - container</i></a>, each sequence of inline-level boxes is wrapped in an 1.266 - anonymous <a href="#ruby-base-box"><i>ruby base box</i></a>. Similarly, 1.267 - within each <a href="#ruby-annotation-container-box"><i>ruby annotation 1.268 - container</i></a>, each sequence of inline-level boxes is wrapped in an 1.269 - anonymous <a href="#ruby-annotation-box"><i>ruby annotation 1.270 - box</i></a>. 1.271 - 1.272 - <li>A sequence of <a href="#ruby-base-container-box"><i>ruby base 1.273 - containers</i></a> and/or <a 1.274 - href="#ruby-annotation-container-box"><i>ruby annotation 1.275 - containers</i></a> not parented by a <a 1.276 - href="#ruby-container-box"><i>ruby container</i></a> is wrapped in an 1.277 - anonymous <a href="#ruby-container-box"><i>ruby container</i></a>. 1.278 - </ol> 1.279 - 1.280 - <p>At this point, all ruby layout structures are properly parented, and 1.281 - the UA can start to associate bases with their annotations. 1.282 - 1.283 - <p class=note> Note that the UA is not required to create any of these 1.284 - anonymous boxes in its internal structures, as long as pairing and 1.285 - layout behaves as if they existed. 1.286 - 1.287 - <h3 id=pairing><span class=secno>2.3. </span> Ruby Pairing and Annotation 1.288 - Levels</h3> 1.289 - 1.290 - <p>Within a ruby structure, each <a href="#ruby-base-box"><i>ruby 1.291 - bases</i></a> are associated with <a href="#ruby-annotation-box"><i>ruby 1.292 - annotations</i></a> and vice versa. A <a href="#ruby-base-box"><i>ruby 1.293 - base</i></a> can be associated with at most one <a 1.294 - href="#ruby-annotation-box"><i>ruby annotation</i></a> per annotation 1.295 - level. If there are multiple annotation levels, it can therefore be 1.296 - associated with multiple <a href="#ruby-annotation-box"><i>ruby 1.297 - annotations</i></a>. A <a href="#ruby-annotation-box"><i>ruby 1.298 - annotation</i></a> is associated with one or more <a 1.299 - href="#ruby-base-box"><i>ruby bases</i></a>; annotations can span 1.300 - multiple bases. 1.301 - 1.302 - <p><dfn id=annotation-pairing>Annotation pairing</dfn> is the process of 1.303 - associating <a href="#ruby-annotation-box"><i>ruby annotations</i></a> 1.304 - with <a href="#ruby-base-box"><i>ruby bases</i></a>. 1.305 - 1.306 - <ol> 1.307 - <li> 1.308 - <p>First, the ruby structure is divided into <a 1.309 - href="#ruby-segments"><i>ruby segments</i></a>, each consisting of a 1.310 - single <a href="#ruby-base-container-box"><i>ruby base 1.311 - container</i></a> followed by one or more <a 1.312 - href="#ruby-annotation-container-box"><i>ruby annotation 1.313 - containers</i></a>. If the first child of a <a 1.314 - href="#ruby-container-box"><i>ruby container</i></a> is a <a 1.315 - href="#ruby-annotation-container-box"><i>ruby annotation 1.316 - container</i></a>, an anonymous, empty <a 1.317 - href="#ruby-base-container-box"><i>ruby base container</i></a> is 1.318 - assumed to exist before it. Similarly, if the <a 1.319 - href="#ruby-container-box"><i>ruby container</i></a> contains 1.320 - consecutive <a href="#ruby-base-container-box"><i>ruby base 1.321 - containers</i></a>, anonymous, empty <a 1.322 - href="#ruby-annotation-container-box"><i>ruby annotation 1.323 - containers</i></a> are assumed to exist between them. The <a 1.324 - href="#ruby-base-container-box"><i>ruby base container</i></a> in each 1.325 - segment is thus associated with each of the <a 1.326 - href="#ruby-annotation-container-box"><i>ruby annotation 1.327 - containers</i></a> in that segment. 1.328 - 1.329 - <p>Each <a href="#ruby-annotation-container-box"><i>ruby annotation 1.330 - containers</i></a> in a <i>ruby segment</i> represents one <dfn 1.331 - id=level title="annotation level | level">level</dfn> of annotation: 1.332 - the first one represents the first level of annotation, the second one 1.333 - represents the second level of annotation, and so on. 1.334 - 1.335 - <li>Within each <i>ruby segment</i>, each <a 1.336 - href="#ruby-base-box"><i>ruby base box</i></a> in the <a 1.337 - href="#ruby-base-container-box"><i>ruby base container</i></a> is 1.338 - paired with one <a href="#ruby-annotation-box"><i>ruby annotation 1.339 - box</i></a> from each <a href="#ruby-annotation-container-box"><i>ruby 1.340 - annotation container</i></a> in its <i>ruby segment</i>. If there are 1.341 - not enough <a href="#ruby-annotation-box"><i>ruby annotations</i></a> 1.342 - in a <a href="#ruby-annotation-container-box"><i>ruby annotation 1.343 - container</i></a>, the last one is associated with any excess <a 1.344 - href="#ruby-base-box"><i>ruby bases</i></a>. (If there are not any in 1.345 - the <a href="#ruby-annotation-container-box"><i>ruby annotation 1.346 - container</i></a>, an anonymous empty one is assumed to exist.) If 1.347 - there are not enough <a href="#ruby-base-box"><i>ruby bases</i></a>, 1.348 - any remaining <a href="#ruby-annotation-box"><i>ruby 1.349 - annotations</i></a> are assumed to be associated with empty, anonymous 1.350 - bases inserted at the end of the <a 1.351 - href="#ruby-base-container-box"><i>ruby base container</i></a>. 1.352 - <p>If an implementation supports ruby markup with explicit spanning 1.353 - (e.g. XHTML Complex Ruby Annotations), it must adjust the pairing 1.354 - rules to pair spanning annotations to multiple bases appropriately. 1.355 - </ol> 1.356 - 1.357 - <p>A this point, ruby “columns” are defined, each represented by a 1.358 - single <a href="#ruby-base-box"><i>ruby base</i></a> and associated with 1.359 - one <a href="#ruby-annotation-box"><i>ruby annotation</i></a> (possibly 1.360 - an empty, anonymous one) from each <a href="#level"><i>annotation 1.361 - level</i></a>. 1.362 - 1.363 - <h4 id=nested-pairing><span class=secno>2.3.1. </span> Nested Ruby</h4> 1.364 - 1.365 - <p>When <a href="#ruby-container-box"><i>ruby containers</i></a> are 1.366 - nested, pairing begins with the deepest <a 1.367 - href="#ruby-container-box"><i>ruby container</i></a>, then expands out, 1.368 - treating each <a href="#ruby-container-box"><i>ruby container</i></a> 1.369 - nested within another <a href="#ruby-container-box"><i>ruby 1.370 - container</i></a> as a <a href="#ruby-base-box"><i>ruby base</i></a>, 1.371 - and associating each <a href="#ruby-annotation-box"><i>ruby 1.372 - annotation</i></a> associated with the nested <a 1.373 - href="#ruby-container-box"><i>ruby container</i></a> as being associated 1.374 - with (spanning) all of its <a href="#ruby-base-box"><i>ruby 1.375 - bases</i></a>. 1.376 - 1.377 - <p>Using nested <a href="#ruby-container-box"><i>ruby containers</i></a> 1.378 - thus allows the representation of complex spanning relationships. 1.379 - 1.380 - <p class=issue>This shouldn't belong in Level 1. But HTML5 allows it, so 1.381 - we have to handle it. Yay HTML5. 1.382 - 1.383 - <h3 id=box-model><span class=secno>2.4. </span> Generating Ruby Structure</h3> 1.384 - 1.385 - <p> 1.386 - 1.387 - <h3 id=box-model><span class=secno>2.5. </span> Ruby box model</h3> 1.388 - 1.389 - <p>In the following description, the elements specified by Ruby 1.390 - Annotation <a href="#RUBY" rel=biblioentry>[RUBY]<!--{{RUBY}}--></a> are 1.391 - used to describe the box model. As mentioned earlier, a user agent can 1.392 - obtain the same results by using the Ruby specific ‘<code 1.393 - class=property>display</code>’ property values. 1.394 - 1.395 - <p>For a user agent that supports the ruby markup, the ruby structure 1.396 - consists of three or more boxes. The outermost container is the <a 1.397 - href="http://www.w3.org/TR/ruby/#ruby"><samp>ruby</samp></a> element 1.398 - itself. In the simple case, it is a container for two non-overlapping 1.399 - boxes: the ruby text box (<a 1.400 - href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element) and 1.401 - the ruby base box (<a 1.402 - href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element). The 1.403 - positioning of these two boxes relative to each other is controlled by 1.404 - the <a href="#rubypos">‘<code 1.405 - class=property>ruby-position</code>’</a> property. 1.406 - 1.407 - <div class=figure> <img 1.408 - alt="Diagram of the ruby box model consisting of two boxes, one on top of the other, enclosed within a third box representing the ruby element" 1.409 - class=example height=93 src="images/r-box-t.gif" width=223> 1.410 - <p><b>Figure 3.2.1</b>: Ruby box model (simple case) 1.411 - </div> 1.412 - 1.413 - <p>In the case of complex ruby, the ruby element is a container for two 1.414 - or three non-overlapping boxes: one ruby base collection (<a 1.415 - href="http://www.w3.org/TR/ruby/#rbc"><samp>rbc</samp></a> element), and 1.416 - one or two ruby text collections (<a 1.417 - href="http://www.w3.org/TR/ruby/#rtc"><samp>rtc</samp></a> element). The 1.418 - <samp>rbc</samp> element is itself a container for one or several ruby 1.419 - base box (<samp>rb</samp> element), while each <samp>rtc</samp> element 1.420 - is a container for one or several ruby text box (rt element). The 1.421 - position of the <samp>rtc</samp> element in relation to the related 1.422 - <samp>rbc</samp> element is controlled by the <a 1.423 - href="#rubypos">‘<code class=property>ruby-position</code>’</a> 1.424 - property. The two following figures show examples of these complex ruby. 1.425 - 1.426 - <div class=figure> <img 1.427 - alt="Diagram of a group ruby with a full ruby text above and partial ruby text below" 1.428 - height=170 src="images/r-box-g.gif" width=408> 1.429 - <p><b>Figure 3.2.2</b>: Ruby box model (complex ruby with an empty rt 1.430 - element after) 1.431 - </div> 1.432 - 1.433 - <p>In the example above, the ruby text after (below) the ruby bases 1.434 - contains two <samp>rt</samp> elements with the first one being empty, 1.435 - the empty <samp>rt</samp> element corresponds to the first part of the 1.436 - ruby base collection (the first part is identified by the first 1.437 - <samp>rb</samp> element within the <samp> rbc</samp> element). 1.438 - 1.439 - <div class=figure> <img 1.440 - alt="Diagram of a group ruby with a spanning ruby text above and partial ruby text below" 1.441 - height=173 src="images/r-box-h.gif" width=400> 1.442 - <p><b>Figure 3.2.3</b>: Ruby box model (complex ruby with a spanning 1.443 - ruby text element) 1.444 - </div> 1.445 - 1.446 - <p>In the example above, the ruby text before (above) the ruby bases 1.447 - spans the whole ruby base collection. The ruby text after (below) the 1.448 - ruby bases still contain two <samp>rt</samp> elements, one of which is 1.449 - empty. The spanning behavior of <samp>rt</samp> text elements is 1.450 - controlled by the <a 1.451 - href="http://www.w3.org/TR/ruby/#ruby"><samp>rbspan</samp></a> attribute 1.452 - in a way similar to the <samp>colspan</samp> attribute used for table 1.453 - column. 1.454 - 1.455 - <p class=issue><span class=issuehead>Issue: </span> The examples above 1.456 - contain the term ‘<code class=css>group ruby</code>’, which is not 1.457 - used elsewhere in this specification. It appears to be used in a way 1.458 - that is different to the use of the term in JLREQ. I propose to replace 1.459 - it with just ‘<a href="#ruby"><code class=property>ruby</code></a>’. 1.460 - 1.461 - <p class=note><span class=note-label>Note:</span> The visual description 1.462 - of the ruby elements does not refer necessarily to the logical orders of 1.463 - the elements 1.464 - 1.465 - <p>The width of the ruby box is by default determined by its widest child 1.466 - element, whose width in turn is determined by its content. The width of 1.467 - all direct children of the <a href="#ruby"><samp>ruby</samp></a> element 1.468 - is the width of the widest children. In this respect, the ruby box is 1.469 - much like a two or three row <samp>table</samp> element, with the 1.470 - following exceptions: 1.471 - 1.472 - <ul> 1.473 - <li>the ruby box is an inline element, like an image, even though it 1.474 - itself, like a table, is a container of other boxes 1.475 - 1.476 - <li>the equivalent of the cells: the <samp>rb</samp> element and the 1.477 - <samp>rt</samp> text element can only contain inline-level elements. 1.478 - 1.479 - <li>the content of each ‘<code class=property>cell</code>’ is always 1.480 - measured at its maximum width 1.481 - 1.482 - <li>unlike a table, a ruby element doesn't have to fit in a line, the 1.483 - ruby box may be split into several boxes at line boundary, depending of 1.484 - the spanning of the ruby texts. This is however only possible for the 1.485 - complex ruby and can only happen at the boundary of non spanning 1.486 - elements. 1.487 - 1.488 - <li>both the ruby text and the ruby base boxes may overlap with adjacent 1.489 - text (outside of the ruby element) if an appropriate <a 1.490 - href="#rubyover">‘<code class=property>ruby-overhang</code>’</a> 1.491 - parameter is set via CSS. Note however that the actual content of the 1.492 - ruby base cannot overlap with that adjacent text. The distribution of 1.493 - the content of the ruby base within the ruby base box is controlled by 1.494 - the <a href="#rubyalign">‘<code 1.495 - class=property>ruby-align</code>’</a> property. 1.496 - </ul> 1.497 - 1.498 - <p>If the ruby text is not allowed to overhang, then the ruby behaves 1.499 - like a traditional box, i.e. only its contents are rendered within its 1.500 - boundaries and adjacent elements do not cross the box boundary: 1.501 - 1.502 + </dl> 1.503 + 1.504 + <p>The orientation which the above symbols assume in the diagrams 1.505 + corresponds to the orientation that the glyphs they represent are intended 1.506 + to assume when rendered by the user agent. Spacing between these 1.507 + characters in the diagrams is incidental, unless intentionally changed to 1.508 + make a point. 1.509 + 1.510 + <h3 id=ruby-def><span class=secno>1.4. </span> What is ruby?</h3> 1.511 + 1.512 + <p><dfn id=ruby>Ruby</dfn> is the commonly-used name for a run of text that 1.513 + appears alongside another run of text (referred to as the “base”) and 1.514 + serves as an annotation or a pronunciation guide associated with that run 1.515 + of text. 1.516 + 1.517 + <p>The following figures show two examples of Ruby, a simple case and one 1.518 + with more complicated structure. 1.519 + 1.520 + <div class=example> 1.521 + <p>In this first example, a single annotation is used to annotate the base 1.522 + text. 1.523 + 1.524 + <div class=figure> 1.525 + <p><img alt="Example of ruby applied on top of a Japanese expression" 1.526 + src="images/licence.png"> 1.527 + 1.528 + <p class=caption>Example of ruby used in Japanese (simple case) 1.529 + </div> 1.530 + 1.531 + <p>In Japanese typography, this case is sometimes called <i 1.532 + lang=ja>taigo</i> ruby or group-ruby (per-word ruby), because the 1.533 + annotation as a whole is associated with multi-character word (as a 1.534 + whole). 1.535 + </div> 1.536 + 1.537 + <div class=example> 1.538 + <p>In this second example, two levels of annotations are attached to a 1.539 + base sequence: the hiragana characters on top refer to the pronunciation 1.540 + of each of the base kanji characters, while the words “Keio” and 1.541 + “University” on the bottom are annotations describing the English 1.542 + translation. 1.543 + 1.544 + <div class=figure> 1.545 + <p><img 1.546 + alt="Example showing complex ruby with annotation text over and under the base characters" 1.547 + src="images/ruby-univ.gif"> 1.548 + 1.549 + <p class=caption>Complex ruby with annotation text over and under the 1.550 + base characters 1.551 + </div> 1.552 + 1.553 + <p> 1.554 + 1.555 + <p>Notice that to allow correct association between the hiragana 1.556 + characters and their corresponding Kanji base characters, the spacing 1.557 + between these Kanji characters is adjusted. (This happens around the 1.558 + fourth Kanji character in the figure above.) To avoid variable spacing 1.559 + between the Kanji characters in the example above the hiragana 1.560 + annotations can be styled as a <i>collapsed annotation</i>, which will 1.561 + look more like the group-ruby example earlier. However because the 1.562 + base-annotation pairings are recorded in the ruby structure, if the text 1.563 + breaks across lines, the annotation characters will stay correctly paired 1.564 + with their respective base characters. 1.565 + </div> 1.566 + 1.567 + <p><a href="#ruby"><i>Ruby</i></a> formatting as used in Japanese is 1.568 + described in JIS X-4051 <a href="#JIS4051" 1.569 + rel=biblioentry>[JIS4051]<!--{{JIS4051}}--></a> (in Japanese) and in 1.570 + Requirements for Japanese Text Layout <a href="#JLREQ" 1.571 + rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> (in English and Japanese)]. In 1.572 + HTML, ruby structure and markup to represent it is described in the Ruby 1.573 + Markup Extension specification. This module describes the CSS rendering 1.574 + model and formatting controls relevant to ruby layout of such markup. 1.575 + 1.576 + <h2 id=ruby-model><span class=secno>2. </span> Ruby Formatting Model</h2> 1.577 + 1.578 + <p>The CSS ruby model is based on the <a 1.579 + href="http://darobin.github.io/html-ruby/">HTML Ruby Markup Extension</a> 1.580 + and <a href="http://www.w3.org/TR/ruby/">XHTML Ruby Annotation 1.581 + Recommendation</a> <a href="#RUBY" 1.582 + rel=biblioentry>[RUBY]<!--{{RUBY}}--></a>. In this model, a ruby structure 1.583 + consists of one or more <dfn id=ruby-base>ruby base</dfn> elements 1.584 + representing the base (annotated) text, associated with one or more levels 1.585 + of <dfn id=ruby-annotation>ruby annotation</dfn> elements representing the 1.586 + annotations. The structure of ruby is similar to that of a table: there 1.587 + are “rows” (the base text level, each annotation level) and 1.588 + “columns” (each <a href="#ruby-base-box"><i>ruby base</i></a> and its 1.589 + corresponding <a href="#ruby-annotation-box"><i>ruby annotations</i></a>). 1.590 + 1.591 + <p>Consecutive bases and annotations are grouped together into <dfn 1.592 + id=ruby-segments>ruby segments</dfn>. Within a <i>ruby segment</i>, a <a 1.593 + href="#ruby-annotation-box"><i>ruby annotation</i></a> may span multiple 1.594 + <a href="#ruby-base-box"><i>ruby bases<i>. </i></i></a> 1.595 + 1.596 + <p class=note>In HTML, a single <code><ruby></code> element may 1.597 + contain multiple <a href="#ruby-segments"><i>ruby segments</i></a>. (In 1.598 + the XHTML Ruby model, a single <code><ruby></code> element can only 1.599 + contain one <i>ruby segment</i>.) 1.600 + 1.601 + <h3 id=ruby-display><span class=secno>2.1. </span> Ruby-specific ‘<code 1.602 + class=property>display</code>’ property values</h3> 1.603 + 1.604 + <p>For document languages (such as XML applications) that do not have 1.605 + pre-defined ruby elements, authors must map document language elements to 1.606 + ruby elements; this is done with the ‘<code 1.607 + class=property>display</code>’ property. 1.608 + 1.609 + <table class=propdef> 1.610 + <tbody> 1.611 + <tr> 1.612 + <th>Name: 1.613 + 1.614 + <td>display 1.615 + 1.616 + <tr> 1.617 + <th><a href="#values">New Values</a>: 1.618 + 1.619 + <td>ruby | ruby-base | ruby-text | ruby-base-container | 1.620 + ruby-text-container 1.621 + </table> 1.622 + 1.623 + <p>The following new ‘<code class=property>display</code>’ values 1.624 + assign ruby layout roles to an arbitrary element: 1.625 + 1.626 + <dl> 1.627 + <dt>‘<a href="#ruby"><code class=css>ruby</code></a>’ 1.628 + 1.629 + <dd>Specifies that an element generates a <dfn id=ruby-container-box 1.630 + title="ruby container | ruby container box">ruby container box</dfn>. 1.631 + (Corresponds to HTML/XHTML <code><ruby></code> elements.) 1.632 + 1.633 + <dt>‘<code class=css>ruby-base</code>’ 1.634 + 1.635 + <dd>Specifies that an element generates a <dfn id=ruby-base-box 1.636 + title="ruby base box | ruby base">ruby base box</dfn>. (Corresponds to 1.637 + HTML/XHTML <code><rb></code> elements.) 1.638 + 1.639 + <dt>‘<code class=css>ruby-text</code>’ 1.640 + 1.641 + <dd>Specifies that an element generates a <dfn id=ruby-annotation-box 1.642 + title="ruby annotation box | ruby annotation">ruby annotation box</dfn>. 1.643 + (Corresponds to HTML/XHTML <code><rt></code> elements.) 1.644 + 1.645 + <dt>‘<code class=css>ruby-base-container</code>’ 1.646 + 1.647 + <dd>Specifies that an element generates a <dfn id=ruby-base-container-box 1.648 + title="ruby base container box | ruby base container">ruby base container 1.649 + box</dfn>. (Corresponds to XHTML <code><rbc></code> elements; 1.650 + always implied in HTML.) 1.651 + 1.652 + <dt>‘<code class=css>ruby-text-container</code>’ 1.653 + 1.654 + <dd>Specifies that an element generates a <dfn 1.655 + id=ruby-annotation-container-box 1.656 + title="ruby annotation container box | ruby annotation container">ruby 1.657 + annotation container box</dfn>. (Corresponds to HTML/XHTML 1.658 + <code><ruby></code> elements.) 1.659 + </dl> 1.660 + 1.661 + <h3 id=box-fixup><span class=secno>2.2. </span> Anonymous Ruby Box 1.662 + Generation</h3> 1.663 + 1.664 + <p>The CSS model does not require that the document language include 1.665 + elements that correspond to each of these components. Missing parts of the 1.666 + structure are implied through the anonymous box generation rules <a 1.667 + href="http://www.w3.org/TR/CSS21/tables.html#anonymous-boxes">similar to 1.668 + those used to normalize tables</a>. <a href="#CSS21" 1.669 + rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> 1.670 + 1.671 + <ol> 1.672 + <li>Any in-flow block-level boxes directly contained by a <a 1.673 + href="#ruby-container-box"><i>ruby container</i></a>, <a 1.674 + href="#ruby-base-container-box"><i>ruby base container</i></a>, <a 1.675 + href="#ruby-annotation-container-box"><i>ruby annotation 1.676 + container</i></a>, <a href="#ruby-base-box"><i>ruby base box</i></a>, or 1.677 + <a href="#ruby-annotation-box"><i>ruby annotation box</i></a> are forced 1.678 + to be inline-level boxes, and their ‘<code 1.679 + class=property>display</code>’ value computed accordingly. For example, 1.680 + the ‘<code class=property>display</code>’ property of an in-flow 1.681 + element with ‘<code class=css>display: block</code>’ parented by an 1.682 + element with ‘<code class=css>display: ruby-text</code>’ computes to 1.683 + ‘<code class=css>inline-block</code>’. This computation occurs after 1.684 + any intermediary anonymous-box fixup (such as that required by internal 1.685 + table elements). 1.686 + 1.687 + <li>Any consecutive sequence of <a href="#ruby-base-box"><i>ruby 1.688 + bases</i></a> not parented by a <a 1.689 + href="#ruby-base-container-box"><i>ruby base container</i></a> is wrapped 1.690 + in an anonymous <a href="#ruby-base-container-box"><i>ruby base 1.691 + container</i></a>. Similarly, any consecutive sequence of <a 1.692 + href="#ruby-annotation-box"><i>ruby annotations</i></a> not parented by a 1.693 + <a href="#ruby-annotation-container-box"><i>ruby annotation 1.694 + container</i></a> is wrapped in an anonymous <a 1.695 + href="#ruby-annotation-container-box"><i>ruby annotation 1.696 + container</i></a>. 1.697 + 1.698 + <li>Within each <a href="#ruby-base-container-box"><i>ruby base 1.699 + container</i></a>, each sequence of inline-level boxes is wrapped in an 1.700 + anonymous <a href="#ruby-base-box"><i>ruby base box</i></a>. Similarly, 1.701 + within each <a href="#ruby-annotation-container-box"><i>ruby annotation 1.702 + container</i></a>, each sequence of inline-level boxes is wrapped in an 1.703 + anonymous <a href="#ruby-annotation-box"><i>ruby annotation box</i></a>. 1.704 + 1.705 + <li>A sequence of <a href="#ruby-base-container-box"><i>ruby base 1.706 + containers</i></a> and/or <a 1.707 + href="#ruby-annotation-container-box"><i>ruby annotation 1.708 + containers</i></a> not parented by a <a 1.709 + href="#ruby-container-box"><i>ruby container</i></a> is wrapped in an 1.710 + anonymous <a href="#ruby-container-box"><i>ruby container</i></a>. 1.711 + </ol> 1.712 + 1.713 + <p>At this point, all ruby layout structures are properly parented, and the 1.714 + UA can start to associate bases with their annotations. 1.715 + 1.716 + <p class=note> Note that the UA is not required to create any of these 1.717 + anonymous boxes in its internal structures, as long as pairing and layout 1.718 + behaves as if they existed. 1.719 + 1.720 + <h3 id=pairing><span class=secno>2.3. </span> Ruby Pairing and Annotation 1.721 + Levels</h3> 1.722 + 1.723 + <p>Within a ruby structure, each <a href="#ruby-base-box"><i>ruby 1.724 + bases</i></a> are associated with <a href="#ruby-annotation-box"><i>ruby 1.725 + annotations</i></a> and vice versa. A <a href="#ruby-base-box"><i>ruby 1.726 + base</i></a> can be associated with at most one <a 1.727 + href="#ruby-annotation-box"><i>ruby annotation</i></a> per annotation 1.728 + level. If there are multiple annotation levels, it can therefore be 1.729 + associated with multiple <a href="#ruby-annotation-box"><i>ruby 1.730 + annotations</i></a>. A <a href="#ruby-annotation-box"><i>ruby 1.731 + annotation</i></a> is associated with one or more <a 1.732 + href="#ruby-base-box"><i>ruby bases</i></a>; annotations can span multiple 1.733 + bases. 1.734 + 1.735 + <p><dfn id=annotation-pairing>Annotation pairing</dfn> is the process of 1.736 + associating <a href="#ruby-annotation-box"><i>ruby annotations</i></a> 1.737 + with <a href="#ruby-base-box"><i>ruby bases</i></a>. 1.738 + 1.739 + <ol> 1.740 + <li> 1.741 + <p>First, the ruby structure is divided into <a 1.742 + href="#ruby-segments"><i>ruby segments</i></a>, each consisting of a 1.743 + single <a href="#ruby-base-container-box"><i>ruby base container</i></a> 1.744 + followed by one or more <a href="#ruby-annotation-container-box"><i>ruby 1.745 + annotation containers</i></a>. If the first child of a <a 1.746 + href="#ruby-container-box"><i>ruby container</i></a> is a <a 1.747 + href="#ruby-annotation-container-box"><i>ruby annotation 1.748 + container</i></a>, an anonymous, empty <a 1.749 + href="#ruby-base-container-box"><i>ruby base container</i></a> is 1.750 + assumed to exist before it. Similarly, if the <a 1.751 + href="#ruby-container-box"><i>ruby container</i></a> contains 1.752 + consecutive <a href="#ruby-base-container-box"><i>ruby base 1.753 + containers</i></a>, anonymous, empty <a 1.754 + href="#ruby-annotation-container-box"><i>ruby annotation 1.755 + containers</i></a> are assumed to exist between them. The <a 1.756 + href="#ruby-base-container-box"><i>ruby base container</i></a> in each 1.757 + segment is thus associated with each of the <a 1.758 + href="#ruby-annotation-container-box"><i>ruby annotation 1.759 + containers</i></a> in that segment. 1.760 + 1.761 + <p>Each <a href="#ruby-annotation-container-box"><i>ruby annotation 1.762 + containers</i></a> in a <i>ruby segment</i> represents one <dfn id=level 1.763 + title="annotation level | level">level</dfn> of annotation: the first 1.764 + one represents the first level of annotation, the second one represents 1.765 + the second level of annotation, and so on. 1.766 + 1.767 + <li>Within each <i>ruby segment</i>, each <a href="#ruby-base-box"><i>ruby 1.768 + base box</i></a> in the <a href="#ruby-base-container-box"><i>ruby base 1.769 + container</i></a> is paired with one <a 1.770 + href="#ruby-annotation-box"><i>ruby annotation box</i></a> from each <a 1.771 + href="#ruby-annotation-container-box"><i>ruby annotation 1.772 + container</i></a> in its <i>ruby segment</i>. If there are not enough <a 1.773 + href="#ruby-annotation-box"><i>ruby annotations</i></a> in a <a 1.774 + href="#ruby-annotation-container-box"><i>ruby annotation 1.775 + container</i></a>, the last one is associated with any excess <a 1.776 + href="#ruby-base-box"><i>ruby bases</i></a>. (If there are not any in the 1.777 + <a href="#ruby-annotation-container-box"><i>ruby annotation 1.778 + container</i></a>, an anonymous empty one is assumed to exist.) If there 1.779 + are not enough <a href="#ruby-base-box"><i>ruby bases</i></a>, any 1.780 + remaining <a href="#ruby-annotation-box"><i>ruby annotations</i></a> are 1.781 + assumed to be associated with empty, anonymous bases inserted at the end 1.782 + of the <a href="#ruby-base-container-box"><i>ruby base container</i></a>. 1.783 + 1.784 + <p>If an implementation supports ruby markup with explicit spanning (e.g. 1.785 + XHTML Complex Ruby Annotations), it must adjust the pairing rules to 1.786 + pair spanning annotations to multiple bases appropriately. 1.787 + </ol> 1.788 + 1.789 + <p>A this point, ruby “columns” are defined, each represented by a 1.790 + single <a href="#ruby-base-box"><i>ruby base</i></a> and associated with 1.791 + one <a href="#ruby-annotation-box"><i>ruby annotation</i></a> (possibly an 1.792 + empty, anonymous one) from each <a href="#level"><i>annotation 1.793 + level</i></a>. 1.794 + 1.795 + <h4 id=nested-pairing><span class=secno>2.3.1. </span> Nested Ruby</h4> 1.796 + 1.797 + <p>When <a href="#ruby-container-box"><i>ruby containers</i></a> are 1.798 + nested, pairing begins with the deepest <a 1.799 + href="#ruby-container-box"><i>ruby container</i></a>, then expands out, 1.800 + treating each <a href="#ruby-container-box"><i>ruby container</i></a> 1.801 + nested within another <a href="#ruby-container-box"><i>ruby 1.802 + container</i></a> as a <a href="#ruby-base-box"><i>ruby base</i></a>, and 1.803 + associating each <a href="#ruby-annotation-box"><i>ruby annotation</i></a> 1.804 + associated with the nested <a href="#ruby-container-box"><i>ruby 1.805 + container</i></a> as being associated with (spanning) all of its <a 1.806 + href="#ruby-base-box"><i>ruby bases</i></a>. 1.807 + 1.808 + <p>Using nested <a href="#ruby-container-box"><i>ruby containers</i></a> 1.809 + thus allows the representation of complex spanning relationships. 1.810 + 1.811 + <p class=issue>This shouldn't belong in Level 1. But HTML5 allows it, so we 1.812 + have to handle it. Yay HTML5. 1.813 + 1.814 + <h3 id=box-model><span class=secno>2.4. </span> Generating Ruby Structure</h3> 1.815 + 1.816 + <p> 1.817 + 1.818 + <h3 id=box-model><span class=secno>2.5. </span> Ruby box model</h3> 1.819 + 1.820 + <p>In the following description, the elements specified by Ruby Annotation 1.821 + <a href="#RUBY" rel=biblioentry>[RUBY]<!--{{RUBY}}--></a> are used to 1.822 + describe the box model. As mentioned earlier, a user agent can obtain the 1.823 + same results by using the Ruby specific ‘<code 1.824 + class=property>display</code>’ property values. 1.825 + 1.826 + <p>For a user agent that supports the ruby markup, the ruby structure 1.827 + consists of three or more boxes. The outermost container is the <a 1.828 + href="http://www.w3.org/TR/ruby/#ruby"><samp>ruby</samp></a> element 1.829 + itself. In the simple case, it is a container for two non-overlapping 1.830 + boxes: the ruby text box (<a 1.831 + href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element) and the 1.832 + ruby base box (<a href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> 1.833 + element). The positioning of these two boxes relative to each other is 1.834 + controlled by the <a href="#rubypos">‘<code 1.835 + class=property>ruby-position</code>’</a> property. 1.836 + 1.837 + <div class=figure> <img 1.838 + alt="Diagram of the ruby box model consisting of two boxes, one on top of the other, enclosed within a third box representing the ruby element" 1.839 + class=example height=93 src="images/r-box-t.gif" width=223> 1.840 + <p><b>Figure 3.2.1</b>: Ruby box model (simple case) 1.841 + </div> 1.842 + 1.843 + <p>In the case of complex ruby, the ruby element is a container for two or 1.844 + three non-overlapping boxes: one ruby base collection (<a 1.845 + href="http://www.w3.org/TR/ruby/#rbc"><samp>rbc</samp></a> element), and 1.846 + one or two ruby text collections (<a 1.847 + href="http://www.w3.org/TR/ruby/#rtc"><samp>rtc</samp></a> element). The 1.848 + <samp>rbc</samp> element is itself a container for one or several ruby 1.849 + base box (<samp>rb</samp> element), while each <samp>rtc</samp> element is 1.850 + a container for one or several ruby text box (rt element). The position of 1.851 + the <samp>rtc</samp> element in relation to the related <samp>rbc</samp> 1.852 + element is controlled by the <a href="#rubypos">‘<code 1.853 + class=property>ruby-position</code>’</a> property. The two following 1.854 + figures show examples of these complex ruby. 1.855 + 1.856 + <div class=figure> <img 1.857 + alt="Diagram of a group ruby with a full ruby text above and partial ruby text below" 1.858 + height=170 src="images/r-box-g.gif" width=408> 1.859 + <p><b>Figure 3.2.2</b>: Ruby box model (complex ruby with an empty rt 1.860 + element after) 1.861 + </div> 1.862 + 1.863 + <p>In the example above, the ruby text after (below) the ruby bases 1.864 + contains two <samp>rt</samp> elements with the first one being empty, the 1.865 + empty <samp>rt</samp> element corresponds to the first part of the ruby 1.866 + base collection (the first part is identified by the first <samp>rb</samp> 1.867 + element within the <samp> rbc</samp> element). 1.868 + 1.869 + <div class=figure> <img 1.870 + alt="Diagram of a group ruby with a spanning ruby text above and partial ruby text below" 1.871 + height=173 src="images/r-box-h.gif" width=400> 1.872 + <p><b>Figure 3.2.3</b>: Ruby box model (complex ruby with a spanning ruby 1.873 + text element) 1.874 + </div> 1.875 + 1.876 + <p>In the example above, the ruby text before (above) the ruby bases spans 1.877 + the whole ruby base collection. The ruby text after (below) the ruby bases 1.878 + still contain two <samp>rt</samp> elements, one of which is empty. The 1.879 + spanning behavior of <samp>rt</samp> text elements is controlled by the <a 1.880 + href="http://www.w3.org/TR/ruby/#ruby"><samp>rbspan</samp></a> attribute 1.881 + in a way similar to the <samp>colspan</samp> attribute used for table 1.882 + column. 1.883 + 1.884 + <p class=issue><span class=issuehead>Issue: </span> The examples above 1.885 + contain the term ‘<code class=css>group ruby</code>’, which is not 1.886 + used elsewhere in this specification. It appears to be used in a way that 1.887 + is different to the use of the term in JLREQ. I propose to replace it with 1.888 + just ‘<a href="#ruby"><code class=property>ruby</code></a>’. 1.889 + 1.890 + <p class=note><span class=note-label>Note:</span> The visual description of 1.891 + the ruby elements does not refer necessarily to the logical orders of the 1.892 + elements 1.893 + 1.894 + <p>The width of the ruby box is by default determined by its widest child 1.895 + element, whose width in turn is determined by its content. The width of 1.896 + all direct children of the <a href="#ruby"><samp>ruby</samp></a> element 1.897 + is the width of the widest children. In this respect, the ruby box is much 1.898 + like a two or three row <samp>table</samp> element, with the following 1.899 + exceptions: 1.900 + 1.901 + <ul> 1.902 + <li>the ruby box is an inline element, like an image, even though it 1.903 + itself, like a table, is a container of other boxes 1.904 + 1.905 + <li>the equivalent of the cells: the <samp>rb</samp> element and the 1.906 + <samp>rt</samp> text element can only contain inline-level elements. 1.907 + 1.908 + <li>the content of each ‘<code class=property>cell</code>’ is always 1.909 + measured at its maximum width 1.910 + 1.911 + <li>unlike a table, a ruby element doesn't have to fit in a line, the ruby 1.912 + box may be split into several boxes at line boundary, depending of the 1.913 + spanning of the ruby texts. This is however only possible for the complex 1.914 + ruby and can only happen at the boundary of non spanning elements. 1.915 + 1.916 + <li>both the ruby text and the ruby base boxes may overlap with adjacent 1.917 + text (outside of the ruby element) if an appropriate <a 1.918 + href="#rubyover">‘<code class=property>ruby-overhang</code>’</a> 1.919 + parameter is set via CSS. Note however that the actual content of the 1.920 + ruby base cannot overlap with that adjacent text. The distribution of the 1.921 + content of the ruby base within the ruby base box is controlled by the <a 1.922 + href="#rubyalign">‘<code class=property>ruby-align</code>’</a> 1.923 + property. 1.924 + </ul> 1.925 + 1.926 + <p>If the ruby text is not allowed to overhang, then the ruby behaves like 1.927 + a traditional box, i.e. only its contents are rendered within its 1.928 + boundaries and adjacent elements do not cross the box boundary: 1.929 + 1.930 + <div class=figure> 1.931 + <p><img 1.932 + alt="Diagram showing the ruby boxes interacting with adjacent text" 1.933 + class=example height=91 src="images/ro-n.gif" width=220> 1.934 + 1.935 + <p><b>Figure 3.2.4</b>: Simple ruby whose text is not allowed to overhang 1.936 + adjacent text 1.937 + </div> 1.938 + 1.939 + <p>However, if ruby text is allowed to overhang adjacent elements and it 1.940 + happens to be wider than its base, then the adjacent content is partially 1.941 + rendered within the area of the ruby base box, while the ruby text may be 1.942 + partially overlapping with the upper blank parts of the adjacent content: 1.943 + 1.944 + <div class=figure> 1.945 + <p><img 1.946 + alt="Diagram showing the ruby boxes interacting with adjacent text" 1.947 + class=example height=91 src="images/ro-a.gif" width=177> 1.948 + 1.949 + <p><b>Figure 3.2.5</b>: Simple ruby whose text is allowed to overhang 1.950 + adjacent text 1.951 + </div> 1.952 + 1.953 + <p>The ruby text related to a ruby base can never overhang another ruby 1.954 + base. 1.955 + 1.956 + <p>The alignment of the contents of the base or the ruby text is not 1.957 + affected by the overhanging behavior. The alignment is achieved the same 1.958 + way regardless of the overhang behavior setting and it is computed before 1.959 + the space available for overlap is determined. It is controlled by the <a 1.960 + href="#rubyalign">‘<code class=property>ruby-align</code>’</a> 1.961 + property. 1.962 + 1.963 + <p>The exact circumstances in which the ruby text will overhang other 1.964 + elements, and to what degree it will do so, will be controlled by the <a 1.965 + href="#rubyover">‘<code class=property>ruby-overhang</code>’</a> 1.966 + property. 1.967 + 1.968 + <p>This entire logic applies the same way in vertical ideographic layout, 1.969 + only the dimension in which it works in such a layout is vertical, instead 1.970 + of horizontal. 1.971 + 1.972 + <p class=note><span class=note-label>Note:</span> Because the purpose of 1.973 + the XHTML <samp>rp</samp> element <a href="#RUBY" 1.974 + rel=biblioentry>[RUBY]<!--{{RUBY}}--></a> is to allow pre-existing user 1.975 + agents to parenthesize ruby text content, an XHTML user agent should use a 1.976 + styling rule for these elements that avoids rendering them such as 1.977 + <samp>rp {display: none}</samp>. 1.978 + 1.979 + <h3 id=ruby-line-height><span class=secno>2.6. </span> Ruby box and line 1.980 + stacking</h3> 1.981 + 1.982 + <p>The interaction of the ruby box and line stacking is controlled by the 1.983 + ‘<code class=property>line-stacking-ruby</code>’ property described in 1.984 + the CSS3 Line Module. That property takes two values: ‘<code 1.985 + class=property>include-ruby</code>’ and ‘<code class=css>exclude-ruby. 1.986 + Depending on the property value, the ruby box is considered or excluded 1.987 + for line stacking. Even if the ruby box is considered for line stacking, 1.988 + some values of the </code>’line-stacking-strategy' property (also 1.989 + described in the CSS3 Line module) can still create occurrences where a 1.990 + the ruby box will eventually be ignored (e.g. case where the ‘<code 1.991 + class=property>line-stacking-strategy</code>’ value is ‘<code 1.992 + class=property>block-line-height</code>’). 1.993 + 1.994 + <p>In the following figure, each line box is shown with leading space 1.995 + distributed before and after the two text segments (‘<code 1.996 + class=css>Previous line</code>’ and ‘<a href="#ruby-base-box"><code 1.997 + class=css>Ruby base</code></a>’); the dotted lines show the line box for 1.998 + each line. The ‘<code class=property>line-stacking-ruby</code>’ 1.999 + property is set to ‘<code class=property>exclude-ruby</code>’. The 1.1000 + achieved effect is that the ruby box does not affect the line to line 1.1001 + spacing. It is however the responsibility of the style author to avoid 1.1002 + ‘<code class=property>bleeding</code>’ effects between the ruby text 1.1003 + and the surrounding text of images. 1.1004 + 1.1005 + <div class=figure> 1.1006 + <p> <img alt="Diagram showing the ruby text using 2 half leading" 1.1007 + class=example height=138 src="images/rlh-a.gif" width=210> 1.1008 + 1.1009 + <p><b>Figure 3.3.1</b>: Excluded Ruby text 1.1010 + </div> 1.1011 + 1.1012 + <p>In the following figure, the line boxes have no extra leading space. The 1.1013 + ‘<code class=property>line-stacking-ruby</code>’ property is set to 1.1014 + ‘<code class=property>include-ruby</code>’ and the ‘<code 1.1015 + class=property>line-stacking-strategy</code>’ property is set to a value 1.1016 + where inline boxes are considered for line stacking. In this case, the 1.1017 + line box with the ruby text is affected and has its ‘<code 1.1018 + class=property>stack-height</code>’ increased by the amount necessary to 1.1019 + fit the ruby text. 1.1020 + 1.1021 + <div class=figure> 1.1022 + <p> <img alt="Diagram showing the ruby text expanding above base text" 1.1023 + class=example height=111 src="images/rlh-b.gif" width=210> 1.1024 + 1.1025 + <p><b>Figure 3.3.2</b>: Ruby text increasing line height 1.1026 + </div> 1.1027 + 1.1028 + <p>This mechanism allows rendering of evenly spaced lines of text within a 1.1029 + block-level element, whether a line contains ruby or not. The authors need 1.1030 + only to set for the block-level element a line height value larger than 1.1031 + the computed line-height of the largest ruby element within the block. 1.1032 + 1.1033 + <h3 id=ruby-line-breaking><span class=secno>2.7. </span> Ruby box and line 1.1034 + breaking</h3> 1.1035 + 1.1036 + <p>When a ruby falls at the end of a line where there is not sufficient 1.1037 + room for the entire ruby to fit on the line, the complex ruby may be 1.1038 + broken at locations where boxes of the ruby container align. Some examples 1.1039 + are provided below to provide more clarity. 1.1040 + 1.1041 + <p> <img 1.1042 + alt="Diagram showing the line breaking opportunity in a complex ruby" 1.1043 + class=example height=201 src="images/r-break-a.gif" width=408> 1.1044 + 1.1045 + <p><b>Figure 3.4.1</b>: Complex ruby line breaking opportunity 1.1046 + 1.1047 + <p> <img 1.1048 + alt="Diagram showing the line breaking opportunity in a "Bopomofo" ruby" 1.1049 + class=example height=90 src="images/r-break-b.gif" width=300> 1.1050 + 1.1051 + <p><b>Figure 3.4.1</b>: "Bopomofo" ruby line breaking opportunity 1.1052 + 1.1053 + <p class=issue><span class=issuehead>Issue: </span> Line breaks should 1.1054 + only be allowed within ruby if the ruby base text can be broken at that 1.1055 + point. E.g. if complex Ruby is used to annotate the two morphemes of 1.1056 + "butterfly", the fact that we have added ruby annotations should 1.1057 + not cause a line breaking opportunity to be present between 1.1058 + "butter" and "fly" 1.1059 + 1.1060 + <h2 id=ruby-props><span class=secno>3. </span> Ruby Properties</h2> 1.1061 + 1.1062 + <p>The following properties are introduced to control ruby positioning and 1.1063 + alignment. 1.1064 + 1.1065 + <h3 id=rubypos><span class=secno>3.1. </span> Ruby positioning: the ‘<a 1.1066 + href="#ruby-position"><code class=property>ruby-position</code></a>’ 1.1067 + property</h3> 1.1068 + 1.1069 + <table class=propdef> 1.1070 + <tbody> 1.1071 + <tr> 1.1072 + <th>Name: 1.1073 + 1.1074 + <td><dfn id=ruby-position>ruby-position</dfn> 1.1075 + 1.1076 + <tr> 1.1077 + <th><a href="#values">Value</a>: 1.1078 + 1.1079 + <td>[ over | under | inter-character ] && [ right | left ] 1.1080 + 1.1081 + <tr> 1.1082 + <th>Initial: 1.1083 + 1.1084 + <td>over right 1.1085 + 1.1086 + <tr> 1.1087 + <th>Applies to: 1.1088 + 1.1089 + <td>ruby annotation containers 1.1090 + 1.1091 + <tr> 1.1092 + <th>Inherited: 1.1093 + 1.1094 + <td>yes 1.1095 + 1.1096 + <tr> 1.1097 + <th>Percentages: 1.1098 + 1.1099 + <td>N/A 1.1100 + 1.1101 + <tr> 1.1102 + <th>Media: 1.1103 + 1.1104 + <td>visual 1.1105 + 1.1106 + <tr> 1.1107 + <th>Computed value: 1.1108 + 1.1109 + <td>specified value 1.1110 + 1.1111 + <tr> 1.1112 + <th>Animatable: 1.1113 + 1.1114 + <td>no 1.1115 + 1.1116 + <tr> 1.1117 + <th>Canonical order: 1.1118 + 1.1119 + <td><abbr title="follows order of property value definition">per 1.1120 + grammar</abbr> 1.1121 + </table> 1.1122 + 1.1123 + <p>This property controls position of the ruby text with respect to its 1.1124 + base. Values have the following meanings: 1.1125 + 1.1126 + <p class=issue><span class=issuehead>Issue-107: </span> Roland Steiner has 1.1127 + requested the addition of an auto value as default. See <a 1.1128 + href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=ruby-position%3A+undesirable+default+value+%27before%27+for+complex+ruby&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&period_month=&period_year=&index-grp=Public__FULL&index-type=t&type-index=www-style&resultsperpage=20&sortby=date">this 1.1129 + thread</a> and <a 1.1130 + href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=Styling+of+complex+Ruby&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&period_month=&period_year=&index-grp=Public__FULL&index-type=t&type-index=public-i18n-core&resultsperpage=20&sortby=date">this 1.1131 + one</a>. 1.1132 + 1.1133 + <dl> 1.1134 + <dt><dfn id=over title="ruby-position:over">‘<code 1.1135 + class=css>over</code>’</dfn> 1.1136 + 1.1137 + <dd>The ruby text appears <i>over</i> the base in horizontal text. 1.1138 <div class=figure> 1.1139 <p><img 1.1140 - alt="Diagram showing the ruby boxes interacting with adjacent text" 1.1141 - class=example height=91 src="images/ro-n.gif" width=220> 1.1142 - 1.1143 - <p><b>Figure 3.2.4</b>: Simple ruby whose text is not allowed to 1.1144 - overhang adjacent text 1.1145 + alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing above the base" 1.1146 + src="images/shinkansen-top.gif"> 1.1147 + 1.1148 + <p class=caption>Ruby over Japanese base text in horizontal layout 1.1149 </div> 1.1150 1.1151 - <p>However, if ruby text is allowed to overhang adjacent elements and it 1.1152 - happens to be wider than its base, then the adjacent content is 1.1153 - partially rendered within the area of the ruby base box, while the ruby 1.1154 - text may be partially overlapping with the upper blank parts of the 1.1155 - adjacent content: 1.1156 - 1.1157 + <dt><dfn id=right title="ruby-position:right">‘<code 1.1158 + class=css>right</code>’</dfn> 1.1159 + 1.1160 + <dd>The ruby text appears on the right side of the base in vertical text. 1.1161 <div class=figure> 1.1162 <p><img 1.1163 - alt="Diagram showing the ruby boxes interacting with adjacent text" 1.1164 - class=example height=91 src="images/ro-a.gif" width=177> 1.1165 - 1.1166 - <p><b>Figure 3.2.5</b>: Simple ruby whose text is allowed to overhang 1.1167 - adjacent text 1.1168 + alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the right of the base" 1.1169 + src="images/shinkansen-right.gif" width=33> 1.1170 + 1.1171 + <p class=caption>Ruby to the right of Japanese base text in vertical 1.1172 + layout 1.1173 </div> 1.1174 1.1175 - <p>The ruby text related to a ruby base can never overhang another ruby 1.1176 - base. 1.1177 - 1.1178 - <p>The alignment of the contents of the base or the ruby text is not 1.1179 - affected by the overhanging behavior. The alignment is achieved the same 1.1180 - way regardless of the overhang behavior setting and it is computed 1.1181 - before the space available for overlap is determined. It is controlled 1.1182 - by the <a href="#rubyalign">‘<code 1.1183 - class=property>ruby-align</code>’</a> property. 1.1184 - 1.1185 - <p>The exact circumstances in which the ruby text will overhang other 1.1186 - elements, and to what degree it will do so, will be controlled by the <a 1.1187 - href="#rubyover">‘<code class=property>ruby-overhang</code>’</a> 1.1188 - property. 1.1189 - 1.1190 - <p>This entire logic applies the same way in vertical ideographic layout, 1.1191 - only the dimension in which it works in such a layout is vertical, 1.1192 - instead of horizontal. 1.1193 - 1.1194 - <p class=note><span class=note-label>Note:</span> Because the purpose of 1.1195 - the XHTML <samp>rp</samp> element <a href="#RUBY" 1.1196 - rel=biblioentry>[RUBY]<!--{{RUBY}}--></a> is to allow pre-existing user 1.1197 - agents to parenthesize ruby text content, an XHTML user agent should use 1.1198 - a styling rule for these elements that avoids rendering them such as 1.1199 - <samp>rp {display: none}</samp>. 1.1200 - 1.1201 - <h3 id=ruby-line-height><span class=secno>2.6. </span> Ruby box and line 1.1202 - stacking</h3> 1.1203 - 1.1204 - <p>The interaction of the ruby box and line stacking is controlled by the 1.1205 - ‘<code class=property>line-stacking-ruby</code>’ property described 1.1206 - in the CSS3 Line Module. That property takes two values: ‘<code 1.1207 - class=property>include-ruby</code>’ and ‘<code 1.1208 - class=css>exclude-ruby. Depending on the property value, the ruby box is 1.1209 - considered or excluded for line stacking. Even if the ruby box is 1.1210 - considered for line stacking, some values of the 1.1211 - </code>’line-stacking-strategy' property (also described in the CSS3 1.1212 - Line module) can still create occurrences where a the ruby box will 1.1213 - eventually be ignored (e.g. case where the ‘<code 1.1214 - class=property>line-stacking-strategy</code>’ value is ‘<code 1.1215 - class=property>block-line-height</code>’). 1.1216 - 1.1217 - <p>In the following figure, each line box is shown with leading space 1.1218 - distributed before and after the two text segments (‘<code 1.1219 - class=css>Previous line</code>’ and ‘<a href="#ruby-base-box"><code 1.1220 - class=css>Ruby base</code></a>’); the dotted lines show the line box 1.1221 - for each line. The ‘<code class=property>line-stacking-ruby</code>’ 1.1222 - property is set to ‘<code class=property>exclude-ruby</code>’. The 1.1223 - achieved effect is that the ruby box does not affect the line to line 1.1224 - spacing. It is however the responsibility of the style author to avoid 1.1225 - ‘<code class=property>bleeding</code>’ effects between the ruby text 1.1226 - and the surrounding text of images. 1.1227 - 1.1228 + <dt><dfn id=under title="ruby-position:under">‘<code 1.1229 + class=css>under</code>’</dfn> 1.1230 + 1.1231 + <dd>The ruby text appears under the base in horizontal text. This is a 1.1232 + relatively rare setting used in ideographic East Asian writing systems, 1.1233 + most easily found in educational text. 1.1234 <div class=figure> 1.1235 - <p> <img alt="Diagram showing the ruby text using 2 half leading" 1.1236 - class=example height=138 src="images/rlh-a.gif" width=210> 1.1237 - 1.1238 - <p><b>Figure 3.3.1</b>: Excluded Ruby text 1.1239 + <p><img 1.1240 + alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing below the base" 1.1241 + src="images/shinkansen-bottom.gif"> 1.1242 + 1.1243 + <p class=caption>Ruby under Japanese base text in horizontal layout 1.1244 </div> 1.1245 1.1246 - <p>In the following figure, the line boxes have no extra leading space. 1.1247 - The ‘<code class=property>line-stacking-ruby</code>’ property is set 1.1248 - to ‘<code class=property>include-ruby</code>’ and the ‘<code 1.1249 - class=property>line-stacking-strategy</code>’ property is set to a 1.1250 - value where inline boxes are considered for line stacking. In this case, 1.1251 - the line box with the ruby text is affected and has its ‘<code 1.1252 - class=property>stack-height</code>’ increased by the amount necessary 1.1253 - to fit the ruby text. 1.1254 - 1.1255 + <dt><dfn id=left title="ruby-position:left">‘<code 1.1256 + class=css>left</code>’</dfn> 1.1257 + 1.1258 + <dd>The ruby text appears on the left side of the base in vertical text. 1.1259 <div class=figure> 1.1260 - <p> <img alt="Diagram showing the ruby text expanding above base text" 1.1261 - class=example height=111 src="images/rlh-b.gif" width=210> 1.1262 - 1.1263 - <p><b>Figure 3.3.2</b>: Ruby text increasing line height 1.1264 + <p><img 1.1265 + alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the left of the base" 1.1266 + src="images/shinkansen-left.gif"> 1.1267 + 1.1268 + <p class=caption>Ruby to the left of Japanese base text in vertical 1.1269 + layout 1.1270 </div> 1.1271 1.1272 - <p>This mechanism allows rendering of evenly spaced lines of text within 1.1273 - a block-level element, whether a line contains ruby or not. The authors 1.1274 - need only to set for the block-level element a line height value larger 1.1275 - than the computed line-height of the largest ruby element within the 1.1276 - block. 1.1277 - 1.1278 - <h3 id=ruby-line-breaking><span class=secno>2.7. </span> Ruby box and 1.1279 - line breaking</h3> 1.1280 - 1.1281 - <p>When a ruby falls at the end of a line where there is not sufficient 1.1282 - room for the entire ruby to fit on the line, the complex ruby may be 1.1283 - broken at locations where boxes of the ruby container align. Some 1.1284 - examples are provided below to provide more clarity. 1.1285 - 1.1286 - <p> <img 1.1287 - alt="Diagram showing the line breaking opportunity in a complex ruby" 1.1288 - class=example height=201 src="images/r-break-a.gif" width=408> 1.1289 - 1.1290 - <p><b>Figure 3.4.1</b>: Complex ruby line breaking opportunity 1.1291 - 1.1292 - <p> <img 1.1293 - alt="Diagram showing the line breaking opportunity in a "Bopomofo" ruby" 1.1294 - class=example height=90 src="images/r-break-b.gif" width=300> 1.1295 - 1.1296 - <p><b>Figure 3.4.1</b>: "Bopomofo" ruby line breaking opportunity 1.1297 - 1.1298 - <p class=issue><span class=issuehead>Issue: </span> Line breaks should 1.1299 - only be allowed within ruby if the ruby base text can be broken at that 1.1300 - point. E.g. if complex Ruby is used to annotate the two morphemes of 1.1301 - "butterfly", the fact that we have added ruby annotations 1.1302 - should not cause a line breaking opportunity to be present between 1.1303 - "butter" and "fly" 1.1304 - 1.1305 - <h2 id=ruby-props><span class=secno>3. </span> Ruby Properties</h2> 1.1306 - 1.1307 - <h3 id=rubypos><span class=secno>3.1. </span> Ruby positioning: the ‘<a 1.1308 - href="#ruby-position"><code class=property>ruby-position</code></a>’ 1.1309 - property</h3> 1.1310 - 1.1311 - <table class=propdef> 1.1312 - <tbody> 1.1313 - <tr> 1.1314 - <th>Name: 1.1315 - 1.1316 - <td><dfn id=ruby-position>ruby-position</dfn> 1.1317 - 1.1318 - <tr> 1.1319 - <th><a href="#values">Value</a>: 1.1320 - 1.1321 - <td>[ over | under | inter-character ] && [ right | left ] 1.1322 - 1.1323 - <tr> 1.1324 - <th>Initial: 1.1325 - 1.1326 - <td>over right 1.1327 - 1.1328 - <tr> 1.1329 - <th>Applies to: 1.1330 - 1.1331 - <td>the parent of elements with display: ruby-text. 1.1332 - 1.1333 - <tr> 1.1334 - <th>Inherited: 1.1335 - 1.1336 - <td>yes 1.1337 - 1.1338 - <tr> 1.1339 - <th>Percentages: 1.1340 - 1.1341 - <td>N/A 1.1342 - 1.1343 - <tr> 1.1344 - <th>Media: 1.1345 - 1.1346 - <td>visual 1.1347 - 1.1348 - <tr> 1.1349 - <th>Computed value: 1.1350 - 1.1351 - <td>specified value (except for initial and inherit) 1.1352 - 1.1353 - <tr> 1.1354 - <th>Animatable: 1.1355 - 1.1356 - <td>no 1.1357 - 1.1358 - <tr> 1.1359 - <th>Canonical order: 1.1360 - 1.1361 - <td><abbr title="follows order of property value definition">per 1.1362 - grammar</abbr> 1.1363 - </table> 1.1364 - 1.1365 - <p class=issue><span class=issuehead>Issue: </span> We replaced ‘<code 1.1366 - class=property>right</code>’ with ‘<code 1.1367 - class=property>inter-character</code>’, since that was its original 1.1368 - intended purpose and such removes potential ambiguity with ‘<code 1.1369 - class=property>inline</code>’ or ‘<code 1.1370 - class=property>before</code>’. Bopomofo ruby needs special handling by 1.1371 - the implementation, if ruby is to always appear to the right. (Note that 1.1372 - the user may also choose to position bopomofo ruby before the base, in 1.1373 - which case they would use the normal ‘<code 1.1374 - class=property>before</code>’ setting.) 1.1375 - 1.1376 - <p>This property is used by the parent of elements with display: 1.1377 - ruby-text to control the position of the ruby text with respect to its 1.1378 - base. Such parents are typically either the <a 1.1379 - href="#ruby"><samp>ruby</samp></a> element itself (simple ruby) or the 1.1380 - <samp>rtc</samp> element (complex ruby). This assures that all parts of 1.1381 - a <samp>rtc</samp> element will be displayed in the same position. 1.1382 - Possible values: 1.1383 - 1.1384 - <p class=issue><span class=issuehead>Issue-107: </span> Roland Steiner 1.1385 - has requested the addition of an auto value as default. See <a 1.1386 - href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=ruby-position%3A+undesirable+default+value+%27before%27+for+complex+ruby&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&period_month=&period_year=&index-grp=Public__FULL&index-type=t&type-index=www-style&resultsperpage=20&sortby=date">this 1.1387 - thread</a> and <a 1.1388 - href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=Styling+of+complex+Ruby&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&period_month=&period_year=&index-grp=Public__FULL&index-type=t&type-index=public-i18n-core&resultsperpage=20&sortby=date">this 1.1389 - one</a>. 1.1390 - 1.1391 - <dl> 1.1392 - <dt><dfn id=over title="ruby-position:over">‘<code 1.1393 - class=css>over</code>’</dfn> 1.1394 - 1.1395 - <dd>The ruby text appears over the base in horizontal text. This is the 1.1396 - most common setting used in ideographic East Asian writing systems. 1.1397 - This is the initial value. 1.1398 - <div class=figure> 1.1399 - <p> <img 1.1400 - alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing above the base" 1.1401 - height=33 src="images/shinkansen-top.gif" width=140> 1.1402 - 1.1403 - <p><b>Figure 4.1.1</b>: Top ruby in horizontal layout applied to 1.1404 - Japanese text 1.1405 - </div> 1.1406 - 1.1407 - <dt><dfn id=right title="ruby-position:right">‘<code 1.1408 - class=css>right</code>’</dfn> 1.1409 - 1.1410 - <dd>The ruby text appears on the right side of the base in vertical 1.1411 - text. 1.1412 - <div class=figure> 1.1413 - <p> <img 1.1414 - alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the right of the base" 1.1415 - height=141 src="images/shinkansen-right.gif" width=33> 1.1416 - 1.1417 - <p><b>Figure 4.1.2</b>: Top ruby in vertical ideographic layout 1.1418 - applied to Japanese text 1.1419 - </div> 1.1420 - 1.1421 - <dt><dfn id=under title="ruby-position:under">‘<code 1.1422 - class=css>under</code>’</dfn> 1.1423 - 1.1424 - <dd>The ruby text appears under the base in horizontal text. This is a 1.1425 - relatively rare setting used in ideographic East Asian writing systems, 1.1426 - most easily found in educational text. 1.1427 - <div class=figure> 1.1428 - <p> <img 1.1429 - alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing below the base" 1.1430 - height=36 src="images/shinkansen-bottom.gif" width=142> 1.1431 - 1.1432 - <p><b>Figure 4.1.3</b>: Bottom ruby in horizontal layout applied to 1.1433 - Japanese text 1.1434 - </div> 1.1435 - 1.1436 - <dt><dfn id=left title="ruby-position:left">‘<code 1.1437 - class=css>left</code>’</dfn> 1.1438 - 1.1439 - <dd>The ruby text appears on the left side of the base in vertical text. 1.1440 - 1.1441 - <div class=figure> 1.1442 - <p> <img 1.1443 - alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the left of the base" 1.1444 - height=141 src="images/shinkansen-left.gif" width=37> 1.1445 - 1.1446 - <p><b>Figure 4.1.4</b>: Bottom ruby in vertical ideographic layout 1.1447 - applied to Japanese text 1.1448 - </div> 1.1449 - 1.1450 - <dt><dfn id=inter-character 1.1451 - title="ruby-position:inter-character">‘<code 1.1452 - class=css>inter-character</code>’</dfn> 1.1453 - 1.1454 - <dd> 1.1455 - <p class=issue><span class=issuehead>Issue: </span> We replaced 1.1456 - ‘<code class=property>right</code>’ with ‘<code 1.1457 - class=property>inter-character</code>’, since that was its original 1.1458 - intended purpose and such removes potential ambiguity with ‘<code 1.1459 - class=property>inline</code>’ or ‘<code 1.1460 - class=property>before</code>’. Bopomofo ruby needs special handling 1.1461 - by the implementation, if ruby is to always appear to the right. (Note 1.1462 - that the user may also choose to position bopomofo ruby before the 1.1463 - base, in which case they would use the normal ‘<code 1.1464 - class=property>before</code>’ setting.) See <a 1.1465 - href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20Vertical+layout+not+enough+for+bopomofo&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">this 1.1466 - thread</a> following a request from the i18n WG. 1.1467 - 1.1468 - <p>The ruby text appears on the right of the base in horizontal text. 1.1469 - 1.1470 - <p>This value is provided for the special case of traditional Chinese 1.1471 - as used especially in Taiwan: ruby (made of <a 1.1472 - href="#g-bopomofo"><span lang=zh>bopomofo</span></a> glyphs) in that 1.1473 - context appears vertically along the right side of the base glyph, 1.1474 - even when the layout of the base characters is horizontal: 1.1475 - 1.1476 - <div class=figure> 1.1477 - <p><img alt="Example of Taiwanese-style ruby" height=42 1.1478 - src="images/bopomofo.gif" width=138> 1.1479 - 1.1480 - <p><b>Figure 4.1.5</b>: "<span lang=zh>Bopomofo</span>" ruby in 1.1481 - traditional Chinese (ruby text shown in blue for clarity) in 1.1482 - horizontal layout 1.1483 - </div> 1.1484 - 1.1485 - <p class=note><span class=note-label>Note:</span> The bopomofo 1.1486 - transcription is written in the normal way as part of the ruby text. 1.1487 - The user agent is responsible for ensuring the correct relative 1.1488 - alignment and positioning of the glyphs, including those corresponding 1.1489 - to the tone marks, when displaying. Tone marks are spacing characters 1.1490 - that occur in memory at the end of the ruby text for each base 1.1491 - character. They are usually displayed in a separate column to the 1.1492 - right of the bopomofo characters, and the height of the tone mark 1.1493 - depends on the number of characters in the syllable. One tone mark, 1.1494 - however, is placed above the bopomofo, not to the right of it. 1.1495 - 1.1496 - <p class=note><span class=note-label>Note:</span> To make bopomofo 1.1497 - annotations appear before or after the base text, like annotations for 1.1498 - most other East Asian writing systems, use the ‘<code 1.1499 - class=property>before</code>’ and ‘<code 1.1500 - class=property>after</code>’ values of ruby-position. 1.1501 - 1.1502 - <p>It is not defined how a user-agent should handle ruby text that is 1.1503 - not bopomofo when the value of ruby-position is set to ‘<code 1.1504 - class=property>inter-character</code>’.</p> 1.1505 - <!-- See Taiwanese requirements doc for EPUB at http://epub-revision.googlecode.com/files/EGLS_TW_eng.ppt --></dd> 1.1506 - <!-- 1.1507 -<dt><strong>inline</strong></dt> 1.1508 -<dd> 1.1509 -<p>Ruby text follows the ruby base with no special styling. The value can be used to disable ruby text positioning.</p> 1.1510 -<p>If the author has used the XHTML <samp>rp</samp> element [[RUBY]] they should set the <samp>display</samp> value for that element to <samp>inline</samp>, so that the ruby text is distinguishable from the base text. If no <samp>rp</samp> element has been used, the author can use the <samp>content</samp> property with the <samp>:before</samp> and <samp>:after</samp> pseudo-elements to set off the ruby text. </p> 1.1511 -<p class="issue"><span class="issuehead">Issue: </span> Here is a <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20inline+value+description+missing&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">request </a>for this section to be added, from the i18n WG..</p> 1.1512 -</dd> 1.1513 - --> 1.1514 - </dl> 1.1515 - 1.1516 - <p>If two rtc elements are set with the same ruby-position value, (for 1.1517 - example both 'before'), the relative position of the two elements is 1.1518 - undefined. This setting should not be used. 1.1519 - 1.1520 - <h3 id=rubymerge><span class=secno>3.2. </span>Ruby merge: the ‘<a 1.1521 - href="#ruby-merge"><code class=property>ruby-merge</code></a>’ 1.1522 - property</h3> 1.1523 - 1.1524 - <table class=propdef> 1.1525 - <tbody> 1.1526 - <tr> 1.1527 - <th>Name: 1.1528 - 1.1529 - <td><dfn id=ruby-merge>ruby-merge</dfn> 1.1530 - 1.1531 - <tr> 1.1532 - <th><a href="#values">Value</a>: 1.1533 - 1.1534 - <td>separate | collapse | auto 1.1535 - 1.1536 - <tr> 1.1537 - <th>Initial: 1.1538 - 1.1539 - <td>separate 1.1540 - 1.1541 - <tr> 1.1542 - <th>Applies to: 1.1543 - 1.1544 - <td>all elements and generated content 1.1545 - 1.1546 - <tr> 1.1547 - <th>Inherited: 1.1548 - 1.1549 - <td>yes 1.1550 - 1.1551 - <tr> 1.1552 - <th>Percentages: 1.1553 - 1.1554 - <td>N/A 1.1555 - 1.1556 - <tr> 1.1557 - <th>Media: 1.1558 - 1.1559 - <td>visual 1.1560 - 1.1561 - <tr> 1.1562 - <th>Computed value: 1.1563 - 1.1564 - <td>specified value (except for initial and inherit) 1.1565 - </table> 1.1566 - 1.1567 - <p> This property controls how ruby annotation boxes should be rendered 1.1568 - when there are more than one in a ruby container box. 1.1569 - 1.1570 - <p>Possible values: 1.1571 - 1.1572 - <dl> 1.1573 - <dt><dfn id=separate title="ruby-merge:separate">‘<code 1.1574 - class=css>separate</code>’</dfn> 1.1575 - 1.1576 - <dd> 1.1577 - <p> Each ruby annotation box is rendered in the same column as its 1.1578 - corresponding base box. This style is called Mono-ruby in <a 1.1579 - href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.1580 - 1.1581 - <div class=example> 1.1582 - <p>The following two markups render the same: 1.1583 - 1.1584 - <pre><ruby>無<rt>む</ruby><ruby>常<rt>じょう</ruby></pre> 1.1585 - 1.1586 - <p>and: 1.1587 - 1.1588 - <pre><ruby style="ruby-merge:separate"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 1.1589 - </div> 1.1590 - 1.1591 - <dt><dfn id=collapse title="ruby-merge:collapse">‘<code 1.1592 - class=css>collapse</code>’</dfn> 1.1593 - 1.1594 - <dd> 1.1595 - <p> All ruby annotation boxes are concatenated, and rendered to the 1.1596 - concatenated ruby base boxes. This style renders similar to Group-ruby 1.1597 - in <a href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>, 1.1598 - except that it allows line break between annotation pairs. 1.1599 - 1.1600 - <div class=example> 1.1601 - <p>The following two markups render the same if fit in a line: 1.1602 - 1.1603 - <pre><ruby>無常<rt>むじょう</ruby></pre> 1.1604 - 1.1605 - <p>and: 1.1606 - 1.1607 - <pre><ruby style="ruby-merge:collapse"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 1.1608 - </div> 1.1609 - 1.1610 - <dt><dfn id=auto title="ruby-merge:auto">‘<code 1.1611 - class=css>auto</code>’</dfn> 1.1612 - 1.1613 - <dd> 1.1614 - <p> The user agent may use any algorithm to determine how each ruby 1.1615 - annotation box is rendered to its corresponding base box. 1.1616 - 1.1617 - <div class=example> 1.1618 - <p> One possible algorithm is described as Jukugo-ruby in <a 1.1619 - href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.1620 - 1.1621 - <p> Another, more simplified algorithm of Jukugo-ruby is to render as 1.1622 - Mono-ruby if all ruby annotation boxes fit within advances of their 1.1623 - corresponding base boxes, and render as Group-ruby otherwise. 1.1624 - </div> 1.1625 - </dl> 1.1626 - 1.1627 - <h3 id=rubyalign><span class=secno>3.3. </span> Ruby alignment: the ‘<a 1.1628 - href="#ruby-align"><code class=property>ruby-align</code></a>’ 1.1629 - property</h3> 1.1630 - 1.1631 - <table class=propdef> 1.1632 - <tbody> 1.1633 - <tr> 1.1634 - <th>Name: 1.1635 - 1.1636 - <td><dfn id=ruby-align>ruby-align</dfn> 1.1637 - 1.1638 - <tr> 1.1639 - <th><a href="#values">Value</a>: 1.1640 - 1.1641 - <td>auto | start | center | distribute-letter | distribute-space 1.1642 - 1.1643 - <tr> 1.1644 - <th>Initial: 1.1645 - 1.1646 - <td>auto 1.1647 - 1.1648 - <tr> 1.1649 - <th>Applies to: 1.1650 - 1.1651 - <td>all elements and generated content 1.1652 - 1.1653 - <tr> 1.1654 - <th>Inherited: 1.1655 - 1.1656 - <td>yes 1.1657 - 1.1658 - <tr> 1.1659 - <th>Percentages: 1.1660 - 1.1661 - <td>N/A 1.1662 - 1.1663 - <tr> 1.1664 - <th>Media: 1.1665 - 1.1666 - <td>visual 1.1667 - 1.1668 - <tr> 1.1669 - <th>Computed value: 1.1670 - 1.1671 - <td>specified value (except for initial and inherit) 1.1672 - </table> 1.1673 - 1.1674 - <p>This property can be used on any element to control the text alignment 1.1675 - of the ruby text and ruby base contents relative to each other. It 1.1676 - applies to all the rubys in the element. For simple ruby, the alignment 1.1677 - is applied to the ruby child element whose content is shorter: either 1.1678 - the <a href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element 1.1679 - or the <a href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> 1.1680 - element <a href="#RUBY" rel=biblioentry>[RUBY]<!--{{RUBY}}--></a>. For 1.1681 - complex ruby, the alignment is also applied to the ruby child elements 1.1682 - whose content is shorter: either the <samp>rb</samp> element and/or one 1.1683 - or two <samp>rt</samp> elements for each related ruby text and ruby base 1.1684 - element within the <samp>rtc</samp> and <samp>rbc</samp> element. 1.1685 - 1.1686 - <p>Possible values: 1.1687 - 1.1688 - <p class=issue><span class=issuehead>Issue: </span> Tony Graham has <a 1.1689 - href="http://www.w3.org/Style/XSL/Group/FO/wiki/Ruby#Treat_CSS3_.22ruby-align.22_As_Shorthand.3F">suggested 1.1690 - </a>that distribute-letter and distribute-space be values of a 1.1691 - ruby-group-distribution property, and line-edge be moved to a 1.1692 - ruby-alignment-edge property, and that the rest be gathered under a 1.1693 - ruby-alignment property. And that ruby-align become a shorthand. 1.1694 - 1.1695 - <dl> 1.1696 - <dt><dfn id=auto0 title="ruby-align:auto">‘<code 1.1697 - class=css>auto</code>’</dfn> 1.1698 - 1.1699 - <dd> 1.1700 - <p>The user agent determines how the ruby contents are aligned. This is 1.1701 - the initial value. The behavior recommended by <a href="#JLREQ" 1.1702 - rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> is for wide-cell ruby to 1.1703 - be aligned in the ‘<code class=property>distribute-space</code>’ 1.1704 - mode: 1.1705 - 1.1706 - <div class=figure> 1.1707 - <p><img 1.1708 - alt="Diagram of glyph layout in auto aligned ruby when ruby text is shorter than base" 1.1709 - height=91 src="images/ra-ds.gif" width=145><img 1.1710 - alt="Diagram of glyph layout in auto aligned ruby when ruby text is longer than base" 1.1711 - height=91 src="images/ra-ds-rb.gif" width=145> 1.1712 - 1.1713 - <p><b>Figure 4.2.1</b>: Wide-cell text in ‘<code 1.1714 - class=property>auto</code>’ ruby alignment is ‘<code 1.1715 - class=property>distribute-space</code>’ justified 1.1716 - </div> 1.1717 - 1.1718 - <p>The recommended behavior for narrow-cell glyph ruby is to be aligned 1.1719 - in the ‘<code class=property>center</code>’ mode. 1.1720 - 1.1721 - <div class=figure> 1.1722 - <p><img 1.1723 - alt="Diagram of glyph layout in auto aligned ruby when halfwidth ruby text is shorter than base" 1.1724 - height=91 src="images/ra-c-h.gif" width=145><img 1.1725 - alt="Diagram of character layout in auto aligned ruby when ruby text is longer than narrow-width base" 1.1726 - height=91 src="images/ra-c-rb-h.gif" width=145> 1.1727 - 1.1728 - <p><b>Figure 4.2.2</b>: Narrow-width ruby text in ‘<code 1.1729 - class=property>auto</code>’ ruby alignment is centered 1.1730 - </div> 1.1731 - 1.1732 - <dt><dfn id=start title="ruby-align:start">‘<code 1.1733 - class=css>start</code>’</dfn> 1.1734 - 1.1735 - <dd>The ruby text content is aligned with the start edge of the base. 1.1736 - <p class=issue><span class=issuehead>Issue: </span> The i18n WG feels 1.1737 - that start and left should not be synonymous, and proposed to drop 1.1738 - left (there is no left/right in overhang)? See <a 1.1739 - href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20left/start+and+right/end&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">this 1.1740 - thread</a>. 1.1741 - 1.1742 - <div class=figure> 1.1743 - <p><img 1.1744 - alt="Diagram of glyph layout in left aligned ruby when ruby text is shorter than base" 1.1745 - height=91 src="images/ra-l.gif" width=145><img 1.1746 - alt="Diagram of glyph layout in left aligned ruby when ruby text is longer than base" 1.1747 - height=91 src="images/ra-l-rb.gif" width=145> 1.1748 - 1.1749 - <p><b>Figure 4.2.3</b>: Start ruby alignment 1.1750 - </div> 1.1751 - 1.1752 - <dt><dfn id=center title="ruby-align:center">‘<code 1.1753 - class=css>center</code>’</dfn> 1.1754 - 1.1755 - <dd>The ruby text content is centered within the width of the base. If 1.1756 - the length of the base is smaller than the length of the ruby text, 1.1757 - then the base is centered within the width of the ruby text. 1.1758 - <div class=figure> 1.1759 - <p><img 1.1760 - alt="Diagram of glyph layout in center aligned ruby when ruby text is shorter than base" 1.1761 - height=91 src="images/ra-c.gif" width=145><img 1.1762 - alt="Diagram of glyph layout in center aligned ruby when ruby text is longer than base" 1.1763 - height=91 src="images/ra-c-rb.gif" width=145> 1.1764 - 1.1765 - <p><b>Figure 4.2.4</b>: Center ruby alignment 1.1766 - </div> 1.1767 - </dd> 1.1768 - <!-- 1.1769 + <dt><dfn id=inter-character title="ruby-position:inter-character">‘<code 1.1770 + class=css>inter-character</code>’</dfn> 1.1771 + 1.1772 + <dd> 1.1773 + <p>The ruby text appears on the right of the base in horizontal text. 1.1774 + This value forces the ‘<code class=property>writing-mode</code>’ of 1.1775 + the <a href="#ruby-annotation-box"><i>ruby annotation</i></a> to be 1.1776 + vertical. 1.1777 + 1.1778 + <p>This value is provided for the special case of traditional Chinese as 1.1779 + used especially in Taiwan: ruby (made of <a 1.1780 + href="#g-bopomofo">bopomofo</a> glyphs) in that context appears 1.1781 + vertically along the right side of the base glyph, even when the layout 1.1782 + of the base characters is horizontal: 1.1783 + 1.1784 + <div class=figure> 1.1785 + <p><img alt="Example of Taiwanese-style ruby" src="images/bopomofo.gif"> 1.1786 + 1.1787 + <p class=caption>“Bopomofo” ruby in traditional Chinese (ruby text 1.1788 + shown in blue for clarity) in horizontal layout 1.1789 + </div> 1.1790 + 1.1791 + <p class=note> Note that the user agent is responsible for ensuring the 1.1792 + correct relative alignment and positioning of the glyphs, including 1.1793 + those corresponding to the tone marks, when displaying. Tone marks are 1.1794 + spacing characters that occur (in memory) at the end of the ruby text 1.1795 + for each base character. They are usually displayed in a separate column 1.1796 + to the right of the bopomofo characters, and the height of the tone mark 1.1797 + depends on the number of characters in the syllable. One tone mark, 1.1798 + however, is placed above the bopomofo, not to the right of it. 1.1799 + <!-- See Taiwanese requirements doc for EPUB at http://epub-revision.googlecode.com/files/EGLS_TW_eng.ppt --> 1.1800 + </dl> 1.1801 + 1.1802 + <p>If multiple <a href="#ruby-annotation-container-box"><i>ruby annotation 1.1803 + containers</i></a> have the same ‘<a href="#ruby-position"><code 1.1804 + class=property>ruby-position</code></a>’, they stack along the block 1.1805 + axis, with lower levels of annotation closer to the base text. 1.1806 + 1.1807 + <h3 id=collapsed-ruby><span class=secno>3.2. </span> Collapsed Ruby 1.1808 + Annotations: the ‘<a href="#ruby-merge"><code 1.1809 + class=property>ruby-merge</code></a>’ property</h3> 1.1810 + 1.1811 + <table class=propdef> 1.1812 + <tbody> 1.1813 + <tr> 1.1814 + <th>Name: 1.1815 + 1.1816 + <td><dfn id=ruby-merge>ruby-merge</dfn> 1.1817 + 1.1818 + <tr> 1.1819 + <th><a href="#values">Value</a>: 1.1820 + 1.1821 + <td>separate | collapse | auto 1.1822 + 1.1823 + <tr> 1.1824 + <th>Initial: 1.1825 + 1.1826 + <td>separate 1.1827 + 1.1828 + <tr> 1.1829 + <th>Applies to: 1.1830 + 1.1831 + <td>ruby annotation containers 1.1832 + 1.1833 + <tr> 1.1834 + <th>Inherited: 1.1835 + 1.1836 + <td>yes 1.1837 + 1.1838 + <tr> 1.1839 + <th>Percentages: 1.1840 + 1.1841 + <td>N/A 1.1842 + 1.1843 + <tr> 1.1844 + <th>Media: 1.1845 + 1.1846 + <td>visual 1.1847 + 1.1848 + <tr> 1.1849 + <th>Computed value: 1.1850 + 1.1851 + <td>specified value 1.1852 + 1.1853 + <tr> 1.1854 + <th>Animatable: 1.1855 + 1.1856 + <td>no 1.1857 + 1.1858 + <tr> 1.1859 + <th>Canonical order: 1.1860 + 1.1861 + <td><abbr title="follows order of property value definition">per 1.1862 + grammar</abbr> 1.1863 + </table> 1.1864 + 1.1865 + <p> This property controls how ruby annotation boxes should be rendered 1.1866 + when there are more than one in a ruby container box. 1.1867 + 1.1868 + <p>Possible values: 1.1869 + 1.1870 + <dl> 1.1871 + <dt><dfn id=separate title="ruby-merge:separate">‘<code 1.1872 + class=css>separate</code>’</dfn> 1.1873 + 1.1874 + <dd> 1.1875 + <p> Each ruby annotation box is rendered in the same column(s) as its 1.1876 + corresponding base box(es). This style is called “mono ruby” in <a 1.1877 + href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.1878 + 1.1879 + <div class=example> 1.1880 + <p>For example, the following two markups render the same: 1.1881 + 1.1882 + <pre><ruby>無<rt>む</ruby><ruby>常<rt>じょう</ruby></pre> 1.1883 + 1.1884 + <p>and: 1.1885 + 1.1886 + <pre><ruby style="ruby-merge:separate"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 1.1887 + </div> 1.1888 + 1.1889 + <dt><dfn id=collapse title="ruby-merge:collapse">‘<code 1.1890 + class=css>collapse</code>’</dfn> 1.1891 + 1.1892 + <dd> 1.1893 + <p> All <a href="#ruby-annotation-box"><i>ruby annotation boxes</i></a> 1.1894 + within the same <i>ruby segment</i> on the same line are concatenated, 1.1895 + and laid out as if their contents belonged to a single <a 1.1896 + href="#ruby-annotation-box"><i>ruby annotation box</i></a> spanning all 1.1897 + their associated <i>ruby base boxes. This style renders similar to 1.1898 + “group ruby” in <a href="#JLREQ" 1.1899 + rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>, except that <a 1.1900 + href="#ruby-annotation-box"><i>ruby annotations</i></a> are kept 1.1901 + together with their respective <a href="#ruby-base-box"><i>ruby 1.1902 + bases</i></a> when breaking lines. </i> 1.1903 + 1.1904 + <div class=example> 1.1905 + <p>The following two markups render the same both characters fit on one 1.1906 + line: 1.1907 + 1.1908 + <pre><ruby>無常<rt>むじょう</ruby></pre> 1.1909 + 1.1910 + <p>and: 1.1911 + 1.1912 + <pre><ruby style="ruby-merge:collapse"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 1.1913 + 1.1914 + <p>However, the second one renders the same as ‘<code 1.1915 + class=css>ruby-position: separate</code>’ when the two bases are 1.1916 + split across lines. 1.1917 + </div> 1.1918 + 1.1919 + <dt><dfn id=auto title="ruby-merge:auto">‘<code 1.1920 + class=css>auto</code>’</dfn> 1.1921 + 1.1922 + <dd> 1.1923 + <p> The user agent may use any algorithm to determine how each ruby 1.1924 + annotation box is rendered to its corresponding base box. 1.1925 + 1.1926 + <div class=example> 1.1927 + <p> One possible algorithm is described as Jukugo-ruby in <a 1.1928 + href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.1929 + 1.1930 + <p> Another, more simplified algorithm of Jukugo-ruby is to render as 1.1931 + Mono-ruby if all ruby annotation boxes fit within advances of their 1.1932 + corresponding base boxes, and render as Group-ruby otherwise. 1.1933 + </div> 1.1934 + </dl> 1.1935 + 1.1936 + <h3 id=rubyalign><span class=secno>3.3. </span> Ruby Text Distribution: the 1.1937 + ‘<a href="#ruby-align"><code class=property>ruby-align</code></a>’ 1.1938 + property</h3> 1.1939 + 1.1940 + <table class=propdef> 1.1941 + <tbody> 1.1942 + <tr> 1.1943 + <th>Name: 1.1944 + 1.1945 + <td><dfn id=ruby-align>ruby-align</dfn> 1.1946 + 1.1947 + <tr> 1.1948 + <th><a href="#values">Value</a>: 1.1949 + 1.1950 + <td>auto | start | center | distribute-letter | distribute-space 1.1951 + 1.1952 + <tr> 1.1953 + <th>Initial: 1.1954 + 1.1955 + <td>auto 1.1956 + 1.1957 + <tr> 1.1958 + <th>Applies to: 1.1959 + 1.1960 + <td>ruby bases, ruby annotations, ruby base containers, ruby annotation 1.1961 + containers 1.1962 + 1.1963 + <tr> 1.1964 + <th>Inherited: 1.1965 + 1.1966 + <td>yes 1.1967 + 1.1968 + <tr> 1.1969 + <th>Percentages: 1.1970 + 1.1971 + <td>N/A 1.1972 + 1.1973 + <tr> 1.1974 + <th>Media: 1.1975 + 1.1976 + <td>visual 1.1977 + 1.1978 + <tr> 1.1979 + <th>Computed value: 1.1980 + 1.1981 + <td>specified value (except for initial and inherit) 1.1982 + </table> 1.1983 + 1.1984 + <p>This property specifies how text is distributed within the various ruby 1.1985 + boxes when their text contents exactly fill their respective boxes. 1.1986 + 1.1987 + <p>Values have the following meanings: 1.1988 + 1.1989 + <p class=issue><span class=issuehead>Issue: </span> Tony Graham has <a 1.1990 + href="http://www.w3.org/Style/XSL/Group/FO/wiki/Ruby#Treat_CSS3_.22ruby-align.22_As_Shorthand.3F">suggested 1.1991 + </a>that distribute-letter and distribute-space be values of a 1.1992 + ruby-group-distribution property, and line-edge be moved to a 1.1993 + ruby-alignment-edge property, and that the rest be gathered under a 1.1994 + ruby-alignment property. And that ruby-align become a shorthand. 1.1995 + 1.1996 + <dl> 1.1997 + <dt><dfn id=auto0 title="ruby-align:auto">‘<code 1.1998 + class=css>auto</code>’</dfn> 1.1999 + 1.2000 + <dd> 1.2001 + <p>The user agent determines how the ruby contents are aligned. This is 1.2002 + the initial value. The behavior recommended by <a href="#JLREQ" 1.2003 + rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> is for wide-cell ruby to be 1.2004 + aligned in the ‘<code class=property>distribute-space</code>’ mode: 1.2005 + 1.2006 + <div class=figure> 1.2007 + <p><img 1.2008 + alt="Diagram of glyph layout in auto aligned ruby when ruby text is shorter than base" 1.2009 + height=91 src="images/ra-ds.gif" width=145><img 1.2010 + alt="Diagram of glyph layout in auto aligned ruby when ruby text is longer than base" 1.2011 + height=91 src="images/ra-ds-rb.gif" width=145> 1.2012 + 1.2013 + <p><b>Figure 4.2.1</b>: Wide-cell text in ‘<code 1.2014 + class=property>auto</code>’ ruby alignment is ‘<code 1.2015 + class=property>distribute-space</code>’ justified 1.2016 + </div> 1.2017 + 1.2018 + <p>The recommended behavior for narrow-cell glyph ruby is to be aligned 1.2019 + in the ‘<code class=property>center</code>’ mode. 1.2020 + 1.2021 + <div class=figure> 1.2022 + <p><img 1.2023 + alt="Diagram of glyph layout in auto aligned ruby when halfwidth ruby text is shorter than base" 1.2024 + height=91 src="images/ra-c-h.gif" width=145><img 1.2025 + alt="Diagram of character layout in auto aligned ruby when ruby text is longer than narrow-width base" 1.2026 + height=91 src="images/ra-c-rb-h.gif" width=145> 1.2027 + 1.2028 + <p><b>Figure 4.2.2</b>: Narrow-width ruby text in ‘<code 1.2029 + class=property>auto</code>’ ruby alignment is centered 1.2030 + </div> 1.2031 + 1.2032 + <dt><dfn id=start title="ruby-align:start">‘<code 1.2033 + class=css>start</code>’</dfn> 1.2034 + 1.2035 + <dd>The ruby annotation content is aligned with the start edge of the 1.2036 + base. 1.2037 + <div class=figure> 1.2038 + <p><img 1.2039 + alt="Diagram of glyph layout in left aligned ruby when ruby text is shorter than base" 1.2040 + height=91 src="images/ra-l.gif" width=145><img 1.2041 + alt="Diagram of glyph layout in left aligned ruby when ruby text is longer than base" 1.2042 + height=91 src="images/ra-l-rb.gif" width=145> 1.2043 + 1.2044 + <p><b>Figure 4.2.3</b>: Start ruby alignment 1.2045 + </div> 1.2046 + 1.2047 + <dt><dfn id=center title="ruby-align:center">‘<code 1.2048 + class=css>center</code>’</dfn> 1.2049 + 1.2050 + <dd>The ruby text content is centered within the width of the base. If the 1.2051 + length of the base is smaller than the length of the ruby text, then the 1.2052 + base is centered within the width of the ruby text. 1.2053 + <div class=figure> 1.2054 + <p><img 1.2055 + alt="Diagram of glyph layout in center aligned ruby when ruby text is shorter than base" 1.2056 + height=91 src="images/ra-c.gif" width=145><img 1.2057 + alt="Diagram of glyph layout in center aligned ruby when ruby text is longer than base" 1.2058 + height=91 src="images/ra-c-rb.gif" width=145> 1.2059 + 1.2060 + <p><b>Figure 4.2.4</b>: Center ruby alignment 1.2061 + </div> 1.2062 + </dd> 1.2063 + <!-- 1.2064 <dt><strong>right</strong></dt> 1.2065 <dd>The ruby text content is aligned with the end edge of the base. 1.2066 <p class="issue"><span class="issuehead">Issue: </span> The i18n WG feels that end and right should not be synonymous, and proposed to drop right (there is no left/right in overhang)? See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20left/start+and+right/end&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">this thread</a>.</p> 1.2067 @@ -1368,51 +1327,50 @@ 1.2068 </dd> 1.2069 --> 1.2070 1.2071 - <dt><dfn id=distribute-letter 1.2072 - title="ruby-align:distribute-letter">‘<code 1.2073 - class=css>distribute-letter</code>’</dfn> 1.2074 - 1.2075 - <dd>If the width of the ruby text is smaller than that of the base, then 1.2076 - the ruby text contents are evenly distributed across the width of the 1.2077 - base, with the first and last ruby text glyphs lining up with the 1.2078 - corresponding first and last base glyphs. If the width of the ruby text 1.2079 - is at least the width of the base, then the letters of the base are 1.2080 - evenly distributed across the width of the ruby text. 1.2081 - <div class=figure> 1.2082 - <p><img 1.2083 - alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is shorter than base" 1.2084 - height=91 src="images/ra-dl.gif" width=145><img 1.2085 - alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is longer than base" 1.2086 - height=91 src="images/ra-dl-rb.gif" width=145> 1.2087 - 1.2088 - <p><b>Figure 4.2.6</b>: Distribute-letter ruby alignment 1.2089 - </div> 1.2090 - 1.2091 - <dt><dfn id=distribute-space 1.2092 - title="ruby-align:distribute-space">‘<code 1.2093 - class=css>distribute-space</code>’</dfn> 1.2094 - 1.2095 - <dd>If the width of the ruby text is smaller than that of the base, then 1.2096 - the ruby text contents are evenly distributed across the width of the 1.2097 - base, with a certain amount of white space preceding the first and 1.2098 - following the last character in the ruby text. That amount of white 1.2099 - space is normally equal to half the amount of inter-character space of 1.2100 - the ruby text. If the width of the ruby text is at least the width of 1.2101 - the base, then the same type of space distribution applies to the base. 1.2102 - In other words, if the base is shorter than the ruby text, the base is 1.2103 - distribute-space aligned. This type of alignment is described by <a 1.2104 - href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.2105 - <div class=figure> 1.2106 - <p><img 1.2107 - alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is shorter than base" 1.2108 - height=91 src="images/ra-ds.gif" width=145><img 1.2109 - alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is longer than base" 1.2110 - height=91 src="images/ra-ds-rb.gif" width=145> 1.2111 - 1.2112 - <p><b>Figure 4.2.7</b>: Distribute-space ruby alignment 1.2113 - </div> 1.2114 - </dd> 1.2115 - <!-- 1.2116 + <dt><dfn id=distribute-letter 1.2117 + title="ruby-align:distribute-letter">‘<code 1.2118 + class=css>distribute-letter</code>’</dfn> 1.2119 + 1.2120 + <dd>If the width of the ruby text is smaller than that of the base, then 1.2121 + the ruby text contents are evenly distributed across the width of the 1.2122 + base, with the first and last ruby text glyphs lining up with the 1.2123 + corresponding first and last base glyphs. If the width of the ruby text 1.2124 + is at least the width of the base, then the letters of the base are 1.2125 + evenly distributed across the width of the ruby text. 1.2126 + <div class=figure> 1.2127 + <p><img 1.2128 + alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is shorter than base" 1.2129 + height=91 src="images/ra-dl.gif" width=145><img 1.2130 + alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is longer than base" 1.2131 + height=91 src="images/ra-dl-rb.gif" width=145> 1.2132 + 1.2133 + <p><b>Figure 4.2.6</b>: Distribute-letter ruby alignment 1.2134 + </div> 1.2135 + 1.2136 + <dt><dfn id=distribute-space title="ruby-align:distribute-space">‘<code 1.2137 + class=css>distribute-space</code>’</dfn> 1.2138 + 1.2139 + <dd>If the width of the ruby text is smaller than that of the base, then 1.2140 + the ruby text contents are evenly distributed across the width of the 1.2141 + base, with a certain amount of white space preceding the first and 1.2142 + following the last character in the ruby text. That amount of white space 1.2143 + is normally equal to half the amount of inter-character space of the ruby 1.2144 + text. If the width of the ruby text is at least the width of the base, 1.2145 + then the same type of space distribution applies to the base. In other 1.2146 + words, if the base is shorter than the ruby text, the base is 1.2147 + distribute-space aligned. This type of alignment is described by <a 1.2148 + href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.2149 + <div class=figure> 1.2150 + <p><img 1.2151 + alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is shorter than base" 1.2152 + height=91 src="images/ra-ds.gif" width=145><img 1.2153 + alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is longer than base" 1.2154 + height=91 src="images/ra-ds-rb.gif" width=145> 1.2155 + 1.2156 + <p><b>Figure 4.2.7</b>: Distribute-space ruby alignment 1.2157 + </div> 1.2158 + </dd> 1.2159 + <!-- 1.2160 <dt><strong>line-edge</strong></dt> 1.2161 <dd>If the ruby text is not adjacent to a line edge, it is aligned as in 1.2162 'auto'. If it is adjacent to a line edge, then it is still aligned as in 1.2163 @@ -1432,56 +1390,55 @@ 1.2164 </div> 1.2165 </dd> 1.2166 --> 1.2167 - </dl> 1.2168 - 1.2169 - <p>For a complex ruby with spanning elements, one additional 1.2170 - consideration is required. If the spanning element spans multiple 1.2171 - ‘<code class=property>rows</code>’ (other rbc or rtc elements), and 1.2172 - the ruby alignment requires space distribution among the ‘<code 1.2173 - class=property>spanned</code>’ elements, a ratio must be determined 1.2174 - among the ‘<code class=property>columns</code>’ of spanned elements. 1.2175 - This ratio is computed by taking into consideration the widest element 1.2176 - within each column. 1.2177 - 1.2178 - <h2 id=rubyover><span class=secno>4. </span> Ruby Overhang and Edge 1.2179 - Effects</h2> 1.2180 - 1.2181 - <p> When <a href="#ruby-annotation-box"><i>ruby annotation box</i></a> is 1.2182 - longer than its corresponding <a href="#ruby-base-box"><i>ruby base 1.2183 - box</i></a>, the <a href="#ruby-annotation-box"><i>ruby annotation 1.2184 - box</i></a> may partially overhang adjacent boxes. 1.2185 - 1.2186 - <p> This level of the specificaiton does not define how much the overhang 1.2187 - may be allowed, and under what conditions. 1.2188 - 1.2189 - <div class=example> 1.2190 - <p> The user agent may use <a href="#JIS4051" 1.2191 - rel=biblioentry>[JIS4051]<!--{{JIS4051}}--></a> recommendation of using 1.2192 - one ruby text character length as the maximum overhang length. Detailed 1.2193 - rules for how ruby text can overhang adjacent characters for Japanese 1.2194 - are described by <a href="#JLREQ" 1.2195 - rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.2196 - </div> 1.2197 - 1.2198 - <p> When such <a href="#ruby-annotation-box"><i>ruby annotation 1.2199 - box</i></a> is at the start or end edge of a line, user agent may align 1.2200 - the side of the ruby text that touches the edge of the line to the 1.2201 - corresponding edge of the base. This type of alignment is described by 1.2202 - <a href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.2203 - 1.2204 - <p> This level of the specificaiton does not provide a mechanism to 1.2205 - control this behavior. 1.2206 - 1.2207 - <div class=figure> 1.2208 - <p><img 1.2209 - alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is shorter than base" 1.2210 - height=109 src="images/ra-le-l.gif" width=146><img 1.2211 - alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is longer than base" 1.2212 - height=110 src="images/ra-le-r.gif" width=146> 1.2213 - 1.2214 - <p><b>Figure 4.2.8</b>: Line edge ruby alignment 1.2215 - </div> 1.2216 - <!-- 1.2217 + </dl> 1.2218 + 1.2219 + <p>For a complex ruby with spanning elements, one additional consideration 1.2220 + is required. If the spanning element spans multiple ‘<code 1.2221 + class=property>rows</code>’ (other rbc or rtc elements), and the ruby 1.2222 + alignment requires space distribution among the ‘<code 1.2223 + class=property>spanned</code>’ elements, a ratio must be determined 1.2224 + among the ‘<code class=property>columns</code>’ of spanned elements. 1.2225 + This ratio is computed by taking into consideration the widest element 1.2226 + within each column. 1.2227 + 1.2228 + <h2 id=rubyover><span class=secno>4. </span> Ruby Overhang and Edge Effects</h2> 1.2229 + 1.2230 + <p> When <a href="#ruby-annotation-box"><i>ruby annotation box</i></a> is 1.2231 + longer than its corresponding <a href="#ruby-base-box"><i>ruby base 1.2232 + box</i></a>, the <a href="#ruby-annotation-box"><i>ruby annotation 1.2233 + box</i></a> may partially overhang adjacent boxes. 1.2234 + 1.2235 + <p> This level of the specificaiton does not define how much the overhang 1.2236 + may be allowed, and under what conditions. 1.2237 + 1.2238 + <div class=example> 1.2239 + <p> The user agent may use <a href="#JIS4051" 1.2240 + rel=biblioentry>[JIS4051]<!--{{JIS4051}}--></a> recommendation of using 1.2241 + one ruby text character length as the maximum overhang length. Detailed 1.2242 + rules for how ruby text can overhang adjacent characters for Japanese are 1.2243 + described by <a href="#JLREQ" 1.2244 + rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.2245 + </div> 1.2246 + 1.2247 + <p> When such <a href="#ruby-annotation-box"><i>ruby annotation box</i></a> 1.2248 + is at the start or end edge of a line, user agent may align the side of 1.2249 + the ruby text that touches the edge of the line to the corresponding edge 1.2250 + of the base. This type of alignment is described by <a href="#JLREQ" 1.2251 + rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>. 1.2252 + 1.2253 + <p> This level of the specificaiton does not provide a mechanism to control 1.2254 + this behavior. 1.2255 + 1.2256 + <div class=figure> 1.2257 + <p><img 1.2258 + alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is shorter than base" 1.2259 + height=109 src="images/ra-le-l.gif" width=146><img 1.2260 + alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is longer than base" 1.2261 + height=110 src="images/ra-le-r.gif" width=146> 1.2262 + 1.2263 + <p><b>Figure 4.2.8</b>: Line edge ruby alignment 1.2264 + </div> 1.2265 + <!-- 1.2266 <h3 id="rubyover"> 1.2267 Ruby overhanging: the 'ruby-overhang' property</h3> 1.2268 1.2269 @@ -1642,54 +1599,53 @@ 1.2270 </myruby></pre> 1.2271 --> 1.2272 1.2273 - <h2 class=no-num id=default-stylesheet> Appendix A: Default Style Sheet</h2> 1.2274 - 1.2275 - <p><em>This section is informative.</em> 1.2276 - 1.2277 - <h3 class=no-num id=default-ua-ruby> Supporting Ruby Layout</h3> 1.2278 - 1.2279 - <p>The following represents a default UA style sheet for rendering HTML 1.2280 - and XHTML ruby markup as ruby layout: 1.2281 - 1.2282 - <pre> 1.2283 + <h2 class=no-num id=default-stylesheet> Appendix A: Default Style Sheet</h2> 1.2284 + 1.2285 + <p><em>This section is informative.</em> 1.2286 + 1.2287 + <h3 class=no-num id=default-ua-ruby> Supporting Ruby Layout</h3> 1.2288 + 1.2289 + <p>The following represents a default UA style sheet for rendering HTML and 1.2290 + XHTML ruby markup as ruby layout: 1.2291 + 1.2292 + <pre> 1.2293 <!-- -->ruby { display: ruby; } 1.2294 <!-- -->rb { display: ruby-base; white-space: nowrap; } 1.2295 <!-- -->rt { display: ruby-text; white-space: nowrap; font-size: 50%; } 1.2296 <!-- -->rbc { display: ruby-base-container; } 1.2297 <!-- -->rtc { display: ruby-text-container; }</pre> 1.2298 1.2299 - <p>Additional rules for UAs supporting the relevant features of <a 1.2300 - href="#CSS3-TEXT-DECOR" 1.2301 - rel=biblioentry>[CSS3-TEXT-DECOR]<!--{{CSS3-TEXT-DECOR}}--></a> and <a 1.2302 - href="#CSS3-FONTS" 1.2303 - rel=biblioentry>[CSS3-FONTS]<!--{{CSS3-FONTS}}--></a>: 1.2304 - 1.2305 - <pre>rt { font-variant-east-asian: ruby; text-emphasis: none; }</pre> 1.2306 - 1.2307 - <p class=note>Authors should not use the above rules; a UA that supports 1.2308 - ruby layout should provide these by default. 1.2309 - 1.2310 - <h3 class=no-num id=default-inline> Inlining Ruby Annotations</h3> 1.2311 - 1.2312 - <p>The following represents a sample style sheet for rendering HTML and 1.2313 - XHTML ruby markup as inline annotations: 1.2314 - 1.2315 - <pre>ruby, rb, rt, rbc, rtc, rp { 1.2316 + <p>Additional rules for UAs supporting the relevant features of <a 1.2317 + href="#CSS3-TEXT-DECOR" 1.2318 + rel=biblioentry>[CSS3-TEXT-DECOR]<!--{{CSS3-TEXT-DECOR}}--></a> and <a 1.2319 + href="#CSS3-FONTS" rel=biblioentry>[CSS3-FONTS]<!--{{CSS3-FONTS}}--></a>: 1.2320 + 1.2321 + <pre>rt { font-variant-east-asian: ruby; text-emphasis: none; }</pre> 1.2322 + 1.2323 + <p class=note>Authors should not use the above rules; a UA that supports 1.2324 + ruby layout should provide these by default. 1.2325 + 1.2326 + <h3 class=no-num id=default-inline> Inlining Ruby Annotations</h3> 1.2327 + 1.2328 + <p>The following represents a sample style sheet for rendering HTML and 1.2329 + XHTML ruby markup as inline annotations: 1.2330 + 1.2331 + <pre>ruby, rb, rt, rbc, rtc, rp { 1.2332 <!-- --> display: inline; white-space: inherit; 1.2333 <!-- --> font-variant-east-asian: inherit; text-emphasis: inherit; }</pre> 1.2334 1.2335 - <h3 class=no-num id=default-parens> Generating Parentheses</h3> 1.2336 - 1.2337 - <p>Unfortunately, because Selectors cannot match against text nodes, it's 1.2338 - not possible with CSS to express rules that will automatically and 1.2339 - correctly add parentheses to unparenthesized ruby annotations in HTML. 1.2340 - (This is because HTML ruby allows implying the <a 1.2341 - href="#ruby-base-box"><i>ruby base</i></a> from raw text, without a 1.2342 - corresponding element.) However, these rules will handle cases where 1.2343 - either <code><rb></code> or <code><rtc></code> is used 1.2344 - rigorously. 1.2345 - 1.2346 - <pre> 1.2347 + <h3 class=no-num id=default-parens> Generating Parentheses</h3> 1.2348 + 1.2349 + <p>Unfortunately, because Selectors cannot match against text nodes, it's 1.2350 + not possible with CSS to express rules that will automatically and 1.2351 + correctly add parentheses to unparenthesized ruby annotations in HTML. 1.2352 + (This is because HTML ruby allows implying the <a 1.2353 + href="#ruby-base-box"><i>ruby base</i></a> from raw text, without a 1.2354 + corresponding element.) However, these rules will handle cases where 1.2355 + either <code><rb></code> or <code><rtc></code> is used 1.2356 + rigorously. 1.2357 + 1.2358 + <pre> 1.2359 <!-- -->/* Parens around <rtc> */ 1.2360 <!-- -->rtc::before { content: "("; } 1.2361 <!-- -->rtc::after { content: ")"; } 1.2362 @@ -1703,474 +1659,546 @@ 1.2363 <!-- -->rt + rb::before { content: ")"; } 1.2364 <!-- -->rt + rtc::before { content: ")("; }</pre> 1.2365 1.2366 - <h2 id=glossary><span class=secno>5. </span> Glossary</h2> 1.2367 - 1.2368 - <dl> 1.2369 - <dt><a id=g-bopomofo><strong><span lang=zh>Bopomofo</span></strong></a> 1.2370 - 1.2371 - <dd>37 characters and 4 tone markings used as phonetics in Chinese, 1.2372 - especially standard Mandarin. 1.2373 - 1.2374 - <dt><a id=g-hanja><strong><span lang=ko>Hanja</span></strong></a> 1.2375 - 1.2376 - <dd>Subset of the Korean writing system that utilizes ideographic 1.2377 - characters borrowed or adapted from the Chinese writing system. Also 1.2378 - see <a href="#g-kanji"><span lang=ja>Kanji</span></a>. 1.2379 - 1.2380 - <dt><a id=g-hiragana><strong><span lang=ja>Hiragana</span></strong></a> 1.2381 - 1.2382 - <dd>Japanese syllabic script, or character of that script. Rounded and 1.2383 - cursive in appearance. Subset of the Japanese writing system, used 1.2384 - together with kanji and katakana. In recent times, mostly used to write 1.2385 - Japanese words when kanji are not available or appropriate, and word 1.2386 - endings and particles. Also see <a href="#g-katakana"><span 1.2387 - lang=ja>Katakana</span></a>. 1.2388 - 1.2389 - <dt><a id=g-ideogram><strong>Ideograph</strong></a> 1.2390 - 1.2391 - <dd>A character that is used to represent an idea, word, or word 1.2392 - component, in contrast to a character from an alphabetic or syllabic 1.2393 - script. The most well-known ideographic script is used (with some 1.2394 - variation) in East Asia (China, Japan, Korea,...). 1.2395 - 1.2396 - <dt><a id=g-kana><strong><span lang=ja>Kana</span></strong></a> 1.2397 - 1.2398 - <dd>Collective term for hiragana and katakana. 1.2399 - 1.2400 - <dt><a id=g-kanji><strong>Kanji</strong></a> 1.2401 - 1.2402 - <dd>Japanese term for ideographs; ideographs used in Japanese. Subset of 1.2403 - the Japanese writing system, used together with hiragana and katakana. 1.2404 - Also see <a href="#g-hanja"><span lang=ko>Hanja</span></a>. 1.2405 - 1.2406 - <dt><a id=g-katakana><strong><span lang=ja>Katakana</span></strong></a> 1.2407 - 1.2408 - <dd>Japanese syllabic script, or character of that script. Angular in 1.2409 - appearance. Subset of the Japanese writing system, used together with 1.2410 - kanji and hiragana. In recent times, mainly used to write foreign 1.2411 - words. Also see <a href="#g-hiragana"><span 1.2412 - lang=ja>Hiragana</span></a>. 1.2413 - 1.2414 - <dt><a id=g-monoruby name=g-monoruby><strong>Mono-ruby</strong></a> 1.2415 - 1.2416 - <dd>In Japanese typography: Ruby associated with a single character of 1.2417 - the base text. 1.2418 - 1.2419 - <dt><a id=g-ruby><strong>Ruby</strong></a> 1.2420 - 1.2421 - <dd>A run of text that appears in the vicinity of another run of text 1.2422 - and serves as an annotation or a pronunciation guide for that text. 1.2423 - </dl> 1.2424 - 1.2425 - <h2 id=conformance><span class=secno>6. </span> Conformance</h2> 1.2426 - 1.2427 - <h3 id=conventions><span class=secno>6.1. </span> Document conventions</h3> 1.2428 - 1.2429 - <p>Conformance requirements are expressed with a combination of 1.2430 - descriptive assertions and RFC 2119 terminology. The key words 1.2431 - “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL 1.2432 - NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, 1.2433 - and “OPTIONAL” in the normative parts of this document are to be 1.2434 - interpreted as described in RFC 2119. However, for readability, these 1.2435 - words do not appear in all uppercase letters in this specification. 1.2436 - 1.2437 - <p>All of the text of this specification is normative except sections 1.2438 - explicitly marked as non-normative, examples, and notes. <a 1.2439 - href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a> 1.2440 - 1.2441 - <p>Examples in this specification are introduced with the words “for 1.2442 - example” or are set apart from the normative text with 1.2443 - <code>class="example"</code>, like this: 1.2444 - 1.2445 - <div class=example> 1.2446 - <p>This is an example of an informative example. 1.2447 - </div> 1.2448 - 1.2449 - <p>Informative notes begin with the word “Note” and are set apart 1.2450 - from the normative text with <code>class="note"</code>, like this: 1.2451 - 1.2452 - <p class=note>Note, this is an informative note. 1.2453 - 1.2454 - <h3 id=conformance-classes><span class=secno>6.2. </span> Conformance 1.2455 - classes</h3> 1.2456 - 1.2457 - <p>Conformance to CSS Ruby Module is defined for three conformance 1.2458 - classes: 1.2459 - 1.2460 - <dl> 1.2461 - <dt><dfn id=style-sheet title="style sheet!!as conformance class">style 1.2462 - sheet</dfn> 1.2463 - 1.2464 - <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS 1.2465 - style sheet</a>. 1.2466 - 1.2467 - <dt><dfn id=renderer>renderer</dfn> 1.2468 - 1.2469 - <dd>A <a 1.2470 - href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> that 1.2471 - interprets the semantics of a style sheet and renders documents that 1.2472 - use them. 1.2473 - 1.2474 - <dt><dfn id=authoring-tool>authoring tool</dfn> 1.2475 - 1.2476 - <dd>A <a 1.2477 - href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> that 1.2478 - writes a style sheet. 1.2479 - </dl> 1.2480 - 1.2481 - <p>A style sheet is conformant to CSS Ruby Module if all of its 1.2482 - statements that use syntax defined in this module are valid according to 1.2483 - the generic CSS grammar and the individual grammars of each feature 1.2484 - defined in this module. 1.2485 - 1.2486 - <p>A renderer is conformant to CSS Ruby Module if, in addition to 1.2487 - interpreting the style sheet as defined by the appropriate 1.2488 - specifications, it supports all the features defined by CSS Ruby Module 1.2489 - by parsing them correctly and rendering the document accordingly. 1.2490 - However, the inability of a UA to correctly render a document due to 1.2491 - limitations of the device does not make the UA non-conformant. (For 1.2492 - example, a UA is not required to render color on a monochrome monitor.) 1.2493 - 1.2494 - <p>An authoring tool is conformant to CSS Ruby Module if it writes style 1.2495 - sheets that are syntactically correct according to the generic CSS 1.2496 - grammar and the individual grammars of each feature in this module, and 1.2497 - meet all other conformance requirements of style sheets as described in 1.2498 - this module. 1.2499 - 1.2500 - <h3 id=partial><span class=secno>6.3. </span> Partial implementations</h3> 1.2501 - 1.2502 - <p>So that authors can exploit the forward-compatible parsing rules to 1.2503 - assign fallback values, CSS renderers <strong>must</strong> treat as 1.2504 - invalid (and <a 1.2505 - href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as 1.2506 - appropriate</a>) any at-rules, properties, property values, keywords, 1.2507 - and other syntactic constructs for which they have no usable level of 1.2508 - support. In particular, user agents <strong>must not</strong> 1.2509 - selectively ignore unsupported component values and honor supported 1.2510 - values in a single multi-value property declaration: if any value is 1.2511 - considered invalid (as unsupported values must be), CSS requires that 1.2512 - the entire declaration be ignored. 1.2513 - 1.2514 - <h3 id=experimental><span class=secno>6.4. </span> Experimental 1.2515 - implementations</h3> 1.2516 - 1.2517 - <p>To avoid clashes with future CSS features, the CSS2.1 specification 1.2518 - reserves a <a 1.2519 - href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed 1.2520 - syntax</a> for proprietary and experimental extensions to CSS. 1.2521 - 1.2522 - <p>Prior to a specification reaching the Candidate Recommendation stage 1.2523 - in the W3C process, all implementations of a CSS feature are considered 1.2524 - experimental. The CSS Working Group recommends that implementations use 1.2525 - a vendor-prefixed syntax for such features, including those in W3C 1.2526 - Working Drafts. This avoids incompatibilities with future changes in the 1.2527 - draft. 1.2528 - 1.2529 - <h3 id=testing><span class=secno>6.5. </span> Non-experimental 1.2530 - implementations</h3> 1.2531 - 1.2532 - <p>Once a specification reaches the Candidate Recommendation stage, 1.2533 - non-experimental implementations are possible, and implementors should 1.2534 - release an unprefixed implementation of any CR-level feature they can 1.2535 - demonstrate to be correctly implemented according to spec. 1.2536 - 1.2537 - <p>To establish and maintain the interoperability of CSS across 1.2538 - implementations, the CSS Working Group requests that non-experimental 1.2539 - CSS renderers submit an implementation report (and, if necessary, the 1.2540 - testcases used for that implementation report) to the W3C before 1.2541 - releasing an unprefixed implementation of any CSS features. Testcases 1.2542 - submitted to W3C are subject to review and correction by the CSS Working 1.2543 - Group. 1.2544 - 1.2545 - <p>Further information on submitting testcases and implementation reports 1.2546 - can be found from on the CSS Working Group's website at <a 1.2547 - href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>. 1.2548 - Questions should be directed to the <a 1.2549 - href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a> 1.2550 - mailing list. 1.2551 - 1.2552 - <h2 class=no-num id=acknowledgments> Acknowledgments</h2> 1.2553 - 1.2554 - <p>This specification would not have been possible without the help from: 1.2555 - 1.2556 - <p>Stephen Deach, Martin Dürst, Hideki Hiura(<span lang=ja>樋浦 1.2557 - 秀樹</span>), Masayasu Ishikawa(<span lang=ja>石川 雅康</span>), 1.2558 - Chris Pratley, Takao Suzuki(<span lang=ja>鈴木 孝雄</span>), Frank 1.2559 - Yung-Fong Tang, Chris Thrasher, Masafumi Yabe<span lang=ja>家辺 1.2560 - 勝文</span>), Steve Zilles. 1.2561 - 1.2562 - <h2 class=no-num id=references> References</h2> 1.2563 - 1.2564 - <h3 class=no-num id=normative-references> Normative references</h3> 1.2565 - <!--begin-normative--> <!-- Sorted by label --> 1.2566 - <dl class=bibliography> 1.2567 - <dd 1.2568 - style="display: none"><!-- keeps the doc valid if the DL is empty --> 1.2569 - <!----> 1.2570 - 1.2571 - <dt id=CSS21>[CSS21] 1.2572 - 1.2573 - <dd>Bert Bos; et al. <a 1.2574 - href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading 1.2575 - Style Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 1.2576 - June 2011. W3C Recommendation. URL: <a 1.2577 - href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a> 1.2578 - </dd> 1.2579 - <!----> 1.2580 - 1.2581 - <dt id=RFC2119>[RFC2119] 1.2582 - 1.2583 - <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key 1.2584 - words for use in RFCs to Indicate Requirement Levels.</cite></a> 1.2585 - Internet RFC 2119. URL: <a 1.2586 - href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 1.2587 - </dd> 1.2588 - <!----> 1.2589 - </dl> 1.2590 - <!--end-normative--> 1.2591 - <h3 class=no-num id=other-references> Other references</h3> 1.2592 - <!--begin-informative--> <!-- Sorted by label --> 1.2593 - <dl class=bibliography> 1.2594 - <dd 1.2595 - style="display: none"><!-- keeps the doc valid if the DL is empty --> 1.2596 - <!----> 1.2597 - 1.2598 - <dt id=CSS3-FONTS>[CSS3-FONTS] 1.2599 - 1.2600 - <dd>John Daggett. <a 1.2601 - href="http://www.w3.org/TR/2013/WD-css3-fonts-20130212/"><cite>CSS 1.2602 - Fonts Module Level 3.</cite></a> 12 February 2013. W3C Working Draft. 1.2603 - (Work in progress.) URL: <a 1.2604 - href="http://www.w3.org/TR/2013/WD-css3-fonts-20130212/">http://www.w3.org/TR/2013/WD-css3-fonts-20130212/</a> 1.2605 - </dd> 1.2606 - <!----> 1.2607 - 1.2608 - <dt id=CSS3-TEXT-DECOR>[CSS3-TEXT-DECOR] 1.2609 - 1.2610 - <dd>Elika J. Etemad; Koji Ishii. <a 1.2611 - href="http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/"><cite>CSS 1.2612 - Text Decoration Module Level 3.</cite></a> 3 January 2013. W3C Working 1.2613 - Draft. (Work in progress.) URL: <a 1.2614 - href="http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/">http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/</a> 1.2615 - </dd> 1.2616 - <!----> 1.2617 - 1.2618 - <dt id=CSS3VAL>[CSS3VAL] 1.2619 - 1.2620 - <dd>Håkon Wium Lie; Tab Atkins; Elika J. Etemad. <a 1.2621 - href="http://www.w3.org/TR/2013/CR-css3-values-20130404/"><cite>CSS 1.2622 - Values and Units Module Level 3.</cite></a> 4 April 2013. W3C Candidate 1.2623 - Recommendation. (Work in progress.) URL: <a 1.2624 - href="http://www.w3.org/TR/2013/CR-css3-values-20130404/">http://www.w3.org/TR/2013/CR-css3-values-20130404/</a> 1.2625 - </dd> 1.2626 - <!----> 1.2627 - 1.2628 - <dt id=JIS4051>[JIS4051] 1.2629 - 1.2630 - <dd><cite>Formatting rules for Japanese documents 1.2631 - (『日本語文書の組版方法』).</cite> Japanese Standards 1.2632 - Association. 2004. JIS X 4051:2004. In Japanese</dd> 1.2633 - <!----> 1.2634 - 1.2635 - <dt id=JLREQ>[JLREQ] 1.2636 - 1.2637 - <dd>Yasuhiro Anan; et al. <a 1.2638 - href="http://www.w3.org/TR/2012/NOTE-jlreq-20120403/"><cite>Requirements 1.2639 - for Japanese Text Layout.</cite></a> 3 April 2012. W3C Working Group 1.2640 - Note. URL: <a 1.2641 - href="http://www.w3.org/TR/2012/NOTE-jlreq-20120403/">http://www.w3.org/TR/2012/NOTE-jlreq-20120403/</a> 1.2642 - </dd> 1.2643 - <!----> 1.2644 - 1.2645 - <dt id=RUBY>[RUBY] 1.2646 - 1.2647 - <dd>Masayasu Ishikawa; et al. <a 1.2648 - href="http://www.w3.org/TR/2001/REC-ruby-20010531"><cite>Ruby 1.2649 - Annotation.</cite></a> 31 May 2001. W3C Recommendation. URL: <a 1.2650 - href="http://www.w3.org/TR/2001/REC-ruby-20010531">http://www.w3.org/TR/2001/REC-ruby-20010531</a> 1.2651 - </dd> 1.2652 - <!----> 1.2653 - </dl> 1.2654 - <!--end-informative--> 1.2655 - <h2 class=no-num id=index> Index</h2> 1.2656 - <!--begin-index--> 1.2657 - <ul class=indexlist> 1.2658 - <li>annotation level, <a href="#level" 1.2659 - title="section 2.3."><strong>2.3.</strong></a> 1.2660 - 1.2661 - <li>Annotation pairing, <a href="#annotation-pairing" 1.2662 - title="section 2.3."><strong>2.3.</strong></a> 1.2663 - 1.2664 - <li>authoring tool, <a href="#authoring-tool" 1.2665 + <h2 id=glossary><span class=secno>5. </span> Glossary</h2> 1.2666 + 1.2667 + <dl> 1.2668 + <dt><a id=g-bopomofo><strong><span lang=zh>Bopomofo</span></strong></a> 1.2669 + 1.2670 + <dd>37 characters and 4 tone markings used as phonetics in Chinese, 1.2671 + especially standard Mandarin. 1.2672 + 1.2673 + <dt><a id=g-hanja><strong><span lang=ko>Hanja</span></strong></a> 1.2674 + 1.2675 + <dd>Subset of the Korean writing system that utilizes ideographic 1.2676 + characters borrowed or adapted from the Chinese writing system. Also see 1.2677 + <a href="#g-kanji"><span lang=ja>Kanji</span></a>. 1.2678 + 1.2679 + <dt><a id=g-hiragana><strong><span lang=ja>Hiragana</span></strong></a> 1.2680 + 1.2681 + <dd>Japanese syllabic script, or character of that script. Rounded and 1.2682 + cursive in appearance. Subset of the Japanese writing system, used 1.2683 + together with kanji and katakana. In recent times, mostly used to write 1.2684 + Japanese words when kanji are not available or appropriate, and word 1.2685 + endings and particles. Also see <a href="#g-katakana"><span 1.2686 + lang=ja>Katakana</span></a>. 1.2687 + 1.2688 + <dt><a id=g-ideogram><strong>Ideograph</strong></a> 1.2689 + 1.2690 + <dd>A character that is used to represent an idea, word, or word 1.2691 + component, in contrast to a character from an alphabetic or syllabic 1.2692 + script. The most well-known ideographic script is used (with some 1.2693 + variation) in East Asia (China, Japan, Korea,...). 1.2694 + 1.2695 + <dt><a id=g-kana><strong><span lang=ja>Kana</span></strong></a> 1.2696 + 1.2697 + <dd>Collective term for hiragana and katakana. 1.2698 + 1.2699 + <dt><a id=g-kanji><strong>Kanji</strong></a> 1.2700 + 1.2701 + <dd>Japanese term for ideographs; ideographs used in Japanese. Subset of 1.2702 + the Japanese writing system, used together with hiragana and katakana. 1.2703 + Also see <a href="#g-hanja"><span lang=ko>Hanja</span></a>. 1.2704 + 1.2705 + <dt><a id=g-katakana><strong><span lang=ja>Katakana</span></strong></a> 1.2706 + 1.2707 + <dd>Japanese syllabic script, or character of that script. Angular in 1.2708 + appearance. Subset of the Japanese writing system, used together with 1.2709 + kanji and hiragana. In recent times, mainly used to write foreign words. 1.2710 + Also see <a href="#g-hiragana"><span lang=ja>Hiragana</span></a>. 1.2711 + 1.2712 + <dt><a id=g-monoruby name=g-monoruby><strong>Mono-ruby</strong></a> 1.2713 + 1.2714 + <dd>In Japanese typography: Ruby associated with a single character of the 1.2715 + base text. 1.2716 + 1.2717 + <dt><a id=g-ruby><strong>Ruby</strong></a> 1.2718 + 1.2719 + <dd>A run of text that appears in the vicinity of another run of text and 1.2720 + serves as an annotation or a pronunciation guide for that text. 1.2721 + </dl> 1.2722 + 1.2723 + <h2 id=conformance><span class=secno>6. </span> Conformance</h2> 1.2724 + 1.2725 + <h3 id=conventions><span class=secno>6.1. </span> Document conventions</h3> 1.2726 + 1.2727 + <p>Conformance requirements are expressed with a combination of descriptive 1.2728 + assertions and RFC 2119 terminology. The key words “MUST”, “MUST 1.2729 + NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, 1.2730 + “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the 1.2731 + normative parts of this document are to be interpreted as described in RFC 1.2732 + 2119. However, for readability, these words do not appear in all uppercase 1.2733 + letters in this specification. 1.2734 + 1.2735 + <p>All of the text of this specification is normative except sections 1.2736 + explicitly marked as non-normative, examples, and notes. <a 1.2737 + href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a> 1.2738 + 1.2739 + <p>Examples in this specification are introduced with the words “for 1.2740 + example” or are set apart from the normative text with 1.2741 + <code>class="example"</code>, like this: 1.2742 + 1.2743 + <div class=example> 1.2744 + <p>This is an example of an informative example. 1.2745 + </div> 1.2746 + 1.2747 + <p>Informative notes begin with the word “Note” and are set apart from 1.2748 + the normative text with <code>class="note"</code>, like this: 1.2749 + 1.2750 + <p class=note>Note, this is an informative note. 1.2751 + 1.2752 + <h3 id=conformance-classes><span class=secno>6.2. </span> Conformance 1.2753 + classes</h3> 1.2754 + 1.2755 + <p>Conformance to CSS Ruby Module is defined for three conformance classes: 1.2756 + 1.2757 + <dl> 1.2758 + <dt><dfn id=style-sheet title="style sheet!!as conformance class">style 1.2759 + sheet</dfn> 1.2760 + 1.2761 + <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS 1.2762 + style sheet</a>. 1.2763 + 1.2764 + <dt><dfn id=renderer>renderer</dfn> 1.2765 + 1.2766 + <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> 1.2767 + that interprets the semantics of a style sheet and renders documents that 1.2768 + use them. 1.2769 + 1.2770 + <dt><dfn id=authoring-tool>authoring tool</dfn> 1.2771 + 1.2772 + <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> 1.2773 + that writes a style sheet. 1.2774 + </dl> 1.2775 + 1.2776 + <p>A style sheet is conformant to CSS Ruby Module if all of its statements 1.2777 + that use syntax defined in this module are valid according to the generic 1.2778 + CSS grammar and the individual grammars of each feature defined in this 1.2779 + module. 1.2780 + 1.2781 + <p>A renderer is conformant to CSS Ruby Module if, in addition to 1.2782 + interpreting the style sheet as defined by the appropriate specifications, 1.2783 + it supports all the features defined by CSS Ruby Module by parsing them 1.2784 + correctly and rendering the document accordingly. However, the inability 1.2785 + of a UA to correctly render a document due to limitations of the device 1.2786 + does not make the UA non-conformant. (For example, a UA is not required to 1.2787 + render color on a monochrome monitor.) 1.2788 + 1.2789 + <p>An authoring tool is conformant to CSS Ruby Module if it writes style 1.2790 + sheets that are syntactically correct according to the generic CSS grammar 1.2791 + and the individual grammars of each feature in this module, and meet all 1.2792 + other conformance requirements of style sheets as described in this 1.2793 + module. 1.2794 + 1.2795 + <h3 id=partial><span class=secno>6.3. </span> Partial implementations</h3> 1.2796 + 1.2797 + <p>So that authors can exploit the forward-compatible parsing rules to 1.2798 + assign fallback values, CSS renderers <strong>must</strong> treat as 1.2799 + invalid (and <a 1.2800 + href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as 1.2801 + appropriate</a>) any at-rules, properties, property values, keywords, and 1.2802 + other syntactic constructs for which they have no usable level of support. 1.2803 + In particular, user agents <strong>must not</strong> selectively ignore 1.2804 + unsupported component values and honor supported values in a single 1.2805 + multi-value property declaration: if any value is considered invalid (as 1.2806 + unsupported values must be), CSS requires that the entire declaration be 1.2807 + ignored. 1.2808 + 1.2809 + <h3 id=experimental><span class=secno>6.4. </span> Experimental 1.2810 + implementations</h3> 1.2811 + 1.2812 + <p>To avoid clashes with future CSS features, the CSS2.1 specification 1.2813 + reserves a <a 1.2814 + href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed 1.2815 + syntax</a> for proprietary and experimental extensions to CSS. 1.2816 + 1.2817 + <p>Prior to a specification reaching the Candidate Recommendation stage in 1.2818 + the W3C process, all implementations of a CSS feature are considered 1.2819 + experimental. The CSS Working Group recommends that implementations use a 1.2820 + vendor-prefixed syntax for such features, including those in W3C Working 1.2821 + Drafts. This avoids incompatibilities with future changes in the draft. 1.2822 + 1.2823 + <h3 id=testing><span class=secno>6.5. </span> Non-experimental 1.2824 + implementations</h3> 1.2825 + 1.2826 + <p>Once a specification reaches the Candidate Recommendation stage, 1.2827 + non-experimental implementations are possible, and implementors should 1.2828 + release an unprefixed implementation of any CR-level feature they can 1.2829 + demonstrate to be correctly implemented according to spec. 1.2830 + 1.2831 + <p>To establish and maintain the interoperability of CSS across 1.2832 + implementations, the CSS Working Group requests that non-experimental CSS 1.2833 + renderers submit an implementation report (and, if necessary, the 1.2834 + testcases used for that implementation report) to the W3C before releasing 1.2835 + an unprefixed implementation of any CSS features. Testcases submitted to 1.2836 + W3C are subject to review and correction by the CSS Working Group. 1.2837 + 1.2838 + <p>Further information on submitting testcases and implementation reports 1.2839 + can be found from on the CSS Working Group's website at <a 1.2840 + href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>. 1.2841 + Questions should be directed to the <a 1.2842 + href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a> 1.2843 + mailing list. 1.2844 + 1.2845 + <h2 class=no-num id=acknowledgments> Acknowledgments</h2> 1.2846 + 1.2847 + <p>This specification would not have been possible without the help from: 1.2848 + 1.2849 + <p>Stephen Deach, Martin Dürst, Hideki Hiura(<span lang=ja>樋浦 1.2850 + 秀樹</span>), Masayasu Ishikawa(<span lang=ja>石川 雅康</span>), 1.2851 + Chris Pratley, Takao Suzuki(<span lang=ja>鈴木 孝雄</span>), Frank 1.2852 + Yung-Fong Tang, Chris Thrasher, Masafumi Yabe<span lang=ja>家辺 1.2853 + 勝文</span>), Steve Zilles. 1.2854 + 1.2855 + <h2 class=no-num id=changes> Changes</h2> 1.2856 + 1.2857 + <p>The following major changes have been made since the previous Working 1.2858 + Draft: 1.2859 + 1.2860 + <dl> 1.2861 + <dt>Remove ‘<code class=property>ruby-span</code>’ and mentions of 1.2862 + <code>rbspan</code>. 1.2863 + 1.2864 + <dd> Explicit spanning is not used in HTML ruby in favor of implicit 1.2865 + spanning. This can't handle some pathological double-sided spanning 1.2866 + cases, but there seems to be no requirement for these at the moment. (For 1.2867 + implementations that support full complex XHTML Ruby, they can imply 1.2868 + spanning from the markup the same magic way that we handle cell spanning 1.2869 + from tables. It doesn't seem necessary to include controls this in Level 1.2870 + 1.) 1.2871 + 1.2872 + <dt>Defer ‘<code class=property>ruby-overhang</code>’ and ‘<code 1.2873 + class=css>ruby-align: line-end</code>’ to Level 2. 1.2874 + 1.2875 + <dd> It's somewhat complicated, advanced feature. Proposal is to make this 1.2876 + behavior UA-defined and provide some examples of acceptable options. 1.2877 + 1.2878 + <dt>Close issue requesting ‘<code class=css>display: rp</code>’: use 1.2879 + ‘<code class=css>display: none</code>’. 1.2880 + 1.2881 + <dd> The i18nwg added an issue requesting a display value for <rp> 1.2882 + elements. They're supposed to be hidden when &tl;ruby> is displayed as 1.2883 + ruby. But this is easily accomplished already with ‘<code 1.2884 + class=css>display: none</code>’. 1.2885 + 1.2886 + <dt>Change ‘<a href="#ruby-position"><code 1.2887 + class=property>ruby-position</code></a>’ values to match ‘<code 1.2888 + class=property>text-emphasis-position</code>’. 1.2889 + 1.2890 + <dd> Other than ‘<code class=css>inter-character</code>’, which we 1.2891 + need to keep, it makes more sense to align ruby positions with ‘<code 1.2892 + class=property>text-emphasis-position</code>’, which can correctly 1.2893 + handle various combinations of horizontal/vertical preferences. 1.2894 + 1.2895 + <dt>Remove unused values of ‘<a href="#ruby-align"><code 1.2896 + class=property>ruby-align</code></a>’. 1.2897 + 1.2898 + <dd> ‘<code class=property>left</code>’, ‘<code 1.2899 + class=property>right</code>’, and ‘<code class=property>end</code>’ 1.2900 + are not needed. 1.2901 + 1.2902 + <dt>Added ‘<a href="#ruby-merge"><code 1.2903 + class=property>ruby-merge</code></a>’ property to control jukugo 1.2904 + rendering. 1.2905 + 1.2906 + <dd> This is a stylistic effect, not a structural one; the previous model 1.2907 + assumed that it was structural and suggested handling it by changing 1.2908 + markup. :( 1.2909 + 1.2910 + <dt>Remove ‘<code class=css>inline</code>’ from ‘<a 1.2911 + href="#ruby-position"><code class=property>ruby-position</code></a>’. 1.2912 + 1.2913 + <dd> This is do-able via ‘<code class=css>display: inline</code>’ on 1.2914 + all the ruby-related elements, see <a href="#default-inline">Appendix 1.2915 + A</a> 1.2916 + 1.2917 + <dt>Added <a href="#default-style">Default Style</a> rules 1.2918 + 1.2919 + <dd> As requested by i18nwg. 1.2920 + 1.2921 + <dt>Wrote anonymous box generation rules 1.2922 + 1.2923 + <dd> And defined pairing of bases and annotations. Should now handle all 1.2924 + the crazy proposed permutations of HTML ruby markup. 1.2925 + </dl> 1.2926 + 1.2927 + <h2 class=no-num id=references> References</h2> 1.2928 + 1.2929 + <h3 class=no-num id=normative-references> Normative references</h3> 1.2930 + <!--begin-normative--> 1.2931 + <!-- Sorted by label --> 1.2932 + 1.2933 + <dl class=bibliography> 1.2934 + <dd style="display: none"><!-- keeps the doc valid if the DL is empty --> 1.2935 + <!----> 1.2936 + 1.2937 + <dt id=CSS21>[CSS21] 1.2938 + 1.2939 + <dd>Bert Bos; et al. <a 1.2940 + href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading Style 1.2941 + Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 June 1.2942 + 2011. W3C Recommendation. URL: <a 1.2943 + href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a> 1.2944 + </dd> 1.2945 + <!----> 1.2946 + 1.2947 + <dt id=RFC2119>[RFC2119] 1.2948 + 1.2949 + <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key 1.2950 + words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet 1.2951 + RFC 2119. URL: <a 1.2952 + href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 1.2953 + </dd> 1.2954 + <!----> 1.2955 + </dl> 1.2956 + <!--end-normative--> 1.2957 + 1.2958 + <h3 class=no-num id=other-references> Other references</h3> 1.2959 + <!--begin-informative--> 1.2960 + <!-- Sorted by label --> 1.2961 + 1.2962 + <dl class=bibliography> 1.2963 + <dd style="display: none"><!-- keeps the doc valid if the DL is empty --> 1.2964 + <!----> 1.2965 + 1.2966 + <dt id=CSS3-FONTS>[CSS3-FONTS] 1.2967 + 1.2968 + <dd>John Daggett. <a 1.2969 + href="http://www.w3.org/TR/2013/WD-css3-fonts-20130212/"><cite>CSS Fonts 1.2970 + Module Level 3.</cite></a> 12 February 2013. W3C Working Draft. (Work in 1.2971 + progress.) URL: <a 1.2972 + href="http://www.w3.org/TR/2013/WD-css3-fonts-20130212/">http://www.w3.org/TR/2013/WD-css3-fonts-20130212/</a> 1.2973 + </dd> 1.2974 + <!----> 1.2975 + 1.2976 + <dt id=CSS3-TEXT-DECOR>[CSS3-TEXT-DECOR] 1.2977 + 1.2978 + <dd>Elika J. Etemad; Koji Ishii. <a 1.2979 + href="http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/"><cite>CSS 1.2980 + Text Decoration Module Level 3.</cite></a> 3 January 2013. W3C Working 1.2981 + Draft. (Work in progress.) URL: <a 1.2982 + href="http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/">http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/</a> 1.2983 + </dd> 1.2984 + <!----> 1.2985 + 1.2986 + <dt id=CSS3VAL>[CSS3VAL] 1.2987 + 1.2988 + <dd>Håkon Wium Lie; Tab Atkins; Elika J. Etemad. <a 1.2989 + href="http://www.w3.org/TR/2013/CR-css3-values-20130404/"><cite>CSS 1.2990 + Values and Units Module Level 3.</cite></a> 4 April 2013. W3C Candidate 1.2991 + Recommendation. (Work in progress.) URL: <a 1.2992 + href="http://www.w3.org/TR/2013/CR-css3-values-20130404/">http://www.w3.org/TR/2013/CR-css3-values-20130404/</a> 1.2993 + </dd> 1.2994 + <!----> 1.2995 + 1.2996 + <dt id=JIS4051>[JIS4051] 1.2997 + 1.2998 + <dd><cite>Formatting rules for Japanese documents 1.2999 + (『日本語文書の組版方法』).</cite> Japanese Standards 1.3000 + Association. 2004. JIS X 4051:2004. In Japanese</dd> 1.3001 + <!----> 1.3002 + 1.3003 + <dt id=JLREQ>[JLREQ] 1.3004 + 1.3005 + <dd>Yasuhiro Anan; et al. <a 1.3006 + href="http://www.w3.org/TR/2012/NOTE-jlreq-20120403/"><cite>Requirements 1.3007 + for Japanese Text Layout.</cite></a> 3 April 2012. W3C Working Group 1.3008 + Note. URL: <a 1.3009 + href="http://www.w3.org/TR/2012/NOTE-jlreq-20120403/">http://www.w3.org/TR/2012/NOTE-jlreq-20120403/</a> 1.3010 + </dd> 1.3011 + <!----> 1.3012 + 1.3013 + <dt id=RUBY>[RUBY] 1.3014 + 1.3015 + <dd>Masayasu Ishikawa; et al. <a 1.3016 + href="http://www.w3.org/TR/2001/REC-ruby-20010531"><cite>Ruby 1.3017 + Annotation.</cite></a> 31 May 2001. W3C Recommendation. URL: <a 1.3018 + href="http://www.w3.org/TR/2001/REC-ruby-20010531">http://www.w3.org/TR/2001/REC-ruby-20010531</a> 1.3019 + </dd> 1.3020 + <!----> 1.3021 + </dl> 1.3022 + <!--end-informative--> 1.3023 + 1.3024 + <h2 class=no-num id=index> Index</h2> 1.3025 + <!--begin-index--> 1.3026 + 1.3027 + <ul class=indexlist> 1.3028 + <li>annotation level, <a href="#level" 1.3029 + title="section 2.3."><strong>2.3.</strong></a> 1.3030 + 1.3031 + <li>Annotation pairing, <a href="#annotation-pairing" 1.3032 + title="section 2.3."><strong>2.3.</strong></a> 1.3033 + 1.3034 + <li>authoring tool, <a href="#authoring-tool" 1.3035 + title="section 6.2."><strong>6.2.</strong></a> 1.3036 + 1.3037 + <li>level, <a href="#level" title="section 2.3."><strong>2.3.</strong></a> 1.3038 + 1.3039 + <li>renderer, <a href="#renderer" 1.3040 + title="section 6.2."><strong>6.2.</strong></a> 1.3041 + 1.3042 + <li>Ruby, <a href="#ruby" title="section 1.4."><strong>1.4.</strong></a> 1.3043 + 1.3044 + <li>ruby-align, <a href="#ruby-align" 1.3045 + title="section 3.3."><strong>3.3.</strong></a> 1.3046 + 1.3047 + <li>ruby-align:auto, <a href="#auto0" 1.3048 + title="section 3.3."><strong>3.3.</strong></a> 1.3049 + 1.3050 + <li>ruby-align:center, <a href="#center" 1.3051 + title="section 3.3."><strong>3.3.</strong></a> 1.3052 + 1.3053 + <li>ruby-align:distribute-letter, <a href="#distribute-letter" 1.3054 + title="section 3.3."><strong>3.3.</strong></a> 1.3055 + 1.3056 + <li>ruby-align:distribute-space, <a href="#distribute-space" 1.3057 + title="section 3.3."><strong>3.3.</strong></a> 1.3058 + 1.3059 + <li>ruby-align:start, <a href="#start" 1.3060 + title="section 3.3."><strong>3.3.</strong></a> 1.3061 + 1.3062 + <li>ruby annotation, <a href="#ruby-annotation" 1.3063 + title="section 2."><strong>2.</strong></a>, <a 1.3064 + href="#ruby-annotation-box" 1.3065 + title="section 2.1."><strong>2.1.</strong></a> 1.3066 + 1.3067 + <li>ruby annotation box, <a href="#ruby-annotation-box" 1.3068 + title="section 2.1."><strong>2.1.</strong></a> 1.3069 + 1.3070 + <li>ruby annotation container, <a href="#ruby-annotation-container-box" 1.3071 + title="section 2.1."><strong>2.1.</strong></a> 1.3072 + 1.3073 + <li>ruby annotation container box, <a 1.3074 + href="#ruby-annotation-container-box" 1.3075 + title="section 2.1."><strong>2.1.</strong></a> 1.3076 + 1.3077 + <li>ruby base, <a href="#ruby-base" 1.3078 + title="section 2."><strong>2.</strong></a>, <a href="#ruby-base-box" 1.3079 + title="section 2.1."><strong>2.1.</strong></a> 1.3080 + 1.3081 + <li>ruby base box, <a href="#ruby-base-box" 1.3082 + title="section 2.1."><strong>2.1.</strong></a> 1.3083 + 1.3084 + <li>ruby base container, <a href="#ruby-base-container-box" 1.3085 + title="section 2.1."><strong>2.1.</strong></a> 1.3086 + 1.3087 + <li>ruby base container box, <a href="#ruby-base-container-box" 1.3088 + title="section 2.1."><strong>2.1.</strong></a> 1.3089 + 1.3090 + <li>ruby container, <a href="#ruby-container-box" 1.3091 + title="section 2.1."><strong>2.1.</strong></a> 1.3092 + 1.3093 + <li>ruby container box, <a href="#ruby-container-box" 1.3094 + title="section 2.1."><strong>2.1.</strong></a> 1.3095 + 1.3096 + <li>ruby-merge, <a href="#ruby-merge" 1.3097 + title="section 3.2."><strong>3.2.</strong></a> 1.3098 + 1.3099 + <li>ruby-merge:auto, <a href="#auto" 1.3100 + title="section 3.2."><strong>3.2.</strong></a> 1.3101 + 1.3102 + <li>ruby-merge:collapse, <a href="#collapse" 1.3103 + title="section 3.2."><strong>3.2.</strong></a> 1.3104 + 1.3105 + <li>ruby-merge:separate, <a href="#separate" 1.3106 + title="section 3.2."><strong>3.2.</strong></a> 1.3107 + 1.3108 + <li>ruby-position, <a href="#ruby-position" 1.3109 + title="section 3.1."><strong>3.1.</strong></a> 1.3110 + 1.3111 + <li>ruby-position:inter-character, <a href="#inter-character" 1.3112 + title="section 3.1."><strong>3.1.</strong></a> 1.3113 + 1.3114 + <li>ruby-position:left, <a href="#left" 1.3115 + title="section 3.1."><strong>3.1.</strong></a> 1.3116 + 1.3117 + <li>ruby-position:over, <a href="#over" 1.3118 + title="section 3.1."><strong>3.1.</strong></a> 1.3119 + 1.3120 + <li>ruby-position:right, <a href="#right" 1.3121 + title="section 3.1."><strong>3.1.</strong></a> 1.3122 + 1.3123 + <li>ruby-position:under, <a href="#under" 1.3124 + title="section 3.1."><strong>3.1.</strong></a> 1.3125 + 1.3126 + <li>ruby segments, <a href="#ruby-segments" 1.3127 + title="section 2."><strong>2.</strong></a> 1.3128 + 1.3129 + <li>style sheet 1.3130 + <ul> 1.3131 + <li>as conformance class, <a href="#style-sheet" 1.3132 title="section 6.2."><strong>6.2.</strong></a> 1.3133 - 1.3134 - <li>level, <a href="#level" 1.3135 - title="section 2.3."><strong>2.3.</strong></a> 1.3136 - 1.3137 - <li>renderer, <a href="#renderer" 1.3138 - title="section 6.2."><strong>6.2.</strong></a> 1.3139 - 1.3140 - <li>Ruby, <a href="#ruby" title="section 1.4."><strong>1.4.</strong></a> 1.3141 - 1.3142 - <li>ruby-align, <a href="#ruby-align" 1.3143 - title="section 3.3."><strong>3.3.</strong></a> 1.3144 - 1.3145 - <li>ruby-align:auto, <a href="#auto0" 1.3146 - title="section 3.3."><strong>3.3.</strong></a> 1.3147 - 1.3148 - <li>ruby-align:center, <a href="#center" 1.3149 - title="section 3.3."><strong>3.3.</strong></a> 1.3150 - 1.3151 - <li>ruby-align:distribute-letter, <a href="#distribute-letter" 1.3152 - title="section 3.3."><strong>3.3.</strong></a> 1.3153 - 1.3154 - <li>ruby-align:distribute-space, <a href="#distribute-space" 1.3155 - title="section 3.3."><strong>3.3.</strong></a> 1.3156 - 1.3157 - <li>ruby-align:start, <a href="#start" 1.3158 - title="section 3.3."><strong>3.3.</strong></a> 1.3159 - 1.3160 - <li>ruby annotation, <a href="#ruby-annotation" 1.3161 - title="section 2."><strong>2.</strong></a>, <a 1.3162 - href="#ruby-annotation-box" 1.3163 - title="section 2.1."><strong>2.1.</strong></a> 1.3164 - 1.3165 - <li>ruby annotation box, <a href="#ruby-annotation-box" 1.3166 - title="section 2.1."><strong>2.1.</strong></a> 1.3167 - 1.3168 - <li>ruby annotation container, <a href="#ruby-annotation-container-box" 1.3169 - title="section 2.1."><strong>2.1.</strong></a> 1.3170 - 1.3171 - <li>ruby annotation container box, <a 1.3172 - href="#ruby-annotation-container-box" 1.3173 - title="section 2.1."><strong>2.1.</strong></a> 1.3174 - 1.3175 - <li>ruby base, <a href="#ruby-base" 1.3176 - title="section 2."><strong>2.</strong></a>, <a href="#ruby-base-box" 1.3177 - title="section 2.1."><strong>2.1.</strong></a> 1.3178 - 1.3179 - <li>ruby base box, <a href="#ruby-base-box" 1.3180 - title="section 2.1."><strong>2.1.</strong></a> 1.3181 - 1.3182 - <li>ruby base container, <a href="#ruby-base-container-box" 1.3183 - title="section 2.1."><strong>2.1.</strong></a> 1.3184 - 1.3185 - <li>ruby base container box, <a href="#ruby-base-container-box" 1.3186 - title="section 2.1."><strong>2.1.</strong></a> 1.3187 - 1.3188 - <li>ruby container, <a href="#ruby-container-box" 1.3189 - title="section 2.1."><strong>2.1.</strong></a> 1.3190 - 1.3191 - <li>ruby container box, <a href="#ruby-container-box" 1.3192 - title="section 2.1."><strong>2.1.</strong></a> 1.3193 - 1.3194 - <li>ruby-merge, <a href="#ruby-merge" 1.3195 - title="section 3.2."><strong>3.2.</strong></a> 1.3196 - 1.3197 - <li>ruby-merge:auto, <a href="#auto" 1.3198 - title="section 3.2."><strong>3.2.</strong></a> 1.3199 - 1.3200 - <li>ruby-merge:collapse, <a href="#collapse" 1.3201 - title="section 3.2."><strong>3.2.</strong></a> 1.3202 - 1.3203 - <li>ruby-merge:separate, <a href="#separate" 1.3204 - title="section 3.2."><strong>3.2.</strong></a> 1.3205 - 1.3206 - <li>ruby-position, <a href="#ruby-position" 1.3207 - title="section 3.1."><strong>3.1.</strong></a> 1.3208 - 1.3209 - <li>ruby-position:inter-character, <a href="#inter-character" 1.3210 - title="section 3.1."><strong>3.1.</strong></a> 1.3211 - 1.3212 - <li>ruby-position:left, <a href="#left" 1.3213 - title="section 3.1."><strong>3.1.</strong></a> 1.3214 - 1.3215 - <li>ruby-position:over, <a href="#over" 1.3216 - title="section 3.1."><strong>3.1.</strong></a> 1.3217 - 1.3218 - <li>ruby-position:right, <a href="#right" 1.3219 - title="section 3.1."><strong>3.1.</strong></a> 1.3220 - 1.3221 - <li>ruby-position:under, <a href="#under" 1.3222 - title="section 3.1."><strong>3.1.</strong></a> 1.3223 - 1.3224 - <li>ruby segments, <a href="#ruby-segments" 1.3225 - title="section 2."><strong>2.</strong></a> 1.3226 - 1.3227 - <li>style sheet 1.3228 - <ul> 1.3229 - <li>as conformance class, <a href="#style-sheet" 1.3230 - title="section 6.2."><strong>6.2.</strong></a> 1.3231 - </ul> 1.3232 </ul> 1.3233 - <!--end-index--> 1.3234 - <h2 class=no-num id=property-index> Property index</h2> 1.3235 - <!--begin-properties--> 1.3236 - <table class=proptable> 1.3237 - <thead> 1.3238 - <tr> 1.3239 - <th>Property 1.3240 - 1.3241 - <th>Values 1.3242 - 1.3243 - <th>Initial 1.3244 - 1.3245 - <th>Applies to 1.3246 - 1.3247 - <th>Inh. 1.3248 - 1.3249 - <th>Percentages 1.3250 - 1.3251 - <th>Media 1.3252 - 1.3253 - <tbody> 1.3254 - <tr> 1.3255 - <th><a class=property href="#ruby-align">ruby-align</a> 1.3256 - 1.3257 - <td>auto | start | center | distribute-letter | distribute-space 1.3258 - 1.3259 - <td>auto 1.3260 - 1.3261 - <td>all elements and generated content 1.3262 - 1.3263 - <td>yes 1.3264 - 1.3265 - <td>N/A 1.3266 - 1.3267 - <td>visual 1.3268 - 1.3269 - <tr> 1.3270 - <th><a class=property href="#ruby-merge">ruby-merge</a> 1.3271 - 1.3272 - <td>separate | collapse | auto 1.3273 - 1.3274 - <td>separate 1.3275 - 1.3276 - <td>all elements and generated content 1.3277 - 1.3278 - <td>yes 1.3279 - 1.3280 - <td>N/A 1.3281 - 1.3282 - <td>visual 1.3283 - 1.3284 - <tr> 1.3285 - <th><a class=property href="#ruby-position">ruby-position</a> 1.3286 - 1.3287 - <td>[ over | under | inter-character ] && [ right | left ] 1.3288 - 1.3289 - <td>over right 1.3290 - 1.3291 - <td>the parent of elements with display: ruby-text. 1.3292 - 1.3293 - <td>yes 1.3294 - 1.3295 - <td>N/A 1.3296 - 1.3297 - <td>visual 1.3298 - </table> 1.3299 - <!--end-properties--> 1.3300 - </dl> 1.3301 + </ul> 1.3302 + <!--end-index--> 1.3303 + 1.3304 + <h2 class=no-num id=property-index> Property index</h2> 1.3305 + <!--begin-properties--> 1.3306 + 1.3307 + <table class=proptable> 1.3308 + <thead> 1.3309 + <tr> 1.3310 + <th>Property 1.3311 + 1.3312 + <th>Values 1.3313 + 1.3314 + <th>Initial 1.3315 + 1.3316 + <th>Applies to 1.3317 + 1.3318 + <th>Inh. 1.3319 + 1.3320 + <th>Percentages 1.3321 + 1.3322 + <th>Media 1.3323 + 1.3324 + <tbody> 1.3325 + <tr> 1.3326 + <th><a class=property href="#ruby-align">ruby-align</a> 1.3327 + 1.3328 + <td>auto | start | center | distribute-letter | distribute-space 1.3329 + 1.3330 + <td>auto 1.3331 + 1.3332 + <td>ruby bases, ruby annotations, ruby base containers, ruby annotation 1.3333 + containers 1.3334 + 1.3335 + <td>yes 1.3336 + 1.3337 + <td>N/A 1.3338 + 1.3339 + <td>visual 1.3340 + 1.3341 + <tr> 1.3342 + <th><a class=property href="#ruby-merge">ruby-merge</a> 1.3343 + 1.3344 + <td>separate | collapse | auto 1.3345 + 1.3346 + <td>separate 1.3347 + 1.3348 + <td>ruby annotation containers 1.3349 + 1.3350 + <td>yes 1.3351 + 1.3352 + <td>N/A 1.3353 + 1.3354 + <td>visual 1.3355 + 1.3356 + <tr> 1.3357 + <th><a class=property href="#ruby-position">ruby-position</a> 1.3358 + 1.3359 + <td>[ over | under | inter-character ] && [ right | left ] 1.3360 + 1.3361 + <td>over right 1.3362 + 1.3363 + <td>ruby annotation containers 1.3364 + 1.3365 + <td>yes 1.3366 + 1.3367 + <td>N/A 1.3368 + 1.3369 + <td>visual 1.3370 + </table> 1.3371 + <!--end-properties--> 1.3372 </html> 1.3373 <!-- Keep this comment at the end of the file 1.3374 Local variables:
2.1 --- a/css-ruby/Overview.src.html Thu Jun 20 15:24:37 2013 -0700 2.2 +++ b/css-ruby/Overview.src.html Thu Jun 20 15:32:56 2013 -0700 2.3 @@ -1,3 +1,12 @@ 2.4 +<!-- 2.5 + 2.6 +Issues: 2.7 + white space 2.8 + line breaking 2.9 + bidi 2.10 + 2.11 +--> 2.12 + 2.13 <!DOCTYPE html> 2.14 <html lang="en"> 2.15 <head> 2.16 @@ -139,6 +148,7 @@ 2.17 They are typically sized to 50% when used as annotations. 2.18 <dt><img alt="Symbolic narrow-cell glyph representation" width="19" height="39" src="images/halfwidth.gif"> 2.19 <dd>Narrow-cell glyph (e.g. Roman) which is the <var>n</var>th glyph in the text run. 2.20 + </dl> 2.21 2.22 <p>The orientation which the above symbols assume in the diagrams 2.23 corresponds to the orientation that the glyphs they represent 2.24 @@ -192,7 +202,7 @@ 2.25 correctly paired with their respective base characters. 2.26 </div> 2.27 2.28 - <i>Ruby</i> formatting as used in Japanese is described in JIS X-4051 [[JIS4051]] (in Japanese) 2.29 + <p><i>Ruby</i> formatting as used in Japanese is described in JIS X-4051 [[JIS4051]] (in Japanese) 2.30 and in Requirements for Japanese Text Layout [[JLREQ]] (in English and Japanese)]. 2.31 In HTML, ruby structure and markup to represent it is described 2.32 in the Ruby Markup Extension specification. 2.33 @@ -592,6 +602,8 @@ 2.34 <h2 id="ruby-props"> 2.35 Ruby Properties</h2> 2.36 2.37 + <p>The following properties are introduced to control ruby positioning and alignment. 2.38 + 2.39 <h3 id="rubypos"> 2.40 Ruby positioning: the 'ruby-position' property</h3> 2.41 2.42 @@ -607,7 +619,7 @@ 2.43 <td>over right 2.44 <tr> 2.45 <th>Applies to: 2.46 - <td>the parent of elements with display: ruby-text. 2.47 + <td>ruby annotation containers 2.48 <tr> 2.49 <th>Inherited: 2.50 <td>yes 2.51 @@ -619,7 +631,7 @@ 2.52 <td>visual 2.53 <tr> 2.54 <th>Computed value: 2.55 - <td>specified value (except for initial and inherit) 2.56 + <td>specified value 2.57 <tr> 2.58 <th>Animatable: 2.59 <td>no 2.60 @@ -627,112 +639,87 @@ 2.61 <th>Canonical order: 2.62 <td><abbr title="follows order of property value definition">per grammar</abbr> 2.63 </table> 2.64 - <p class="issue"><span class="issuehead">Issue: </span> We replaced 'right' with 'inter-character', since that was its original intended purpose and such removes potential ambiguity with 'inline' or 'before'. Bopomofo ruby needs special handling by the implementation, if ruby is to always appear to the right. (Note that the user may also choose to position bopomofo ruby before the base, in which case they would use the normal 'before' setting.)</p> 2.65 - <p>This property is used by the parent of elements with display: ruby-text to 2.66 - control the position of the ruby text with respect to its base. Such parents 2.67 - are typically either the <samp>ruby</samp> element itself (simple ruby) or the 2.68 - <samp>rtc</samp> element (complex ruby). This assures that all parts of a <samp>rtc</samp> 2.69 - element will be displayed in the same position. Possible values:</p> 2.70 + 2.71 + <p>This property controls position of the ruby text with respect to its base. 2.72 + Values have the following meanings: 2.73 + 2.74 <p class="issue"><span class="issuehead">Issue-107: </span> Roland Steiner has requested the addition of an auto value as default. See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=ruby-position%3A+undesirable+default+value+%27before%27+for+complex+ruby&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&period_month=&period_year=&index-grp=Public__FULL&index-type=t&type-index=www-style&resultsperpage=20&sortby=date">this thread</a> and <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=Styling+of+complex+Ruby&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&period_month=&period_year=&index-grp=Public__FULL&index-type=t&type-index=public-i18n-core&resultsperpage=20&sortby=date">this one</a>.</p> 2.75 <dl> 2.76 - <dt><dfn title="ruby-position:over">''over''</dfn></dt> 2.77 - <dd>The ruby text appears over the base in horizontal text. 2.78 - This is the most common setting used in ideographic East Asian writing systems. 2.79 - This is the initial value. 2.80 + <dt><dfn title="ruby-position:over">''over''</dfn> 2.81 + <dd>The ruby text appears <i>over</i> the base in horizontal text. 2.82 2.83 <div class="figure"> 2.84 - <p> 2.85 - <img 2.86 - alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing above the base" 2.87 - src="images/shinkansen-top.gif" width="140" height="33" /></p> 2.88 - <p><b>Figure 4.1.1</b>: Top ruby in horizontal layout applied to 2.89 - Japanese text</p> 2.90 + <p><img src="images/shinkansen-top.gif" 2.91 + alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing above the base"> 2.92 + <p class="caption">Ruby over Japanese base text in horizontal layout 2.93 </div> 2.94 </dd> 2.95 2.96 - <dt><dfn title="ruby-position:right">''right''</dfn></dt> 2.97 + <dt><dfn title="ruby-position:right">''right''</dfn> 2.98 <dd>The ruby text appears on the right side of the base in vertical text. 2.99 - 2.100 <div class="figure"> 2.101 - <p> 2.102 - <img 2.103 - alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the right of the base" 2.104 - src="images/shinkansen-right.gif" width="33" height="141" /></p> 2.105 - <p><b>Figure 4.1.2</b>: Top ruby in vertical ideographic layout applied 2.106 - to Japanese text</p> 2.107 + <p><img src="images/shinkansen-right.gif" width="33" 2.108 + alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the right of the base"> 2.109 + <p class="caption">Ruby to the right of Japanese base text in vertical layout 2.110 </div> 2.111 </dd> 2.112 2.113 - <dt><dfn title="ruby-position:under">''under''</dfn></dt> 2.114 + <dt><dfn title="ruby-position:under">''under''</dfn> 2.115 <dd>The ruby text appears under the base in horizontal text. 2.116 This is a relatively rare setting used in ideographic East Asian writing systems, 2.117 most easily found in educational text. 2.118 2.119 <div class="figure"> 2.120 - <p> 2.121 - <img 2.122 - alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing below the base" 2.123 - src="images/shinkansen-bottom.gif" width="142" height="36" /></p> 2.124 - <p><b>Figure 4.1.3</b>: Bottom ruby in horizontal layout applied to Japanese text</p> 2.125 + <p><img src="images/shinkansen-bottom.gif" 2.126 + alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing below the base"> 2.127 + <p class="caption">Ruby under Japanese base text in horizontal layout 2.128 </div> 2.129 </dd> 2.130 2.131 - <dt><dfn title="ruby-position:left">''left''</dfn></dt> 2.132 + <dt><dfn title="ruby-position:left">''left''</dfn> 2.133 <dd>The ruby text appears on the left side of the base in vertical text. 2.134 2.135 <div class="figure"> 2.136 - <p> 2.137 - <img 2.138 - alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the left of the base" 2.139 - src="images/shinkansen-left.gif" width="37" height="141" /></p> 2.140 - <p><b>Figure 4.1.4</b>: Bottom ruby in vertical ideographic layout applied to Japanese text</p> 2.141 + <p><img src="images/shinkansen-left.gif" 2.142 + alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the left of the base"> 2.143 + <p class="caption">Ruby to the left of Japanese base text in vertical layout 2.144 </div> 2.145 </dd> 2.146 2.147 <dt><dfn title="ruby-position:inter-character">''inter-character''</dfn></dt> 2.148 <dd> 2.149 - <p class="issue"><span class="issuehead">Issue: </span> We replaced 'right' with 'inter-character', since that was its original intended purpose and such removes potential ambiguity with 'inline' or 'before'. Bopomofo ruby needs special handling by the implementation, if ruby is to always appear to the right. (Note that the user may also choose to position bopomofo ruby before the base, in which case they would use the normal 'before' setting.) See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20Vertical+layout+not+enough+for+bopomofo&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">this thread</a> following a request from the i18n WG.</p> 2.150 <p>The ruby text appears on the right of the base in horizontal text. 2.151 - 2.152 - <p>This value is provided for the special case of traditional Chinese as used especially in 2.153 - Taiwan: ruby (made of <a href="#g-bopomofo"><span 2.154 - lang="zh">bopomofo</span></a> glyphs) in that context appears vertically along 2.155 - the right side of the base glyph, 2.156 - even when the layout of the base characters is horizontal:</p> 2.157 + This value forces the 'writing-mode' of the <i>ruby annotation</i> to be vertical. 2.158 + 2.159 + <p>This value is provided for the special case of traditional Chinese 2.160 + as used especially in Taiwan: 2.161 + ruby (made of <a href="#g-bopomofo">bopomofo</a> glyphs) in that context 2.162 + appears vertically along the right side of the base glyph, 2.163 + even when the layout of the base characters is horizontal: 2.164 2.165 <div class="figure"> 2.166 - <p><img alt="Example of Taiwanese-style ruby" 2.167 - width="138" height="42" src="images/bopomofo.gif" /></p> 2.168 - <p><b>Figure 4.1.5</b>: "<span lang="zh">Bopomofo</span>" ruby in 2.169 - traditional Chinese (ruby text shown in blue for clarity) in horizontal 2.170 - layout</p> 2.171 + <p><img src="images/bopomofo.gif" 2.172 + alt="Example of Taiwanese-style ruby"> 2.173 + <p class="caption">“Bopomofo” ruby in traditional Chinese 2.174 + (ruby text shown in blue for clarity) in horizontal layout 2.175 </div> 2.176 - <p class="note"><span class="note-label">Note:</span> The bopomofo 2.177 - transcription is written in the normal way as part of the ruby text. 2.178 - The user agent is responsible for ensuring the correct relative alignment 2.179 - and positioning of the glyphs, including those corresponding to the 2.180 - tone marks, when displaying. Tone marks are spacing characters that occur in memory at the end of the ruby text for each base character. They are usually displayed in a separate column to the right of the bopomofo characters, and the height of the tone mark depends on the number of characters in the syllable. One tone mark, however, is placed above the bopomofo, not to the right of it.</p> 2.181 - <p class="note"><span class="note-label">Note:</span> To make bopomofo annotations appear before or after the base text, like annotations for most other East Asian writing systems, use the 'before' and 'after' values of ruby-position.</p> 2.182 - <p>It is not defined how a user-agent should handle ruby text that is not bopomofo 2.183 - when the value of ruby-position is set to 'inter-character'.</p> 2.184 + <p class="note"> 2.185 + Note that the user agent is responsible for ensuring the correct relative alignment and positioning of the glyphs, 2.186 + including those corresponding to the tone marks, when displaying. 2.187 + Tone marks are spacing characters that occur (in memory) at the end of the ruby text for each base character. 2.188 + They are usually displayed in a separate column to the right of the bopomofo characters, 2.189 + and the height of the tone mark depends on the number of characters in the syllable. 2.190 + One tone mark, however, is placed above the bopomofo, not to the right of it. 2.191 <!-- See Taiwanese requirements doc for EPUB at http://epub-revision.googlecode.com/files/EGLS_TW_eng.ppt --> 2.192 </dd> 2.193 - 2.194 - <!-- 2.195 -<dt><strong>inline</strong></dt> 2.196 -<dd> 2.197 -<p>Ruby text follows the ruby base with no special styling. The value can be used to disable ruby text positioning.</p> 2.198 -<p>If the author has used the XHTML <samp>rp</samp> element [[RUBY]] they should set the <samp>display</samp> value for that element to <samp>inline</samp>, so that the ruby text is distinguishable from the base text. If no <samp>rp</samp> element has been used, the author can use the <samp>content</samp> property with the <samp>:before</samp> and <samp>:after</samp> pseudo-elements to set off the ruby text. </p> 2.199 -<p class="issue"><span class="issuehead">Issue: </span> Here is a <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20inline+value+description+missing&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">request </a>for this section to be added, from the i18n WG..</p> 2.200 -</dd> 2.201 - --> 2.202 </dl> 2.203 2.204 -<p>If two rtc elements are set with the same ruby-position value, (for example 2.205 -both 'before'), the relative position of the two elements is undefined. This 2.206 -setting should not be used.</p> 2.207 + <p>If multiple <i>ruby annotation containers</i> have the same 'ruby-position', 2.208 + they stack along the block axis, 2.209 + with lower levels of annotation closer to the base text. 2.210 2.211 -<h3 id="rubymerge">Ruby merge: the 'ruby-merge' property</h3> 2.212 +<h3 id="collapsed-ruby"> 2.213 +Collapsed Ruby Annotations: the 'ruby-merge' property</h3> 2.214 2.215 <table class="propdef"> 2.216 <tr> 2.217 @@ -746,7 +733,102 @@ 2.218 <td>separate 2.219 <tr> 2.220 <th>Applies to: 2.221 - <td>all elements and generated content 2.222 + <td>ruby annotation containers 2.223 + <tr> 2.224 + <th>Inherited: 2.225 + <td>yes 2.226 + <tr> 2.227 + <th>Percentages: 2.228 + <td>N/A 2.229 + <tr> 2.230 + <th>Media: 2.231 + <td>visual 2.232 + <tr> 2.233 + <th>Computed value: 2.234 + <td>specified value 2.235 + <tr> 2.236 + <th>Animatable: 2.237 + <td>no 2.238 + <tr> 2.239 + <th>Canonical order: 2.240 + <td><abbr title="follows order of property value definition">per grammar</abbr> 2.241 + </table> 2.242 + 2.243 + <p> 2.244 + This property controls how ruby annotation boxes should be rendered 2.245 + when there are more than one in a ruby container box. 2.246 + 2.247 + <p>Possible values:</p> 2.248 + <dl> 2.249 + <dt><dfn title="ruby-merge:separate">''separate''</dfn> 2.250 + <dd> 2.251 + <p> 2.252 + Each ruby annotation box is rendered in the same column(s) as its corresponding base box(es). 2.253 + This style is called “mono ruby” in [[JLREQ]]. 2.254 + 2.255 + <div class="example"> 2.256 + <p>For example, the following two markups render the same: 2.257 + <pre><ruby>無<rt>む</ruby><ruby>常<rt>じょう</ruby></pre> 2.258 + <p>and: 2.259 + <pre><ruby style="ruby-merge:separate"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 2.260 + </div> 2.261 + </dd> 2.262 + 2.263 + <dt><dfn title="ruby-merge:collapse">''collapse''</dfn> 2.264 + <dd> 2.265 + <p> 2.266 + All <i>ruby annotation boxes</i> within the same <i>ruby segment</i> on the same line are concatenated, 2.267 + and laid out as if their contents belonged to a single <i>ruby annotation box</i> 2.268 + spanning all their associated <i>ruby base boxes. 2.269 + This style renders similar to “group ruby” in [[JLREQ]], 2.270 + except that <i>ruby annotations</i> are kept together with their respective <i>ruby bases</i> when breaking lines. 2.271 + </p> 2.272 + 2.273 + <div class="example"> 2.274 + <p>The following two markups render the same both characters fit on one line: 2.275 + <pre><ruby>無常<rt>むじょう</ruby></pre> 2.276 + <p>and: 2.277 + <pre><ruby style="ruby-merge:collapse"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 2.278 + <p>However, the second one renders the same as ''ruby-position: separate'' 2.279 + when the two bases are split across lines. 2.280 + </div> 2.281 + </dd> 2.282 + 2.283 + <dt><dfn title="ruby-merge:auto">''auto''</dfn></dt> 2.284 + <dd> 2.285 + <p> 2.286 + The user agent may use any algorithm to determine how each ruby annotation box 2.287 + is rendered to its corresponding base box. 2.288 + <div class="example"> 2.289 + <p> 2.290 + One possible algorithm is described as Jukugo-ruby in [[JLREQ]]. 2.291 + <p> 2.292 + Another, more simplified algorithm of Jukugo-ruby is 2.293 + to render as Mono-ruby if all ruby annotation boxes fit within 2.294 + advances of their corresponding base boxes, 2.295 + and render as Group-ruby otherwise. 2.296 + </p> 2.297 + </div> 2.298 + </dd> 2.299 + </dl> 2.300 + 2.301 +<h3 id="rubyalign"> 2.302 +Ruby Text Distribution: the 'ruby-align' property</h3> 2.303 + 2.304 + <table class="propdef"> 2.305 + <tr> 2.306 + <th>Name: 2.307 + <td><dfn>ruby-align</dfn> 2.308 + <tr> 2.309 + <th><a href="#values">Value</a>: 2.310 + <td>auto | start | center | 2.311 + distribute-letter | distribute-space 2.312 + <tr> 2.313 + <th>Initial: 2.314 + <td>auto 2.315 + <tr> 2.316 + <th>Applies to: 2.317 + <td>ruby bases, ruby annotations, ruby base containers, ruby annotation containers 2.318 <tr> 2.319 <th>Inherited: 2.320 <td>yes 2.321 @@ -761,109 +843,10 @@ 2.322 <td>specified value (except for initial and inherit) 2.323 </table> 2.324 2.325 - <p> 2.326 - This property controls how ruby annotation boxes should be rendered 2.327 - when there are more than one in a ruby container box. 2.328 - </p> 2.329 + <p>This property specifies how text is distributed within the various ruby boxes 2.330 + when their text contents exactly fill their respective boxes. 2.331 2.332 - <p>Possible values:</p> 2.333 - <dl> 2.334 - <dt><dfn title="ruby-merge:separate">''separate''</dfn></dt> 2.335 - <dd> 2.336 - <p> 2.337 - Each ruby annotation box is rendered in the same column as its corresponding base box. 2.338 - This style is called Mono-ruby in [[JLREQ]]. 2.339 - </p> 2.340 - 2.341 - <div class="example"> 2.342 - <p>The following two markups render the same:</p> 2.343 - <pre><ruby>無<rt>む</ruby><ruby>常<rt>じょう</ruby></pre> 2.344 - <p>and:</p> 2.345 - <pre><ruby style="ruby-merge:separate"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 2.346 - </div> 2.347 - </dd> 2.348 - 2.349 - <dt><dfn title="ruby-merge:collapse">''collapse''</dfn></dt> 2.350 - <dd> 2.351 - <p> 2.352 - All ruby annotation boxes are concatenated, 2.353 - and rendered to the concatenated ruby base boxes. 2.354 - This style renders similar to Group-ruby in [[JLREQ]], 2.355 - except that it allows line break between annotation pairs. 2.356 - </p> 2.357 - 2.358 - <div class="example"> 2.359 - <p>The following two markups render the same if fit in a line:</p> 2.360 - <pre><ruby>無常<rt>むじょう</ruby></pre> 2.361 - <p>and:</p> 2.362 - <pre><ruby style="ruby-merge:collapse"><rb>無<rb>常<rt>む<rt>じょう</ruby></pre> 2.363 - </div> 2.364 - </dd> 2.365 - 2.366 - <dt><dfn title="ruby-merge:auto">''auto''</dfn></dt> 2.367 - <dd> 2.368 - <p> 2.369 - The user agent may use any algorithm to determine how each ruby annotation box 2.370 - is rendered to its corresponding base box. 2.371 - </p> 2.372 - <div class="example"> 2.373 - <p> 2.374 - One possible algorithm is described as Jukugo-ruby in [[JLREQ]]. 2.375 - </p> 2.376 - <p> 2.377 - Another, more simplified algorithm of Jukugo-ruby is 2.378 - to render as Mono-ruby if all ruby annotation boxes fit within 2.379 - advances of their corresponding base boxes, 2.380 - and render as Group-ruby otherwise. 2.381 - </p> 2.382 - </div> 2.383 - </dd> 2.384 - </dl> 2.385 - 2.386 -<h3 id="rubyalign"> 2.387 -Ruby alignment: the 'ruby-align' property</h3> 2.388 - 2.389 - <table class="propdef"> 2.390 - <tr> 2.391 - <th>Name: 2.392 - <td><dfn>ruby-align</dfn> 2.393 - <tr> 2.394 - <th><a href="#values">Value</a>: 2.395 - <td>auto | start | center | 2.396 - distribute-letter | distribute-space 2.397 - <tr> 2.398 - <th>Initial: 2.399 - <td>auto 2.400 - <tr> 2.401 - <th>Applies to: 2.402 - <td>all elements and generated content 2.403 - <tr> 2.404 - <th>Inherited: 2.405 - <td>yes 2.406 - <tr> 2.407 - <th>Percentages: 2.408 - <td>N/A 2.409 - <tr> 2.410 - <th>Media: 2.411 - <td>visual 2.412 - <tr> 2.413 - <th>Computed value: 2.414 - <td>specified value (except for initial and inherit) 2.415 - </table> 2.416 - 2.417 - <p>This property can be used on any element to control the text alignment of 2.418 - the ruby text and ruby base contents relative to each other. It applies to all 2.419 - the rubys in the element. For simple ruby, the alignment is applied to the 2.420 - ruby child element whose content is shorter: either the <a 2.421 - href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element or the <a 2.422 - href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element [[RUBY]]. 2.423 - For complex ruby, the alignment is also applied to the 2.424 - ruby child elements whose content is shorter: either the <samp>rb</samp> 2.425 - element and/or one or two <samp>rt</samp> elements for each related ruby text 2.426 - and ruby base element within the <samp>rtc</samp> and <samp>rbc</samp> 2.427 - element.</p> 2.428 - 2.429 - <p>Possible values:</p> 2.430 + <p>Values have the following meanings: 2.431 <p class="issue"><span class="issuehead">Issue: </span> Tony Graham has <a href="http://www.w3.org/Style/XSL/Group/FO/wiki/Ruby#Treat_CSS3_.22ruby-align.22_As_Shorthand.3F">suggested </a>that distribute-letter and distribute-space be values of a ruby-group-distribution property, and line-edge be moved to a ruby-alignment-edge property, and that the rest be gathered under a ruby-alignment property. And that ruby-align become a shorthand.</p> 2.432 <dl> 2.433 <dt><dfn title="ruby-align:auto">''auto''</dfn></dt> 2.434 @@ -897,9 +880,7 @@ 2.435 </dd> 2.436 2.437 <dt><dfn title="ruby-align:start">''start''</dfn></dt> 2.438 - <dd>The ruby text content is aligned with the start edge of the base. 2.439 - <p class="issue"><span class="issuehead">Issue: </span> The i18n WG feels that start and left should not be synonymous, and proposed to drop left (there is no left/right in overhang)? See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20left/start+and+right/end&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date">this thread</a>.</p> 2.440 - 2.441 + <dd>The ruby annotation content is aligned with the start edge of the base. 2.442 <div class="figure"> 2.443 <p><img 2.444 alt="Diagram of glyph layout in left aligned ruby when ruby text is shorter than base"
