changeset
[css-ruby] Switch to using preprocessor for CSS Ruby
Mon, 17 Jun 2013 21:35:27 +0900
- author
- fantasai <fantasai.cvs@inkedblade.net>
- date
- Mon, 17 Jun 2013 21:35:27 +0900
- changeset 8479
- 8a1d4d700090
- parent 8478
- faaa922ab689
- child 8480
- 7260288accfa
[css-ruby] Switch to using preprocessor for CSS Ruby
| 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 Mon Jun 17 20:37:15 2013 +0900 1.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 1.3 @@ -1,1262 +0,0 @@ 1.4 -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 1.5 -"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 1.6 - 1.7 -<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"> 1.8 - 1.9 -<head> 1.10 - <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 1.11 - <title>CSS3 Ruby Module</title> 1.12 - <style type="text/css"> 1.13 - dt {font-weight: normal} 1.14 - /*.issue, .note {font-style: italic}*/ 1.15 - .figure {font-size: smaller;} 1.16 - span.note-label {font-weight: bolder;} 1.17 - 1.18 - /* Stolen from CSS2 Recommendation */ 1.19 - DIV.propdef TH { 1.20 - text-align: right; 1.21 - } 1.22 - 1.23 - A.propdef-title { 1.24 - background: yellow; 1.25 - } 1.26 - 1.27 - DIV.propdef {margin: 1.2em 0} 1.28 - 1.29 - A.noxref:link, A.noxref:visited {color: black; /*color: inherit*/} 1.30 - </style> 1.31 - <style media="print" type="text/css"> 1.32 - img#edge { width: 80%; height: 70%;}dt.label { display: run-in; } 1.33 - 1.34 - </style> 1.35 - 1.36 - 1.37 -<link href="../default.css" rel="stylesheet" type="text/css" /> 1.38 - 1.39 -<link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" /> 1.40 - 1.41 -<style type="text/css"> 1.42 -ins { 1.43 - background-color: #99FF99; 1.44 - text-decoration: none; 1.45 - } 1.46 -del { 1.47 - display: inline; 1.48 - color: silver; 1.49 - } 1.50 -.issue { color: #F00; } 1.51 -.issuehead { background-color:#FF9; } 1.52 -</style> 1.53 -</head> 1.54 - 1.55 -<body> 1.56 - 1.57 -<div class="head"> 1.58 -<p><a href="http://www.w3.org/"><img alt="W3C" src="http://www.w3.org/Icons/w3c_home" height="48" width="72" /></a></p> 1.59 - 1.60 -<h1>CSS3 Ruby Module</h1> 1.61 - 1.62 -<h2 class="no-num no-toc" id="w3c-working">W3C Working Draft 03 December 2010 (Editor's copy)</h2> 1.63 -<dl> 1.64 - <dt>This version:</dt> 1.65 - <dd><a 1.66 - href="http://dev.w3.org/csswg/css3-ruby/">http://dev.w3.org/csswg/css3-ruby/</a></dd> 1.67 - <dt>Latest version:</dt> 1.68 - <dd><a 1.69 - href="http://www.w3.org/TR/css3-ruby">http://www.w3.org/TR/css3-ruby</a></dd> 1.70 -<dt>Previous version:</dt> 1.71 - <dd><a 1.72 - href="http://www.w3.org/TR/2003/CR-css3-ruby-20030514">http://www.w3.org/TR/2003/CR-css3-ruby-20030514</a></dd> 1.73 - <dt>Feedback: 1.74 - <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-ruby%5D%20feedback">www-style@w3.org</a> 1.75 - with subject line “<kbd>[css-ruby] <var>… message topic …</var></kbd>” 1.76 - (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/">archives</a>) 1.77 - 1.78 - <dt>Editor:</dt> 1.79 - <dd><a href="mailto:rishida@w3.org">Richard Ishida (W3C)</a></dd> 1.80 - <dt>Former editors:</dt> 1.81 - <dd><a href="mailto:paulnel@microsoft.com">Paul Nelson (Microsoft)</a></dd> 1.82 - <dd><a href="mailto:michelsu@microsoft.com">Michel Suignard (Microsoft)</a></dd> 1.83 - <dd><a href="mailto:marcins@microsoft.com">Marcin Sawicki (Microsoft)</a></dd> 1.84 -</dl> 1.85 - 1.86 -<p class="copyright"><a 1.87 -href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"> 1.88 -Copyright</a> © 2010 <a href="http://www.w3.org/"><abbr 1.89 -title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a 1.90 -href="http://www.lcs.mit.edu/"><abbr title="Massachusetts Institute of 1.91 -Technology">MIT</abbr></a>, <a 1.92 -href="http://www.ercim.eu/"><acronym title="European Research 1.93 -Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a 1.94 -href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a 1.95 -href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, 1.96 -<a 1.97 -href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, 1.98 -<a 1.99 -href="http://www.w3.org/Consortium/Legal/copyright-documents">document 1.100 -use</a> and <a 1.101 -href="http://www.w3.org/Consortium/Legal/copyright-software">software 1.102 -licensing</a> rules apply.</p> 1.103 -</div> 1.104 -<hr /> 1.105 - 1.106 -<details open class='obsolete'> 1.107 - <summary>Not Actively Maintained</summary> 1.108 - <p>This specification is not being actively maintained, and should not be used as a guide for implementations. It may be revived in the future, but for now should be considered obsolete. <br>If you have questions or comments on this specification, please send an email to the CSS Working Group's mailing list at <a href="mailto:www-style@w3.org">www-style@w3.org</a>. (Before sending mail for the first time, you have to subscribe at <a href="http://lists.w3.org/Archives/Public/www-style/">http://lists.w3.org/Archives/Public/www-style/</a>.) 1.109 -</details> 1.110 - 1.111 -<h2><a id="Abstract">Abstract</a></h2> 1.112 - 1.113 -<p>"Ruby" are short runs of text alongside the base text, typically 1.114 -used in East Asian documents to indicate pronunciation or to provide a 1.115 -short annotation. This document proposes a set of CSS properties 1.116 -associated with the 'Ruby' elements. They can be used in combination 1.117 -with the Ruby elements of HTML [<a href="#ruby">RUBY</a>].</p> 1.118 - 1.119 -<h2><a id="Status">Status of This Document</a></h2> 1.120 - 1.121 -<p class="issue">Text marked as an "<span class="issuehead">Issue</span>" and any change-marked text all indicate proposals that are currently awaiting or under discussion. All such text is subject to modification or removal. Once it is felt that the proposal is acceptable, the change marks will be removed.</p> 1.122 -<p class="issue">See <a href="http://www.w3.org/Style/CSS/Tracker/products/25"> open issues in 1.123 -Tracker.</a></p> 1.124 -<p><strong style="">This document is an editors' copy that has no official standing.</strong></p> 1.125 - 1.126 -<p><em>This section describes the status of this document at the time of 1.127 - its publication. Other documents may supersede this document. A list of 1.128 - current W3C publications and the latest revision of this technical report 1.129 - can be found in the <a href="http://www.w3.org/TR/">W3C technical reports 1.130 - index at http://www.w3.org/TR/.</a></em></p> 1.131 - 1.132 - 1.133 -<p>Publication as a Working Draft does not imply endorsement by the W3C 1.134 - Membership. This is a draft document and may be updated, replaced or 1.135 - obsoleted by other documents at any time. It is inappropriate to cite 1.136 - this document as other than work in progress.</p> 1.137 - 1.138 -<p>The (<a href="http://lists.w3.org/Archives/Public/www-style/">archived</a>) 1.139 - public mailing list <a href="mailto:www-style@w3.org">www-style@w3.org</a> (see <a href="http://www.w3.org/Mail/Request">instructions</a>) is preferred for 1.140 - discussion of this specification. When sending e-mail, please put the 1.141 - text “css3-ruby” in the subject, preferably like this: 1.142 - “[<!---->css3-ruby<!---->] <em>…summary of comment…</em>”</p> 1.143 - 1.144 -<p>This document was produced by the <a href="/Style/CSS/members">CSS 1.145 - Working Group</a> (part of the <a href="/Style/">Style Activity</a>).</p> 1.146 - 1.147 -<p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 1.148 - 2004 W3C Patent Policy</a>. W3C maintains a <a href="/Style/CSS/Disclosures" rel="disclosure">public list of any patent 1.149 - disclosures</a> made in connection with the deliverables of the group; 1.150 - that page also includes instructions for disclosing a patent. An 1.151 - individual who has actual knowledge of a patent which the individual 1.152 - believes contains <a href="/Consortium/Patent-Policy-20040205/#def-essential">Essential 1.153 - Claim(s)</a> must disclose the information in accordance with <a href="/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of 1.154 - the W3C Patent Policy</a>.</p> 1.155 - 1.156 - <!--end-status--> 1.157 -<p>This document contains the <abbr title="Cascading Style 1.158 - Sheets">CSS3</abbr> Ruby Module W3C <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD"> Working 1.159 - Draft</a> of 3 February 2010.</p> 1.160 - 1.161 -<p>The comments that the CSS WG received during the previous Last Call review, 1.162 - together with responses and resulting changes are listed in the <a 1.163 -href="/Style/2003/css3-ruby-last-call">disposition of comments.</a></p> 1.164 -<div class="subtoc"> 1.165 - <h2><a id="Contents">Contents</a></h2> 1.166 -<ul class="toc"> 1.167 - <li class="tocline2"><a href="#dependencies" class="tocxref">1. Dependencies</a></li> 1.168 - <li class="tocline2"><a href="#introduction" class="tocxref">2. Introduction</a> 1.169 - <ul class="toc"> 1.170 - <li class="tocline3"><a href="#conventions" class="tocxref">2.1 Document conventions</a></li> 1.171 - <li class="tocline3"><a href="#ruby-def" class="tocxref">2.2 What is ruby?</a></li> 1.172 - </ul> 1.173 - </li> 1.174 - <li class="tocline2"><a href="#css-model" class="tocxref">3. The CSS ruby model</a> 1.175 - <ul class="toc"> 1.176 - <li class="tocline3"><a href="#display" class="tocxref">3.1 Ruby specific 'display' property values</a></li> 1.177 - <li class="tocline3"><a href="#box-model" class="tocxref">3.2 Ruby box model</a></li> 1.178 - <li class="tocline3"><a href="#ruby-line-height" class="tocxref">3.3 Ruby box and line 1.179 - stacking</a></li> 1.180 - <li class="tocline3"><a href="#ruby-line-breaking" class="tocxref">3.4 Ruby box and line 1.181 - breaking</a></li> 1.182 - </ul> 1.183 - </li> 1.184 - <li class="tocline2"><a href="#ruby-props" class="tocxref">4. Ruby Properties</a> 1.185 - <ul class="toc"> 1.186 - <li class="tocline3"><a href="#rubypos" class="tocxref">4.1 Ruby 1.187 - positioning: the 'ruby-position' property</a></li> 1.188 - <li class="tocline3"><a href="#rubyalign" class="tocxref">4.2 Ruby 1.189 - alignment: the 'ruby-align' property</a></li> 1.190 - <li class="tocline3"><a href="#rubyover" class="tocxref">4.3 Ruby 1.191 - overhanging: the 'ruby-overhang' property</a></li> 1.192 - <li class="tocline3"><a href="#rubyspan" class="tocxref">4.4 Ruby 1.193 - annotation spanning: the 'ruby-span' property</a></li> 1.194 - </ul> 1.195 - </li> 1.196 - <li class="tocline2"><a href="#properties" class="tocxref">5. Properties index</a></li> 1.197 - <li class="tocline2"><a href="#profiles" class="tocxref">6. Profiles</a></li> 1.198 - <li class="tocline2"><a href="#glossary" class="tocxref">Glossary</a></li> 1.199 - <li class="tocline2"><a href="#ack" class="tocxref">Acknowledgements</a></li> 1.200 - <li class="tocline2"><a href="#references" class="tocxref">References</a></li> 1.201 -</ul> 1.202 -</div> 1.203 - 1.204 -<hr /> 1.205 - 1.206 -<h2><a id="dependencies">1. Dependencies on other modules</a></h2> 1.207 - 1.208 -<p>This CSS3 module depends on the following other CSS3 modules:</p> 1.209 -<ul> 1.210 - <li>Text</li> 1.211 - <li>Line</li> 1.212 - <li>Syntax</li> 1.213 - <li>Values and units</li> 1.214 -</ul> 1.215 -<p class="issue"><span class="issuehead">Issue: </span> Check these dependencies are correct.</p> 1.216 -<h2><a id="introduction">2. Introduction</a></h2> 1.217 - 1.218 -<h3><a id="conventions">2.1 Document conventions</a></h3> 1.219 - 1.220 -<p>There are a number of illustrations in this document for which the following 1.221 -legend is used:</p> 1.222 - 1.223 -<p><img alt="Symbolic wide-cell glyph representation" class="example" 1.224 -width="39" height="39" src="images/fullwidth.gif" /> - wide-cell glyph (e.g. Han) 1.225 -which is the <i>n</i>-th character in the text run, they may also appear as 1.226 -half size boxes when used as annotations.<br /> 1.227 -<img alt="Symbolic narrow-cell glyph representation" class="example" 1.228 -width="19" height="39" src="images/halfwidth.gif" /> - narrow-cell glyph (e.g. Roman) 1.229 -which is the <i>n</i>-th glyph in the text run.<br /> 1.230 -</p> 1.231 - 1.232 -<p>Many typographical properties in East Asian typography depend on the fact 1.233 -that a character is typically rendered as either a wide or narrow character. All 1.234 -characters described by the Unicode Standard <a href="#UNICODE">[UNICODE]</a> can be categorized by a 1.235 -width property. This is covered by the Unicode Standard Annex 1.236 -<a href="#UAX11">[UAX#11]</a>. </p> 1.237 - 1.238 -<p>The orientation which the above symbols assume in the diagrams corresponds 1.239 -to the orientation that the glyphs they represent are intended to assume when 1.240 -rendered by the user agent. Spacing between these characters in the diagrams is 1.241 -usually symbolic, unless intentionally changed to make a point.</p> 1.242 - 1.243 -<p>Finally, in this document, requirements are expressed using the key words 1.244 -"MUST", "MUST NOT", "REQUIRED", "SHALL" and "SHALL NOT". Recommendations are 1.245 -expressed using the key words "SHOULD", "SHOULD NOT" and "RECOMMENDED". "MAY" 1.246 -and "OPTIONAL" are used to indicate optional features or behavior. These 1.247 -keywords are used in accordance with <a href="#rfc2119">[RFC 2119]</a>. For 1.248 -legibility these keywords are used in lowercase form.</p> 1.249 - 1.250 -<h3><a id="ruby-def">2.2 What is ruby?</a></h3> 1.251 - 1.252 -<p>"Ruby" is the commonly used name for a run of text that appears in the 1.253 -immediate vicinity of another run of text, referred to as the "base", and 1.254 -serves as an annotation or a pronunciation guide associated with that run of 1.255 -text. Ruby, as used in Japanese, is described in JIS X-4051 [<a 1.256 -href="#jis4051">JIS4051</a>] (in Japanese) and in Requirements for Japanese Text Layout [<a href="#jlreq">JLREQ</a>] (in English and Japanese)]. The ruby structure and the XHTML markup to represent it 1.257 -is described in the Ruby Annotation [<a href="#ruby">RUBY</a>] specification. This 1.258 -section describes the CSS properties relevant to ruby. The following figures 1.259 -show two examples of Ruby.</p> 1.260 - 1.261 -<div class="figure"> 1.262 -<p> 1.263 -<img alt="Example of ruby applied on top of a Japanese expression" 1.264 -class="example" src="images/licence.png" /></p> 1.265 - 1.266 -<p><b>Figure 2.2.1</b>: Example of ruby used in Japanese (simple case)</p> 1.267 -</div> 1.268 - 1.269 -<div class="figure"> 1.270 -<p> 1.271 -<img 1.272 -alt="Example showing complex ruby with annotation text before and after 1.273 -the base characters" 1.274 -class="example" src="images/ruby-univ.gif" width="277" height="108" /></p> 1.275 - 1.276 -<p><strong>Figure 2.2.2</strong>: Complex ruby with annotation text before and after 1.277 -the base characters</p> 1.278 -</div> 1.279 - 1.280 -<p>In the first example, a single annotation is used to annotate the base 1.281 -sequence. In Japanese typography, this simple case is sometimes called "<span lang="ja">taigo</span> ruby" or group-ruby (per-word ruby).</p> 1.282 - 1.283 -<p>In the second example, multiple annotations are attached to a base 1.284 -sequence, the hiragana characters on top refer to the pronunciation of each of the 1.285 -base Kanji characters (annotated in a <a href="#g-monoruby">mono-ruby</a> fashion), while the words 'Keio' 1.286 -and 'University' on the bottom are 1.287 -annotations describing the English translation of respectively the first four 1.288 -and the last two Kanji characters 1.289 -of the base. To allow correct association between the hiragana characters and 1.290 -their corresponding Kanji base characters, the spacing between these Kanji 1.291 -characters may be adjusted (this happens around the fourth Kanji character in the 1.292 -figure 2.2.2 above).</p> 1.293 - 1.294 -<p class="Note"><span class="note-label">Note:</span> To avoid variable spacing between the Kanji 1.295 -characters in the example above the hiragana annotations can also be created as 1.296 -a simple annotation ruby.</p> 1.297 - 1.298 -<p>The two examples correspond respectively to two types of ruby: simple ruby using simple ruby markup and complex ruby using complex ruby 1.299 -markup.</p> 1.300 - 1.301 -<h2><a id="css-model">3. The CSS ruby model</a></h2> 1.302 - 1.303 -<h3 id="display">3.1 Ruby specific 'display' property values</h3> 1.304 - 1.305 -<p>The CSS ruby model is based on the W3C Ruby Annotation Recommendation 1.306 -[<a href="#ruby">RUBY</a>], which is consistent with the XHTML Modularization 1.307 -Framework [<a href="#xhtml-mod">XHTMLMOD</a>]. The Recommendation specifies the ruby structure in a way 1.308 -to closely parallel 1.309 -the visual layout of the ruby element. In this model, a ruby consists of one 1.310 -or more base elements associated with one or more annotation elements.</p> 1.311 - 1.312 -<p>The CSS model does not require that the document language include elements 1.313 -that correspond to each of these components. For document languages (such as 1.314 -XML applications) that do not have pre-defined ruby elements, authors must map 1.315 -document language elements to ruby elements; this is done with the 'display' 1.316 -property. The following 'display' values assign ruby semantics to an arbitrary 1.317 -element:</p> 1.318 -<dl> 1.319 - <dt><strong>ruby</strong> (in XHTML: ruby)</dt> 1.320 - <dd>Specifies that an element defines a ruby structure.</dd> 1.321 - <dt><strong>ruby-base</strong> (in XHTML: rb)</dt> 1.322 - <dd>Specifies that an element defines a ruby base.</dd> 1.323 - <dt><strong>ruby-text</strong> (in XHTML: rt)</dt> 1.324 - <dd>Specifies that an element defines a ruby text.</dd> 1.325 - <dt><strong>ruby-base-container</strong> (in XHTML: rbc)</dt> 1.326 - <dd>Specifies that an element contains one or more ruby base.</dd> 1.327 - <dt><strong>ruby-text-container</strong> (in XHTML: rtc)</dt> 1.328 - <dd>Specifies that an element contains one or more ruby text.</dd> 1.329 -</dl> 1.330 - 1.331 -<p class="issue"><span class="issuehead">Issue: </span> I18n WG proposes that there should be a display value rp also, to allow XML-based formats to associate rp behaviour with elements. See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20display:+rp+value&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">thread</a>.</p> 1.332 - 1.333 -<p>The <a 1.334 -href="http://www.w3.org/TR/ruby/#ruby"><samp>rbspan</samp></a> attribute should 1.335 -also be used by XML applications to allow annotation spanning; but in addition, the 1.336 -'<a href="#ruby-span">ruby-span</a>' property must be used by those applications to indicate to the user agent the number of 1.337 -ruby base elements to be spanned.</p> 1.338 - 1.339 -<h3><a id="box-model">3.2 Ruby box model</a></h3> 1.340 - 1.341 -<p class="issue"><span class="issuehead">Issue: </span> The spec needs to address anonymous box generation rules (and to make them compatible with HTML5 ruby markup).</p> 1.342 -<p>In the following description, the elements specified by Ruby 1.343 -Annotation [<a href="#ruby">RUBY</a>] are used to describe the box model. As mentioned 1.344 -earlier, a user agent can obtain the same results by using the Ruby specific 'display' 1.345 -property values. </p> 1.346 - 1.347 -<p>For a user agent that supports the ruby markup, the ruby structure consists of three or more 1.348 -boxes. The outermost container is the <a 1.349 -href="http://www.w3.org/TR/ruby/#ruby"><samp>ruby</samp></a> element itself. 1.350 -In the simple case, it is a container for two non-overlapping boxes: the ruby 1.351 -text box (<a href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element) 1.352 -and the ruby base box (<a 1.353 -href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element). The 1.354 -positioning of these two boxes relative to each other is controlled by the <a 1.355 -href="#rubypos">'ruby-position'</a> property.</p> 1.356 - 1.357 -<div class="figure"> 1.358 -<img class="example" width="223" height="93" 1.359 -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.360 -src="images/r-box-t.gif" /> 1.361 - 1.362 -<p><b>Figure 3.2.1</b>: Ruby box model (simple case)</p> 1.363 -</div> 1.364 - 1.365 -<p>In the case of complex ruby, the ruby element is a container for two or 1.366 -three non-overlapping boxes: one ruby base collection (<a 1.367 -href="http://www.w3.org/TR/ruby/#rbc"><samp>rbc</samp></a> element), and one 1.368 -or two ruby text collections (<a 1.369 -href="http://www.w3.org/TR/ruby/#rtc"><samp>rtc</samp></a> element). The 1.370 -<samp>rbc</samp> element is itself a container for one or several ruby base 1.371 -box (<samp>rb</samp> element), while each <samp>rtc</samp> element is a 1.372 -container for one or several ruby text box (rt element). The position of the 1.373 -<samp>rtc</samp> element in relation to the related <samp>rbc</samp> element 1.374 -is controlled by the <a href="#rubypos">'ruby-position'</a> property. The two 1.375 -following figures show examples of these complex ruby.</p> 1.376 - 1.377 -<div class="figure"> 1.378 -<img src="images/r-box-g.gif" 1.379 -alt="Diagram of a group ruby with a full ruby text above and partial ruby text below" width="408" height="170" /> 1.380 - 1.381 -<p><b>Figure 3.2.2</b>: Ruby box model (complex ruby with an empty rt element 1.382 -after)</p> 1.383 -</div> 1.384 - 1.385 -<p>In the example above, the ruby text after (below) the ruby bases contains two <samp>rt</samp> elements with the first one 1.386 -being empty, the empty <samp>rt</samp> element corresponds to the first part 1.387 -of the ruby base collection (the first part is identified by the first <samp>rb</samp> element 1.388 -within the <samp> rbc</samp> element).</p> 1.389 - 1.390 -<div class="figure"> 1.391 -<img src="images/r-box-h.gif" 1.392 -alt="Diagram of a group ruby with a spanning ruby text above and partial ruby text below" width="400" height="173" /> 1.393 - 1.394 -<p><b>Figure 3.2.3</b>: Ruby box model (complex ruby with a spanning ruby text 1.395 -element)</p> 1.396 -</div> 1.397 - 1.398 -<p>In the example above, the ruby text before (above) the ruby bases spans the whole ruby base collection. The 1.399 -ruby text after (below) the ruby bases still contain two <samp>rt</samp> elements, one of 1.400 -which is empty. The spanning behavior of <samp>rt</samp> text elements is 1.401 -controlled by the <a 1.402 -href="http://www.w3.org/TR/ruby/#ruby"><samp>rbspan</samp></a> attribute in a 1.403 -way similar to the <samp>colspan</samp> attribute used for table column.</p> 1.404 - 1.405 -<p class="issue"><span class="issuehead">Issue: </span> The examples above contain the term 'group ruby', which is not used elsewhere in this specification. It appears to be used in a way that is different to the use of the term in JLREQ. I propose to replace it with just 'ruby'.</p> 1.406 -<p class="note"><span class="note-label">Note:</span> The visual description of the ruby elements does not refer 1.407 -necessarily to the logical orders of the elements</p> 1.408 - 1.409 -<p>The width of the ruby box is by default determined by its widest child 1.410 -element, whose width in turn is determined by its content. The width of all direct 1.411 -children of the <samp>ruby</samp> element is the width of the widest children. In this respect, the ruby 1.412 -box is much like a two or three row <samp>table</samp> element, with the 1.413 -following exceptions:</p> 1.414 -<ul> 1.415 - <li>the ruby box is an inline element, like an image, even though it itself, 1.416 - like a table, is a container of other boxes</li> 1.417 - <li>the equivalent of the cells: the <samp>rb</samp> element and the 1.418 - <samp>rt</samp> text element can only contain inline-level elements.</li> 1.419 - <li>the content of each 'cell' is always measured at its maximum width</li> 1.420 - <li>unlike a table, a ruby element doesn't have to fit in a line, the ruby 1.421 - box may be split into several boxes at line boundary, depending of the 1.422 - spanning of the ruby texts. This is however only possible for the complex 1.423 - ruby and can only happen at the boundary of non spanning elements.</li> 1.424 - <li>both the ruby text and the ruby base boxes may overlap with adjacent 1.425 - text (outside of the ruby element) if an appropriate <a 1.426 - href="#rubyover">'ruby-overhang'</a> parameter is set via CSS. Note 1.427 - however that the actual content of the ruby base cannot overlap with that 1.428 - adjacent text. The distribution of the content of the ruby base within the 1.429 - ruby base box is controlled by the <a href="#rubyalign">'ruby-align'</a> 1.430 - property.</li> 1.431 -</ul> 1.432 - 1.433 -<p>If the ruby text is not allowed to overhang, then the ruby behaves like a 1.434 -traditional box, i.e. only its contents are rendered within its boundaries and 1.435 -adjacent elements do not cross the box boundary:</p> 1.436 - 1.437 -<div class="figure"> 1.438 -<p><img class="example" width="220" height="91" 1.439 -alt="Diagram showing the ruby boxes interacting with adjacent text" 1.440 -src="images/ro-n.gif" /></p> 1.441 - 1.442 -<p><b>Figure 3.2.4</b>: Simple ruby whose text is not allowed to overhang 1.443 -adjacent text</p> 1.444 -</div> 1.445 - 1.446 -<p>However, if ruby text is allowed to overhang adjacent elements and it 1.447 -happens to be wider than its base, then the adjacent content is partially 1.448 -rendered within the area of the ruby base box, while the ruby text may be 1.449 -partially overlapping with the upper blank parts of the adjacent content:</p> 1.450 - 1.451 -<div class="figure"> 1.452 -<p><img class="example" width="177" height="91" 1.453 -alt="Diagram showing the ruby boxes interacting with adjacent text" 1.454 -src="images/ro-a.gif" /></p> 1.455 - 1.456 -<p><b>Figure 3.2.5</b>: Simple ruby whose text is allowed to overhang adjacent 1.457 -text</p> 1.458 -</div> 1.459 - 1.460 -<p>The ruby text related to a ruby base can never overhang another ruby 1.461 -base.</p> 1.462 - 1.463 -<p>The alignment of the contents of the base or the ruby text is not affected 1.464 -by the overhanging behavior. The alignment is achieved the same way regardless 1.465 -of the overhang behavior setting and it is computed before the space available 1.466 -for overlap is determined. It is controlled by the <a 1.467 -href="#rubyalign">'ruby-align'</a> property.</p> 1.468 - 1.469 -<p>The exact circumstances in which the ruby text will overhang other 1.470 -elements, and to what degree it will do so, will be controlled by the <a 1.471 -href="#rubyover">'ruby-overhang'</a> property.</p> 1.472 - 1.473 -<p>This entire logic applies the same way in vertical ideographic layout, only 1.474 -the dimension in which it works in such a layout is vertical, instead of 1.475 -horizontal.</p> 1.476 - 1.477 -<p class="note"><span class="note-label">Note:</span> Because the purpose of the XHTML <samp>rp</samp> element [<a 1.478 -href="#ruby">RUBY</a>] is to allow pre-existing user agents 1.479 -to parenthesize ruby text content, an XHTML user agent should use a styling rule 1.480 -for these elements that avoids rendering them such as <samp>rp {display: 1.481 -none}</samp>.</p> 1.482 - 1.483 -<h3><a id="ruby-line-height">3.3 Ruby box and line stacking</a></h3> 1.484 - 1.485 -<p>The interaction of the ruby box and line stacking is controlled by the 1.486 -'line-stacking-ruby' property described in the CSS3 Line Module. That property 1.487 -takes two values: 'include-ruby' and 'exclude-ruby. Depending on the property 1.488 -value, the ruby box is considered or excluded for line stacking. Even if the 1.489 -ruby box is considered for line stacking, some values of the 1.490 -'line-stacking-strategy' property (also described in the CSS3 Line module) can 1.491 -still create occurrences where a the ruby box will eventually be ignored (e.g. 1.492 -case where the 'line-stacking-strategy' value is 'block-line-height').</p> 1.493 - 1.494 -<p>In the following figure, each line box is shown with leading space 1.495 -distributed before and after the two text segments ('Previous line' and 'Ruby 1.496 -base'); the dotted lines show the line box for each line. The 1.497 -'line-stacking-ruby' property is set to 'exclude-ruby'. The achieved effect is 1.498 -that the ruby box does not affect the line to line spacing. It is however the 1.499 -responsibility of the style author to avoid 'bleeding' effects between the ruby 1.500 -text and the surrounding text of images.</p> 1.501 - 1.502 -<div class="figure"> 1.503 -<p> 1.504 -<img class="example" 1.505 -alt="Diagram showing the ruby text using 2 half leading" 1.506 -src="images/rlh-a.gif" width="210" height="138" /></p> 1.507 - 1.508 -<p><b>Figure 3.3.1</b>: Excluded Ruby text</p> 1.509 -</div> 1.510 - 1.511 - 1.512 -<p>In the following figure, the line boxes have no extra leading space. The 1.513 -'line-stacking-ruby' property is set to 'include-ruby' and the 1.514 -'line-stacking-strategy' property is set to a value where inline boxes are 1.515 -considered for line stacking. In this case, the line box with 1.516 -the ruby text is affected and has its 'stack-height' increased by the amount 1.517 -necessary to fit the ruby text.</p> 1.518 - 1.519 -<div class="figure"> 1.520 -<p> 1.521 -<img class="example" 1.522 -alt="Diagram showing the ruby text expanding above base text" 1.523 -src="images/rlh-b.gif" width="210" height="111" /></p> 1.524 - 1.525 -<p><b>Figure 3.3.2</b>: Ruby text increasing line height</p> 1.526 -</div> 1.527 -<p>This mechanism allows rendering of evenly spaced lines of text within a 1.528 -block-level element, whether a line contains ruby or not. The authors need 1.529 -only to set for the block-level element a line height value larger than the 1.530 -computed line-height of the largest ruby element within the block.</p> 1.531 - 1.532 -<h3><a id="ruby-line-breaking">3.4 Ruby box and line breaking</a></h3> 1.533 - 1.534 -<p>When a ruby falls at the end of a line where there is not sufficient room for the entire ruby to fit on the line, the complex ruby may be broken at locations where boxes of the ruby container align. Some examples are provided below to provide more clarity.</p> 1.535 - 1.536 -<p> 1.537 -<img class="example" 1.538 -alt="Diagram showing the line breaking opportunity in a complex ruby" 1.539 -src="images/r-break-a.gif" width="408" height="201" /></p> 1.540 - 1.541 -<p><b>Figure 3.4.1</b>: Complex ruby line breaking opportunity</p> 1.542 - 1.543 -<p> 1.544 -<img class="example" 1.545 -alt='Diagram showing the line breaking opportunity in a "Bopomofo" ruby' 1.546 -src="images/r-break-b.gif" width="300" height="90" /></p> 1.547 - 1.548 -<p><b>Figure 3.4.1</b>: "Bopomofo" ruby line breaking opportunity</p> 1.549 -<p class="issue"><span class="issuehead">Issue: </span> Line breaks should only be allowed within ruby if the ruby base text can be broken at that point. E.g. if complex Ruby is used to annotate the two morphemes of "butterfly", the fact that we have added ruby annotations should not cause a line breaking opportunity to be present between "butter" and "fly" </p> 1.550 -<h2><a id="ruby-props">4. Ruby Properties</a></h2> 1.551 - 1.552 -<p>All properties, in addition to the noted values, take 'initial' and 1.553 -'inherit'. These values are not repeated in each of the property value 1.554 -enumeration. </p> 1.555 - 1.556 -<h3><a id="rubypos"></a>4.1 Ruby positioning: the <a href="#ruby-position">'ruby-position'</a> property</h3> 1.557 - 1.558 -<table class="propdef" cellspacing="0" cellpadding="0"> 1.559 - <tbody> 1.560 - <tr align="left"><th>Name:</th><th id="ruby-position">ruby-position</th></tr> 1.561 - <tr> 1.562 - <td><em>Value:</em></td> 1.563 - <td>before | after | inter-character | inline</td> 1.564 - </tr> 1.565 - <tr> 1.566 - <td><em>Initial:</em></td> 1.567 - <td>before</td> 1.568 - </tr> 1.569 - <tr> 1.570 - <td><em>Applies to:</em></td> 1.571 - <td>the parent of elements with display: ruby-text.</td> 1.572 - </tr> 1.573 - <tr> 1.574 - <td><em>Inherited:</em></td> 1.575 - <td>yes</td> 1.576 - </tr> 1.577 - <tr> 1.578 - <td><em>Percentages:</em></td> 1.579 - <td>N/A</td> 1.580 - </tr> 1.581 - <tr> 1.582 - <td><em>Media:</em></td> 1.583 - <td>visual</td> 1.584 - </tr> 1.585 - <tr> 1.586 - <td><em>Computed value: </em></td> 1.587 - <td>specified value (except for initial and inherit)</td> 1.588 - </tr> 1.589 - </tbody> 1.590 - </table> 1.591 -<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> 1.592 -<p>This property is used by the parent of elements with display: ruby-text to 1.593 - control the position of the ruby text with respect to its base. Such parents 1.594 - are typically either the <samp>ruby</samp> element itself (simple ruby) or the 1.595 - <samp>rtc</samp> element (complex ruby). This assures that all parts of a <samp>rtc</samp> 1.596 -element will be displayed in the same position. Possible values:</p> 1.597 -<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> 1.598 -<dl> 1.599 - <dt><strong>before</strong></dt> 1.600 - <dd>The ruby text appears before the base. This is the most common setting 1.601 - used in ideographic East Asian writing systems. This is the initial 1.602 - value. 1.603 - 1.604 - <div class="figure"> 1.605 - <p> 1.606 - <img 1.607 - alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing above the base" 1.608 - class="example" src="images/shinkansen-top.gif" width="140" height="33" /></p> 1.609 - <p><b>Figure 4.1.1</b>: Top ruby in horizontal layout applied to 1.610 - Japanese text</p> 1.611 - </div> 1.612 - <p>If the base appears in a vertical-ideographic layout mode, the ruby 1.613 - appears on the right side of the base and is rendered in the same layout 1.614 - mode as the base (i.e. vertical-ideographic).</p> 1.615 - 1.616 - <div class="figure"> 1.617 - <p> 1.618 - <img 1.619 - alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the right of the base" 1.620 - class="example" src="images/shinkansen-right.gif" width="33" height="141" /></p> 1.621 - <p><b>Figure 4.1.2</b>: Top ruby in vertical ideographic layout applied 1.622 - to Japanese text</p> 1.623 - </div> 1.624 -</dd> 1.625 - <dt><strong>after</strong></dt> 1.626 - <dd>The ruby text appears after the base. This is a relatively rare 1.627 - setting used in ideographic East Asian writing systems, most easily 1.628 - found in educational text. 1.629 - 1.630 - <div class="figure"> 1.631 - <p> 1.632 - <img 1.633 - alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing below the base" 1.634 - class="example" src="images/shinkansen-bottom.gif" width="142" height="36" /></p> 1.635 - <p><b>Figure 4.1.3</b>: Bottom ruby in horizontal layout applied to 1.636 - Japanese text</p> 1.637 - </div> 1.638 - <p>If the base appears in a vertical ideographic mode, the bottom ruby 1.639 - appears on the left side of the base and is rendered in the same layout 1.640 - mode as the base (i.e. vertical).</p> 1.641 - 1.642 - <div class="figure"> 1.643 - <p> 1.644 - <img 1.645 - alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the left of the base" 1.646 - class="example" src="images/shinkansen-left.gif" width="37" height="141" /></p> 1.647 - <p><b>Figure 4.1.4</b>: Bottom ruby in vertical ideographic layout applied 1.648 - to Japanese text</p> 1.649 - </div> 1.650 - </dd> 1.651 - <dt><strong>inter-character</strong></dt> 1.652 - <dd> 1.653 - <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> 1.654 - <p>The ruby text appears on the right of the base. Unlike 'before' and 1.655 - 'after', this value is visual and is not relative to the text flow direction.</p> 1.656 - 1.657 - <p>This value is provided for the special case of traditional Chinese as used especially in 1.658 - Taiwan: ruby (made of <a href="#g-bopomofo"><span 1.659 - lang="zh">bopomofo</span></a> glyphs) in that context appears vertically along 1.660 - the right side of the base glyph, whether the layout of the base characters is vertical or horizontal:</p> 1.661 - 1.662 - <div class="figure"> 1.663 - <p><img alt="Example of Taiwanese-style ruby" class="example" 1.664 - width="138" height="42" src="images/bopomofo.gif" /></p> 1.665 - <p><b>Figure 4.1.5</b>: "<span lang="zh">Bopomofo</span>" ruby in 1.666 - traditional Chinese (ruby text shown in blue for clarity) in horizontal 1.667 - layout</p> 1.668 - </div> 1.669 - <p class="note"><span class="note-label">Note:</span> The bopomofo 1.670 - transcription is written in the normal way as part of the ruby text. 1.671 - The user agent is responsible for ensuring the correct relative alignment 1.672 - and positioning of the glyphs, including those corresponding to the 1.673 - 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> 1.674 - <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> 1.675 - <p>It is not defined how a user-agent should handle ruby text that is not bopomofo when the value of ruby-position is set to 'right'.</p> 1.676 - <!-- See Taiwanese requirements doc for EPUB at http://epub-revision.googlecode.com/files/EGLS_TW_eng.ppt --> 1.677 - </dd> 1.678 -<dt><strong>inline</strong></dt> 1.679 -<dd> 1.680 -<p>Ruby text follows the ruby base with no special styling. The value can be used to disable ruby text positioning.</p> 1.681 -<p>If the author has used the XHTML <samp>rp</samp> element [<a href="#ruby">RUBY</a>] 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.682 -<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.683 -</dd> 1.684 -</dl> 1.685 - 1.686 -<p>If two rtc elements are set with the same ruby-position value, (for example 1.687 -both 'before'), the relative position of the two elements is undefined. This 1.688 -setting should not be used.</p> 1.689 - 1.690 -<h3>4<a id="rubyalign">.2 Ruby alignment: the 'ruby-align' property</a></h3> 1.691 - 1.692 - <table class="propdef" cellspacing="0" cellpadding="0"> 1.693 - <tbody> 1.694 - <tr align="left"><th>Name:</th><th id="ruby-align">ruby-align</th></tr> 1.695 - <tr> 1.696 - <td><em>Value:</em></td> 1.697 - <td>auto | start | left | center | end | right | distribute-letter | 1.698 - distribute-space | line-edge</td> 1.699 - </tr> 1.700 - <tr> 1.701 - <td><em>Initial:</em></td> 1.702 - <td>auto</td> 1.703 - </tr> 1.704 - <tr> 1.705 - <td><em>Applies to:</em></td> 1.706 - <td>all elements and generated content</td> 1.707 - </tr> 1.708 - <tr> 1.709 - <td><em>Inherited:</em></td> 1.710 - <td>yes</td> 1.711 - </tr> 1.712 - <tr> 1.713 - <td><em>Percentages: </em></td> 1.714 - <td>N/A</td> 1.715 - </tr> 1.716 - <tr> 1.717 - <td><em>Media:</em></td> 1.718 - <td>visual</td> 1.719 - </tr> 1.720 - <tr> 1.721 - <td><em>Computed value: </em></td> 1.722 - <td>specified value (except for initial and inherit)</td> 1.723 - </tr> 1.724 - </tbody> 1.725 - </table> 1.726 - 1.727 -<p>This property can be used on any element to control the text alignment of 1.728 -the ruby text and ruby base contents relative to each other. It applies to all 1.729 -the rubys in the element. For simple ruby, the alignment is applied to the 1.730 -ruby child element whose content is shorter: either the <a 1.731 -href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element or the <a 1.732 -href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element [<a 1.733 -href="#ruby">RUBY</a>]. For complex ruby, the alignment is also applied to the 1.734 -ruby child elements whose content is shorter: either the <samp>rb</samp> 1.735 -element and/or one or two <samp>rt</samp> elements for each related ruby text 1.736 -and ruby base element within the <samp>rtc</samp> and <samp>rbc</samp> 1.737 -element.</p> 1.738 - 1.739 -<p>Possible values:</p> 1.740 -<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> 1.741 -<dl> 1.742 - <dt><strong>auto</strong></dt> 1.743 - <dd>The user agent determines how the ruby contents are aligned. This is 1.744 - the initial value. The behavior recommended by [<a href="#jlreq">JLREQ</a>] is for wide-cell ruby to be aligned in the 'distribute-space' mode: 1.745 -<div class="figure"> 1.746 - <p><img class="example" width="145" height="91" 1.747 - alt="Diagram of glyph layout in auto aligned ruby when ruby text is shorter than base" 1.748 - src="images/ra-ds.gif" /><img class="example" width="145" height="91" 1.749 - alt="Diagram of glyph layout in auto aligned ruby when ruby text is longer than base" 1.750 - src="images/ra-ds-rb.gif" /></p> 1.751 - <p><b>Figure 4.2.1</b>: Wide-cell text in 'auto' ruby alignment is 1.752 - 'distribute-space' justified</p> 1.753 - </div> 1.754 - <p>The recommended behavior for narrow-cell glyph ruby is to be 1.755 - aligned in the 'center' mode.</p> 1.756 - 1.757 - <div class="figure"> 1.758 - <p><img 1.759 - alt="Diagram of glyph layout in auto aligned ruby when halfwidth ruby text is shorter than base" 1.760 - class="example" width="145" height="91" 1.761 - src="images/ra-c-h.gif" /><img 1.762 - alt="Diagram of character layout in auto aligned ruby when ruby text is longer than narrow-width base" 1.763 - class="example" width="145" height="91" 1.764 - src="images/ra-c-rb-h.gif" /></p> 1.765 - <p><b>Figure 4.2.2</b>: Narrow-width ruby text in 'auto' ruby alignment 1.766 - is centered</p> 1.767 - </div> 1.768 - </dd> 1.769 - <dt><strong>left</strong></dt> 1.770 - <dd>The ruby text content is aligned with the start edge of the base. 1.771 - 1.772 - <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> 1.773 - 1.774 - <div class="figure"> 1.775 - <p><img 1.776 - alt="Diagram of glyph layout in left aligned ruby when ruby text is shorter than base" 1.777 - class="example" width="145" height="91" src="images/ra-l.gif" /><img 1.778 - class="example" width="145" height="91" 1.779 - alt="Diagram of glyph layout in left aligned ruby when ruby text is longer than base" 1.780 - src="images/ra-l-rb.gif" /></p> 1.781 - <p><b>Figure 4.2.3</b>: Start ruby alignment</p> 1.782 - </div> 1.783 - </dd> 1.784 - <dt><strong>center</strong></dt> 1.785 - <dd>The ruby text content is centered within the width of the base. If the 1.786 - length of the base is smaller than the length of the ruby text, then the 1.787 - base is centered within the width of the ruby text. 1.788 - 1.789 - <div class="figure"> 1.790 - <p><img class="example" width="145" height="91" 1.791 - alt="Diagram of glyph layout in center aligned ruby when ruby text is shorter than base" 1.792 - src="images/ra-c.gif" /><img class="example" width="145" height="91" 1.793 - alt="Diagram of glyph layout in center aligned ruby when ruby text is longer than base" 1.794 - src="images/ra-c-rb.gif" /></p> 1.795 - <p><b>Figure 4.2.4</b>: Center ruby alignment</p> 1.796 - </div> 1.797 - </dd> 1.798 - <dt><strong>right</strong></dt> 1.799 - <dd>The ruby text content is aligned with the end edge of the base. 1.800 - <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.801 -<div class="figure"> 1.802 - <p><img class="example" width="145" height="91" 1.803 - alt="Diagram of glyph layout in right aligned ruby when ruby text is shorter than base" 1.804 - src="images/ra-r.gif" /><img class="example" width="145" height="91" 1.805 - alt="Diagram of glyph layout in right aligned ruby when ruby text is longer than base" 1.806 - src="images/ra-r-rb.gif" /></p> 1.807 - <p><b>Figure 4.2.5</b>: End ruby alignment</p> 1.808 -</div> 1.809 - </dd> 1.810 - <dt><strong>distribute-letter</strong></dt> 1.811 - <dd>If the width of the ruby text is smaller than that of the base, then 1.812 - the ruby text contents are evenly distributed across the width of the 1.813 - base, with the first and last ruby text glyphs lining up with the 1.814 - corresponding first and last base glyphs. If the width of the ruby text 1.815 - is at least the width of the base, then the letters of the base are 1.816 - evenly distributed across the width of the ruby text. 1.817 - 1.818 - <div class="figure"> 1.819 - <p><img class="example" width="145" height="91" 1.820 - alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is shorter than base" 1.821 - src="images/ra-dl.gif" /><img class="example" width="145" height="91" 1.822 - alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is longer than base" 1.823 - src="images/ra-dl-rb.gif" /></p> 1.824 - <p><b>Figure 4.2.6</b>: Distribute-letter ruby alignment</p> 1.825 - </div> 1.826 - </dd> 1.827 - <dt><strong>distribute-space</strong></dt> 1.828 - <dd>If the width of the ruby text is smaller than that of the base, then 1.829 - the ruby text contents are evenly distributed across the width of the 1.830 - base, with a certain amount of white space preceding the first and 1.831 - following the last character in the ruby text. That amount of white 1.832 - space is normally equal to half the amount of inter-character space of 1.833 - the ruby text. If the width of the ruby text is at least the width of 1.834 - the base, then the same type of space distribution applies to the base. 1.835 - In other words, if the base is shorter than the ruby text, the base is 1.836 - distribute-space aligned. This type of alignment 1.837 - is described by [<a href="#jlreq">JLREQ</a>]. 1.838 - <div class="figure"> 1.839 - <p><img class="example" width="145" height="91" 1.840 - alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is shorter than base" 1.841 - src="images/ra-ds.gif" /><img class="example" width="145" height="91" 1.842 - alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is longer than base" 1.843 - src="images/ra-ds-rb.gif" /></p> 1.844 - <p><b>Figure 4.2.7</b>: Distribute-space ruby alignment</p> 1.845 - </div> 1.846 - </dd> 1.847 - <dt><strong>line-edge</strong></dt> 1.848 - <dd>If the ruby text is not adjacent to a line edge, it is aligned as in 1.849 - 'auto'. If it is adjacent to a line edge, then it is still aligned as in 1.850 - auto, but the side of the ruby text that touches the end of the line is 1.851 - lined up with the corresponding edge of the base. This type of alignment 1.852 - is described by [<a href="#jlreq">JLREQ</a>]. This type of alignment is 1.853 - relevant only to the scenario where the ruby text is longer than the 1.854 - ruby base. In the other scenarios, this is just 'auto'. 1.855 - <div class="figure"> 1.856 - <p><img class="example" width="146" height="109" 1.857 - alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is shorter than base" 1.858 - src="images/ra-le-l.gif" /><img class="example" width="146" 1.859 - height="110" 1.860 - alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is longer than base" 1.861 - src="images/ra-le-r.gif" /></p> 1.862 - <p><b>Figure 4.2.8</b>: Line edge ruby alignment</p> 1.863 - </div> 1.864 - </dd> 1.865 -</dl> 1.866 - 1.867 -<p>For a complex ruby with spanning elements, one additional consideration is 1.868 -required. If the spanning element spans multiple 'rows' (other rbc or rtc 1.869 -elements), and the ruby alignment requires space distribution among the 1.870 -'spanned' elements, a ratio must be determined among the 'columns' of spanned 1.871 -elements. This ratio is computed by taking into consideration the widest 1.872 -element within each column.</p> 1.873 - 1.874 -<p>In the context of this property, the 'left' and 'right' values are 1.875 -synonymous with the 'start' and 'end' values respectively. I.e. their meaning 1.876 -is relative according to the text layout flow. Most of the other CSS 1.877 -properties interpret 'left' and 'right' on an 'absolute' term. See Appendix A 1.878 -of the <a href="#CSS3TEXT">CSS3 Text Module</a> for further details.</p> 1.879 - 1.880 -<h3>4<a id="rubyover">.3 Ruby overhanging: the 'ruby-overhang' property</a></h3> 1.881 - 1.882 - <table class="propdef" cellspacing="0" cellpadding="0"> 1.883 - <tbody> 1.884 - <tr align="left"><th>Name:</th><th id="ruby-overhang">ruby-overhang</th></tr> 1.885 - <tr> 1.886 - <td><em>Value:</em></td> 1.887 - <td>auto | start | end | none</td> 1.888 - </tr> 1.889 - <tr> 1.890 - <td><em>Initial:</em></td> 1.891 - <td>none</td> 1.892 - </tr> 1.893 - <tr> 1.894 - <td><em>Applies to:</em></td> 1.895 - <td>the parent of elements with display: ruby-text</td> 1.896 - </tr> 1.897 - <tr> 1.898 - <td><em>Inherited:</em></td> 1.899 - <td>yes</td> 1.900 - </tr> 1.901 - <tr> 1.902 - <td><em>Percentages: </em></td> 1.903 - <td>N/A</td> 1.904 - </tr> 1.905 - <tr> 1.906 - <td><em>Media:</em></td> 1.907 - <td>visual</td> 1.908 - </tr> 1.909 - <tr> 1.910 - <td><em>Computed value: </em></td> 1.911 - <td>specified value (except for initial and inherit)</td> 1.912 - </tr> 1.913 - </tbody> 1.914 - </table> 1.915 - 1.916 -<p>This property determines whether, and on which side, ruby text is allowed 1.917 -to partially overhang any adjacent text in addition to its own base, when the 1.918 -ruby text is wider than the ruby base. Note that ruby text is never allowed to 1.919 -overhang glyphs belonging to another ruby base. <span class="issue"><span class="issuehead">Issue: </span> This rule must be broken if we are to allow support for jukugo ruby.</span> Also the user agent is free to assume 1.920 -a maximum amount by which ruby text may overhang adjacent text. The user agent may use 1.921 -the [<a href="#jis4051">JIS4051</a>] recommendation of using one ruby text character 1.922 -length as the maximum overhang length. Detailed rules for how ruby text can overhang adjacent characters for Japanese are described by [<a href="#jlreq">JLREQ</a>].</p> 1.923 - 1.924 -<p>Possible values:</p> 1.925 -<dl> 1.926 - <dt><strong>auto</strong></dt> 1.927 - <dd>The ruby text can overhang text adjacent to the base on either side. [<a href="#jlreq">JLREQ</a>] and [<a href="#jis4051">JIS4051</a>] specify the categories of characters that 1.928 - ruby text can overhang. The user agent is free to follow those recommendations or specify its own classes of 1.929 - characters to overhang. This is the initial value. 1.930 - <div class="figure"> 1.931 - <p><img class="example" width="177" height="91" 1.932 - alt="Diagram of glyph layout in overhanging ruby" src="images/ro-a.gif" /></p> 1.933 - <p><b>Figure 4.3.1</b>: Ruby overhanging adjacent text</p> 1.934 - </div> 1.935 - </dd> 1.936 - <dt><strong>start</strong></dt> 1.937 - <dd>The ruby text can only overhang the text that precedes it. That means, for 1.938 - example, that ruby cannot overhang text that is to the right of it in 1.939 - horizontal LTR layout, and it cannot overhang text that is below it in 1.940 - vertical-ideographic layout. 1.941 - <div class="figure"> 1.942 - <p><img class="example" width="199" height="91" 1.943 - alt="Diagram of glyph layout when ruby overhangs the preceding glyphs only" 1.944 - src="images/ro-s.gif" /></p> 1.945 - <p><b>Figure 4.3.2</b>: Ruby overhanging preceding text only</p> 1.946 - </div> 1.947 - </dd> 1.948 - <dt><strong>end</strong></dt> 1.949 - <dd>The ruby text can only overhang the text that follows it. That means, for 1.950 - example, that ruby cannot overhang text that is to the left of it in 1.951 - horizontal LTR layout, and it cannot overhang text that is above it in 1.952 - vertical-ideographic layout. 1.953 - <div class="figure"> 1.954 - <p><img class="example" width="198" height="91" 1.955 - alt="Diagram of glyph layout when ruby overhangs the following characters only" 1.956 - src="images/ro-e.gif" /></p> 1.957 - <p><b>Figure 4.3.3</b>: Ruby overhanging following text only</p> 1.958 - </div> 1.959 - </dd> 1.960 - <dt><strong>none</strong></dt> 1.961 - <dd>The ruby text cannot overhang any text adjacent to its base, only its 1.962 - own base. 1.963 - 1.964 - <div class="figure"> 1.965 - <p><img class="example" width="220" height="91" 1.966 - alt="Diagram of glyph layout in non-overhanging ruby" 1.967 - src="images/ro-n.gif" /></p> 1.968 - <p><b>Figure 4.3.4</b>: Ruby not allowed to overhang adjacent text</p> 1.969 - </div> 1.970 - </dd> 1.971 -</dl> 1.972 - 1.973 -<h3>4<a id="rubyspan">.4 Ruby annotation spanning: the 'ruby-span' property</a></h3> 1.974 - 1.975 - <table class="propdef" cellspacing="0" cellpadding="0"> 1.976 - <tbody> 1.977 - <tr align="left"><th>Name:</th><th id="ruby-span">ruby-span</th></tr> 1.978 - <tr> 1.979 - <td><em>Value:</em></td> 1.980 - <td>attr(x) | none</td> 1.981 - </tr> 1.982 - <tr> 1.983 - <td><em>Initial:</em></td> 1.984 - <td>none</td> 1.985 - </tr> 1.986 - <tr> 1.987 - <td><em>Applies to:</em></td> 1.988 - <td>elements with display: ruby-text</td> 1.989 - </tr> 1.990 - <tr> 1.991 - <td><em>Inherited:</em></td> 1.992 - <td>no</td> 1.993 - </tr> 1.994 - <tr> 1.995 - <td><em>Percentages: </em></td> 1.996 - <td>N/A</td> 1.997 - </tr> 1.998 - <tr> 1.999 - <td><em>Media:</em></td> 1.1000 - <td>visual</td> 1.1001 - </tr> 1.1002 - <tr> 1.1003 - <td><em>Computed value: </em></td> 1.1004 - <td><number></td> 1.1005 - </tr> 1.1006 - </tbody> 1.1007 - </table> 1.1008 - 1.1009 -<p>This property controls the spanning behavior of annotation elements. </p> 1.1010 - 1.1011 -<p class="note"><span class="note-label">Note:</span> A XHTML user agent may also use the <samp>rbspan</samp> 1.1012 -attribute to get the same effect.</p> 1.1013 - 1.1014 -<p>Possible values:</p> 1.1015 - 1.1016 -<dl> 1.1017 - <dt><strong>attr(x)</strong></dt> 1.1018 - <dd>The value of attribute 'x' as a string value. The string value is 1.1019 - evaluated as a <number> to determine the number of ruby base elements to be 1.1020 - spanned by the annotation element. If the <number> is '0', it is replaced by 1.1021 - '1'.The <number> is the computed value. </dd> 1.1022 - <dt>none</dt> 1.1023 - <dd>No spanning. The computed value is '1'.</dd> 1.1024 -</dl> 1.1025 - 1.1026 -<p>The following example shows an XML example using the 'display' property 1.1027 -values associated with the 'ruby structure and the 'ruby-span' property</p> 1.1028 -<pre class="xml">myruby { display: ruby; } 1.1029 -myrbc { display: ruby-base-container; } 1.1030 -myrb { display: ruby-base; } 1.1031 -myrtc.before { display: ruby-text-container; ruby-position: before} 1.1032 -myrtc.after { display: ruby-text-container; ruby-position: after} 1.1033 -myrt { display: ruby-text; ruby-span: attr(rbspan); } 1.1034 -... 1.1035 -<myruby> 1.1036 - <myrbc> 1.1037 - <myrb>10</myrb> 1.1038 - <myrb>31</myrb> 1.1039 - <myrb>2002</myrb> 1.1040 - </myrbc> 1.1041 - <myrtc class="before"> 1.1042 - <myrt>Month</myrt> 1.1043 - <myrt>Day</myrt> 1.1044 - <myrt>Year</myrt> 1.1045 - </myrtc> 1.1046 - <myrtc class="after"> 1.1047 - <myrt rbspan="3">Expiration Date</myrt> 1.1048 - </myrtc> 1.1049 -</myruby></pre> 1.1050 - 1.1051 -<hr /> 1.1052 - 1.1053 -<h2><a id="properties">5. Properties index</a></h2> 1.1054 - 1.1055 -<p id="properties0">In addition to the specified values, all properties take the 1.1056 -'inherit' and 'initial' values.</p> 1.1057 - 1.1058 -<table class="proptable" border='1'> 1.1059 - <thead> 1.1060 - <tr align='center'> 1.1061 - <th>Name</th> 1.1062 - <th>Values</th> 1.1063 - <th>Initial</th> 1.1064 - <th>Applies to </th> 1.1065 - <th>Inh.</th> 1.1066 - <th>Percentages </th> 1.1067 - <th>Media groups<br /> 1.1068 - </th> 1.1069 - </tr> 1.1070 - </thead> 1.1071 - <tbody> 1.1072 - <tr> 1.1073 - <td><a href="#rubyalign">'ruby-align'</a></td> 1.1074 - <td>auto | start | left | center | end | right | distribute-letter | 1.1075 - distribute-space | line-edge</td> 1.1076 - <td>auto</td> 1.1077 - <td> all elements and generated content</td> 1.1078 - <td>yes</td> 1.1079 - <td>N/A </td> 1.1080 - <td>visual</td> 1.1081 - </tr> 1.1082 - <tr> 1.1083 - <td><a href="#rubyover">'ruby-overhang'</a></td> 1.1084 - <td>auto | start | end | none</td> 1.1085 - <td>none</td> 1.1086 - <td>the parent of elements with display: ruby-text</td> 1.1087 - <td>yes</td> 1.1088 - <td> N/A</td> 1.1089 - <td>visual</td> 1.1090 - </tr> 1.1091 - <tr> 1.1092 - <td><a href="#rubypos">'ruby-position'</a></td> 1.1093 - <td>before | after | right | inline</td> 1.1094 - <td>see individual properties</td> 1.1095 - <td>the parent of elements with display: ruby-text</td> 1.1096 - <td>yes</td> 1.1097 - <td> N/A</td> 1.1098 - <td>visual</td> 1.1099 - </tr> 1.1100 - <tr> 1.1101 - <td><a href="#rubyspan">'ruby-span'</a></td> 1.1102 - <td>attr(x) | none</td> 1.1103 - <td>none</td> 1.1104 - <td>elements with display: ruby-text</td> 1.1105 - <td>no</td> 1.1106 - <td>N/A</td> 1.1107 - <td>visual</td> 1.1108 - </tr> 1.1109 - </tbody> 1.1110 -</table> 1.1111 - 1.1112 -<p class="issue"><span class="issuehead">Issue: </span> The i18n WG has requested the addition of a sample user agent default style sheet, as promised by Ruby Annotation section 3.4. See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20Default+stylesheet&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.1113 -<h2><a id="profiles">6. Profiles</a></h2> 1.1114 - 1.1115 -<p>There are two modules defined by this module:</p> 1.1116 - 1.1117 -<p>CSS3 Simple Ruby model</p> 1.1118 - 1.1119 -<p>CSS3 Complex Ruby model.</p> 1.1120 - 1.1121 -<p>They both contain all the properties specified by this CSS chapter, i.e. <a 1.1122 -href="#rubyalign">'ruby-align'</a>, <a href="#rubyover">'ruby-overhang'</a>, <a href="#rubypos">'ruby-position'</a> 1.1123 -and <a href="#rubyspan">'ruby-span'</a>. They differ by the required 1.1124 -'display' property values. The Simple Ruby model requires the values: 'ruby', 1.1125 -'ruby-base' and 'ruby-text'. The Complex Ruby model requires in addition the 1.1126 -values: 'ruby-base-container' and 'ruby-text-container'.</p> 1.1127 - 1.1128 -<h2><a id="glossary">Glossary</a></h2> 1.1129 -<dl> 1.1130 - <dt><a id="g-bopomofo"><strong><span 1.1131 - lang="zh">Bopomofo</span></strong></a></dt> 1.1132 - <dd>37 characters and 4 tone markings used as phonetics in Chinese, 1.1133 - especially standard Mandarin.</dd> 1.1134 - <dt><a id="g-hanja"><strong><span 1.1135 - lang="ko">Hanja</span></strong></a></dt> 1.1136 - <dd>Subset of the Korean writing system that utilizes ideographic 1.1137 - characters borrowed or adapted from the Chinese writing system. Also see 1.1138 - <a href="#g-kanji"><span lang="ja">Kanji</span></a>.</dd> 1.1139 - <dt><a id="g-hiragana"><strong><span 1.1140 - lang="ja">Hiragana</span></strong></a></dt> 1.1141 - <dd>Japanese syllabic script, or character of that script. Rounded and 1.1142 - cursive in appearance. Subset of the Japanese writing system, used together 1.1143 - with kanji and katakana. In recent times, mostly used to write Japanese 1.1144 - words when kanji are not available or appropriate, and word endings and 1.1145 - particles. Also see <a 1.1146 - href="#g-katakana"><span lang="ja">Katakana</span></a>.</dd> 1.1147 - <dt><a id="g-ideogram"><strong>Ideograph</strong></a></dt> 1.1148 - <dd>A character that is used to represent an idea, word, or word component, 1.1149 - in contrast to a character from an alphabetic or syllabic script. The most 1.1150 - well-known ideographic script is used (with some variation) in East Asia 1.1151 - (China, Japan, Korea,...).</dd> 1.1152 - <dt><a id="g-kana"><strong><span lang="ja">Kana</span></strong></a></dt> 1.1153 - <dd>Collective term for hiragana and katakana.</dd> 1.1154 - <dt><a id="g-kanji"><strong>Kanji</strong></a></dt> 1.1155 - <dd>Japanese term for ideographs; ideographs used in Japanese. Subset of the 1.1156 - Japanese writing system, used together with hiragana and katakana. Also see <a 1.1157 - href="#g-hanja"><span lang="ko">Hanja</span></a>.</dd> 1.1158 - <dt><a id="g-katakana"><strong><span 1.1159 - lang="ja">Katakana</span></strong></a></dt> 1.1160 - <dd>Japanese syllabic script, or character of that script. Angular in 1.1161 - appearance. Subset of the Japanese writing system, used together with 1.1162 - kanji and hiragana. In recent times, mainly used to write foreign words. Also see <a 1.1163 - href="#g-hiragana"><span lang="ja">Hiragana</span></a>.</dd> 1.1164 - <dt><a id="g-monoruby" name="g-monoruby"><strong>Mono-ruby</strong></a></dt> 1.1165 - <dd>In Japanese typography: Ruby associated with a single character of 1.1166 - the base text.</dd> 1.1167 - <dt><a id="g-ruby"><strong>Ruby</strong></a></dt> 1.1168 - <dd>A run of text that appears in the vicinity of another run of text and 1.1169 - serves as an annotation or a pronunciation guide for that text.</dd> 1.1170 -</dl> 1.1171 -<hr /> 1.1172 - 1.1173 -<h2><a id="ack">Acknowledgements</a></h2> 1.1174 - 1.1175 -<p>This specification would not have been possible without the help from:</p> 1.1176 - 1.1177 -<p>Stephen Deach, Martin Dürst, Hideki Hiura(<span lang="ja">樋浦 秀樹</span>), Masayasu Ishikawa(<span lang="ja">石川 1.1178 -雅康</span>), Chris 1.1179 -Pratley, Takao Suzuki(<span lang="ja">鈴木 孝雄</span>), Frank Yung-Fong Tang, Chris Thrasher, Masafumi Yabe<span lang="ja">家辺 1.1180 -勝文</span>), Steve Zilles.</p> 1.1181 - 1.1182 -<hr /> 1.1183 - 1.1184 -<h2><a id="references">References</a></h2> 1.1185 -<dl> 1.1186 - <dt>[<a id="css">CSS2</a>] <span class="issue"><span class="issuehead">Issue: </span> Change this to CSS 2.1</span></dt> 1.1187 - <dd><em>Cascading Stylesheets, level 2 (CSS2) Specification, W3C 1.1188 - Recommendation</em></dd> 1.1189 - <dd>Bert Bos, Håkon Wium Lie, Chris Lilley and Ian Jacobs, 12 May 1998<br /> 1.1190 - Available at: 1.1191 - <a href="http://www.w3.org/TR/1998/REC-CSS2-19980512">http://www.w3.org/TR/1998/REC-CSS2-19980512</a></dd> 1.1192 - 1.1193 - 1.1194 -<dt>[<a id="jis4051">JIS4051</a>]<span class="issue"><span class="issuehead"> Issue: </span> Change this to the 2004 version of the spec.</span></dt> 1.1195 - <dd><em>Line composition rules for Japanese documents </em>(<span lang="ja">日本語文書の行組版方法</span>)</dd> 1.1196 - <dd>JIS X 4051-1995, Japanese Standards Association, 1995 (in 1.1197 - Japanese)</dd> 1.1198 - 1.1199 - <dt>[<a id="jis4052">JIS4052</a>] </dt> 1.1200 - <dd><em>"<cite>Exchange format for Japanese documents with composition markup</cite>"</em> 1.1201 - (<span lang="ja">日本語文書の組版指定交換形式</span>) </dd> 1.1202 - <dd>JIS X 4052:2000, Japanese Standards Association, 2000 (in Japanese)</dd> 1.1203 - 1.1204 - <dt>[<a id="jlreq">JLREQ</a>]</dt> 1.1205 - <dd><em>"<cite>Requirements for Japanese Text Layout, W3C WG Note</cite>"</em> 1.1206 - (<span lang="ja">日本語組版処理の要件（日本語版）</span>)</dd> 1.1207 - <dd>Yasuhiro Anan (阿南 康宏), Hiroyuki Chiba (千葉 弘幸), Junsaburo Edamoto (枝本 順三郎), Richard Ishida, Keiichiro Ishino (石野 恵一郎), Tatsuo Kobayashi (小林 龍生), Toshi Kobayashi (小林 敏), Kenzou Onozawa (小野澤 賢三), Felix Sasaki, 4 June 2009,<br /> 1.1208 - Available at: <a href="http://www.w3.org/TR/jlreq/">http://www.w3.org/TR/jlreq/</a>, and <a href="http://www.w3.org/TR/2009/NOTE-jlreq-20090604/ja/">in Japanese</a></dd> 1.1209 - 1.1210 - <dt>[<a id="rfc2119">RFC 2119</a>]</dt> 1.1211 - <dd> Scott Bradner, <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words 1.1212 - for use in RFCs to Indicate Requirement Levels</cite></a>, IETF RFC 2119.<br /> 1.1213 - (See 1.1214 - <a href="http://www.ietf.org/rfc/rfc2119.txt"> 1.1215 - http://www.ietf.org/rfc/rfc2119.txt</a>.)</dd> 1.1216 - <dt>[<a id="ruby">RUBY</a>]</dt> 1.1217 - <dd><em>Ruby Annotation, W3C Recommendation</em></dd> 1.1218 - <dd>Marcin Sawicki, Michel Suignard, Masayasu Ishikawa, Martin Dürst and 1.1219 - Tex Texin, 31 May 2001,<br /> 1.1220 - Available at: <a 1.1221 - href="http://www.w3.org/TR/2001/REC-ruby-20010531/">http://www.w3.org/TR/2001/REC-ruby-20010531</a></dd> 1.1222 - 1.1223 -<dt id="UNICODE">[UNICODE]</dt> 1.1224 - 1.1225 -<dd>The Unicode Consortium. Book version: <cite>The Unicode Standard: Version 3.0.</cite> 1.1226 -Addison Wesley Longman. 2000. ISBN 0-201-61633-5. Online version: <cite>The Unicode 1.1227 -Standard: Version 3.2.0,</cite> URL:<br /> 1.1228 -<a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_2_0">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_2_0</a> 1.1229 -<!----> 1.1230 - 1.1231 -<br /> 1.1232 -For more information, consult the Unicode Consortium's home page at 1.1233 -<a href="http://www.unicode.org/">http://www.unicode.org/</a></dd> 1.1234 - 1.1235 -<dt id="UAX11">[UAX#11]</dt> 1.1236 - 1.1237 -<dd>Asmus Freytag. <cite>East Asian Width.</cite> 15 March 2002. Unicode 1.1238 -Standard Annex #11. URL:<br /> 1.1239 -<a href="http://www.unicode.org/unicode/reports/tr11/tr11-10.html">http://www.unicode.org/unicode/reports/tr11/tr11-10</a></dd> 1.1240 -<!----> 1.1241 - 1.1242 - 1.1243 - 1.1244 -<dt> 1.1245 -[<a id="xhtml-mod">XHTMLMOD</a>]</dt> 1.1246 - 1.1247 -<dd><em>Modularization of XHTML, W3C Recommendation</em></dd> 1.1248 - 1.1249 -<dd>Murray Altheim, Shane McCarron, et al., 10 April 2001<br /> 1.1250 -Available at: 1.1251 -<a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/"> 1.1252 -http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/</a></dd></dl> 1.1253 - 1.1254 -</body> 1.1255 -</html> 1.1256 -<!-- Keep this comment at the end of the file 1.1257 -Local variables: 1.1258 -mode: sgml 1.1259 -sgml-declaration:"~/SGML/HTML4.dcl" 1.1260 -sgml-default-doctype-name:"html" 1.1261 -sgml-minimize-attributes:t 1.1262 -sgml-nofill-elements:("pre" "style" "br") 1.1263 -sgml-validate-command: "SP_BCTF=utf-8 nsgmls -s %s %s" 1.1264 -End: 1.1265 --->
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 2.2 +++ b/css-ruby/Overview.src.html Mon Jun 17 21:35:27 2013 +0900 2.3 @@ -0,0 +1,1176 @@ 2.4 +<!DOCTYPE html> 2.5 +<html lang="en"> 2.6 +<head> 2.7 + <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 2.8 + <title>CSS Ruby Module Level 1</title> 2.9 + <link rel=contents href="#contents"> 2.10 + <link rel=index href="#index"> 2.11 + <link rel="stylesheet" type="text/css" href="../default.css"> 2.12 + <link href="../csslogo.ico" rel="shortcut icon" type="image/x-icon"> 2.13 + <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].css"> 2.14 +</head> 2.15 + 2.16 +<body class="h-entry"> 2.17 + 2.18 +<div class="head"> 2.19 +<!--logo--> 2.20 + 2.21 +<h1 class="p-name">CSS Ruby Module Level 1</h1> 2.22 + 2.23 +<h2 class="no-num no-toc">[LONGSTATUS] <time class="dt-updated" datetime="[CDATE]">[DATE]</time> <!-- for HTML4 doctype: <span class="value-title" title="[CDATE]">[DATE]</span></span> --> </h2> 2.24 +<dl> 2.25 + <dt>This version: 2.26 + <dd><a class="u-url" href="[VERSION]">[VERSION]</a> 2.27 + 2.28 + <dt>Latest version: 2.29 + <dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/css3-ruby/</a> 2.30 + 2.31 + <dt>Editor's draft: 2.32 + <dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a> 2.33 + (<a href="https://dvcs.w3.org/hg/csswg/log/tip/[SHORTNAME]/Overview.src.html">change log</a>) 2.34 + 2.35 + <dt>Previous version: 2.36 + <dd><a href="http://www.w3.org/TR/2011/WD-css3-ruby-20110630/"> 2.37 + http://www.w3.org/TR/2011/WD-css3-ruby-20110630/</a> 2.38 + 2.39 + <dt>Issue Tracking:</dt> 2.40 + <dd><a rel="issues" href="http://www.w3.org/Style/CSS/Tracker/products/FIXME">http://www.w3.org/Style/CSS/Tracker/products/FIXME</a> 2.41 + 2.42 + <dt>Feedback:</dt> 2.43 + <dd><a href="mailto:www-style@w3.org?subject=%5BSHORTNAME%5D%20feedback" 2.44 + >www-style@w3.org</a> 2.45 + with subject line “<kbd>[[SHORTNAME]] 2.46 + <var>… message topic …</var></kbd>” 2.47 + (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/" 2.48 + >archives</a>) 2.49 + 2.50 + <dt>Editors: 2.51 + <dd class="p-author h-card vcard"> 2.52 + <a class="p-name fn u-url url" rel="author" 2.53 + href="http://fantasai.inkedblade.net/contact">Elika J. Etemad</a>, 2.54 + <a class="p-org org h-org" href="http://www.mozilla.org/">Mozilla</a> 2.55 + <dd class="p-author h-card vcard"> 2.56 + <a class="p-name fn u-url url" rel="author" 2.57 + href="mailto:koji.a.ishii@mail.rakuten.com">Koji Ishii</a>, 2.58 + <span class="p-org org">Rakuten, Inc.</span> 2.59 + <dd class="p-author h-card vcard"> 2.60 + <a class="p-name fn u-url url" rel="author" 2.61 + href="mailto:ishida@w3.org">Richard Ishida</a>, 2.62 + <span class="p-org org">W3C</span> 2.63 + 2.64 + <dt>Former editors: 2.65 + <dd>Michel Suignard, Microsoft 2.66 + <dd>Marcin Sawicki, Microsoft 2.67 +</dl> 2.68 + 2.69 +<!--copyright--> 2.70 + 2.71 +<hr title="Separator for header"> 2.72 +</div> 2.73 + 2.74 +<h2 class="no-num no-toc" id="abstract">Abstract</h2> 2.75 + 2.76 + <p> 2.77 + <span class="p-summary"> 2.78 + “Ruby” are short runs of text alongside the base text, 2.79 + typically used in East Asian documents to indicate pronunciation 2.80 + or to provide a short annotation. 2.81 + This module describes the rendering model and formatting controls 2.82 + related to displaying ruby annotations in CSS. 2.83 + </span> 2.84 + 2.85 + <a href="http://www.w3.org/TR/CSS/">CSS</a> is a language for describing 2.86 + the rendering of structured documents (such as HTML and XML) on screen, on 2.87 + paper, in speech, etc. 2.88 + 2.89 +<h2 class="no-num no-toc" id="status">Status of this document</h2> 2.90 + 2.91 +<!--status--> 2.92 + 2.93 +<p>The following features are at risk: … 2.94 + 2.95 +<h2 class="no-num no-toc" id="contents"> 2.96 +Table of Contents</h2> 2.97 + 2.98 +<!--toc--> 2.99 + 2.100 +<h2 id="intro"> 2.101 +Introduction</h2> 2.102 + 2.103 + <p><em>This section is not normative.</em> 2.104 + 2.105 +<h3 id="placement"> 2.106 +Module interactions</h3> 2.107 + 2.108 + <p>This module extends the inline box model of CSS Level 2 [[!CSS21]] 2.109 + to support ruby. 2.110 + 2.111 + <p>None of the properties in this module apply to the <code>::first-line</code> or 2.112 + <code>::first-letter</code> pseudo-elements. 2.113 + 2.114 +<h3 id="values"> 2.115 +Values</h3> 2.116 + 2.117 + <p>This specification follows the 2.118 + <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property 2.119 + definition conventions</a> from [[!CSS21]]. Value types not defined in 2.120 + this specification are defined in CSS Level 2 Revision 1 [[!CSS21]]. 2.121 + Other CSS modules may expand the definitions of these value types: for 2.122 + example [[CSS3VAL]], when combined with this module, expands the 2.123 + definition of the <var><length></var> value type as used in this specification.</p> 2.124 + 2.125 + <p>In addition to the property-specific values listed in their definitions, 2.126 + all properties defined in this specification also accept the 2.127 + <a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a> 2.128 + keyword as their property value. For readability it has not been repeated 2.129 + explicitly. 2.130 + 2.131 +<h3 id="conventions"> 2.132 +Document conventions</h3> 2.133 + 2.134 +<p>There are a number of illustrations in this document for which the following 2.135 +legend is used:</p> 2.136 + 2.137 +<p><img alt="Symbolic wide-cell glyph representation" class="example" 2.138 +width="39" height="39" src="images/fullwidth.gif" /> - wide-cell glyph (e.g. Han) 2.139 +which is the <i>n</i>-th character in the text run, they may also appear as 2.140 +half size boxes when used as annotations.<br /> 2.141 +<img alt="Symbolic narrow-cell glyph representation" class="example" 2.142 +width="19" height="39" src="images/halfwidth.gif" /> - narrow-cell glyph (e.g. Roman) 2.143 +which is the <i>n</i>-th glyph in the text run.<br /> 2.144 +</p> 2.145 + 2.146 +<p>Many typographical properties in East Asian typography depend on the fact 2.147 +that a character is typically rendered as either a wide or narrow character. All 2.148 +characters described by the Unicode Standard [[UNICODE]] can be categorized by a 2.149 +width property. This is covered by the Unicode Standard Annex 2.150 +[[UAX11]]</a>. </p> 2.151 + 2.152 +<p>The orientation which the above symbols assume in the diagrams corresponds 2.153 +to the orientation that the glyphs they represent are intended to assume when 2.154 +rendered by the user agent. Spacing between these characters in the diagrams is 2.155 +usually symbolic, unless intentionally changed to make a point.</p> 2.156 + 2.157 +<h3 id="ruby-def"> 2.158 +What is ruby?</h3> 2.159 + 2.160 +<p>"Ruby" is the commonly used name for a run of text that appears in the 2.161 +immediate vicinity of another run of text, referred to as the "base", and 2.162 +serves as an annotation or a pronunciation guide associated with that run of 2.163 +text. Ruby, as used in Japanese, is described in JIS X-4051 [[JIS4051]] (in Japanese) and in Requirements for Japanese Text Layout [[JLREQ]] (in English and Japanese)]. The ruby structure and the XHTML markup to represent it 2.164 +is described in the Ruby Annotation [[RUBY]] specification. This 2.165 +section describes the CSS properties relevant to ruby. The following figures 2.166 +show two examples of Ruby.</p> 2.167 + 2.168 +<div class="figure"> 2.169 +<p> 2.170 +<img alt="Example of ruby applied on top of a Japanese expression" 2.171 +class="example" src="images/licence.png" /></p> 2.172 + 2.173 +<p><b>Figure 2.2.1</b>: Example of ruby used in Japanese (simple case)</p> 2.174 +</div> 2.175 + 2.176 +<div class="figure"> 2.177 +<p> 2.178 +<img 2.179 +alt="Example showing complex ruby with annotation text before and after 2.180 +the base characters" 2.181 +class="example" src="images/ruby-univ.gif" width="277" height="108" /></p> 2.182 + 2.183 +<p><strong>Figure 2.2.2</strong>: Complex ruby with annotation text before and after 2.184 +the base characters</p> 2.185 +</div> 2.186 + 2.187 +<p>In the first example, a single annotation is used to annotate the base 2.188 +sequence. In Japanese typography, this simple case is sometimes called "<span lang="ja">taigo</span> ruby" or group-ruby (per-word ruby).</p> 2.189 + 2.190 +<p>In the second example, multiple annotations are attached to a base 2.191 +sequence, the hiragana characters on top refer to the pronunciation of each of the 2.192 +base Kanji characters (annotated in a <a href="#g-monoruby">mono-ruby</a> fashion), while the words 'Keio' 2.193 +and 'University' on the bottom are 2.194 +annotations describing the English translation of respectively the first four 2.195 +and the last two Kanji characters 2.196 +of the base. To allow correct association between the hiragana characters and 2.197 +their corresponding Kanji base characters, the spacing between these Kanji 2.198 +characters may be adjusted (this happens around the fourth Kanji character in the 2.199 +figure 2.2.2 above).</p> 2.200 + 2.201 +<p class="Note"><span class="note-label">Note:</span> To avoid variable spacing between the Kanji 2.202 +characters in the example above the hiragana annotations can also be created as 2.203 +a simple annotation ruby.</p> 2.204 + 2.205 +<p>The two examples correspond respectively to two types of ruby: simple ruby using simple ruby markup and complex ruby using complex ruby 2.206 +markup.</p> 2.207 + 2.208 +<h2 id="ruby-model"> 2.209 +Ruby Formatting Model</h2> 2.210 + 2.211 +<h3 id="display"> 2.212 +Ruby specific 'display' property values</h3> 2.213 + 2.214 +<p>The CSS ruby model is based on the W3C Ruby Annotation Recommendation [[RUBY]]. 2.215 +The Recommendation specifies the ruby structure in a way to closely parallel 2.216 +the visual layout of the ruby element. In this model, a ruby consists of one 2.217 +or more base elements associated with one or more annotation elements.</p> 2.218 + 2.219 +<p>The CSS model does not require that the document language include elements 2.220 +that correspond to each of these components. For document languages (such as 2.221 +XML applications) that do not have pre-defined ruby elements, authors must map 2.222 +document language elements to ruby elements; this is done with the 'display' 2.223 +property. The following 'display' values assign ruby semantics to an arbitrary 2.224 +element:</p> 2.225 +<dl> 2.226 + <dt><strong>ruby</strong> (in XHTML: ruby)</dt> 2.227 + <dd>Specifies that an element defines a ruby structure.</dd> 2.228 + <dt><strong>ruby-base</strong> (in XHTML: rb)</dt> 2.229 + <dd>Specifies that an element defines a ruby base.</dd> 2.230 + <dt><strong>ruby-text</strong> (in XHTML: rt)</dt> 2.231 + <dd>Specifies that an element defines a ruby text.</dd> 2.232 + <dt><strong>ruby-base-container</strong> (in XHTML: rbc)</dt> 2.233 + <dd>Specifies that an element contains one or more ruby base.</dd> 2.234 + <dt><strong>ruby-text-container</strong> (in XHTML: rtc)</dt> 2.235 + <dd>Specifies that an element contains one or more ruby text.</dd> 2.236 +</dl> 2.237 + 2.238 +<p class="issue"><span class="issuehead">Issue: </span> I18n WG proposes that there should be a display value rp also, to allow XML-based formats to associate rp behaviour with elements. See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20display:+rp+value&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">thread</a>.</p> 2.239 + 2.240 +<p>The <a 2.241 +href="http://www.w3.org/TR/ruby/#ruby"><samp>rbspan</samp></a> attribute should 2.242 +also be used by XML applications to allow annotation spanning; but in addition, the 2.243 +'<a href="#ruby-span">ruby-span</a>' property must be used by those applications to indicate to the user agent the number of 2.244 +ruby base elements to be spanned.</p> 2.245 + 2.246 +<h3 id="box-model"> 2.247 +Ruby box model</h3> 2.248 + 2.249 +<p class="issue"><span class="issuehead">Issue: </span> The spec needs to address anonymous box generation rules (and to make them compatible with HTML5 ruby markup).</p> 2.250 +<p>In the following description, the elements specified by Ruby 2.251 +Annotation [[RUBY]] are used to describe the box model. As mentioned 2.252 +earlier, a user agent can obtain the same results by using the Ruby specific 'display' 2.253 +property values. </p> 2.254 + 2.255 +<p>For a user agent that supports the ruby markup, the ruby structure consists of three or more 2.256 +boxes. The outermost container is the <a 2.257 +href="http://www.w3.org/TR/ruby/#ruby"><samp>ruby</samp></a> element itself. 2.258 +In the simple case, it is a container for two non-overlapping boxes: the ruby 2.259 +text box (<a href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element) 2.260 +and the ruby base box (<a 2.261 +href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element). The 2.262 +positioning of these two boxes relative to each other is controlled by the <a 2.263 +href="#rubypos">'ruby-position'</a> property.</p> 2.264 + 2.265 +<div class="figure"> 2.266 +<img class="example" width="223" height="93" 2.267 +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" 2.268 +src="images/r-box-t.gif" /> 2.269 + 2.270 +<p><b>Figure 3.2.1</b>: Ruby box model (simple case)</p> 2.271 +</div> 2.272 + 2.273 +<p>In the case of complex ruby, the ruby element is a container for two or 2.274 +three non-overlapping boxes: one ruby base collection (<a 2.275 +href="http://www.w3.org/TR/ruby/#rbc"><samp>rbc</samp></a> element), and one 2.276 +or two ruby text collections (<a 2.277 +href="http://www.w3.org/TR/ruby/#rtc"><samp>rtc</samp></a> element). The 2.278 +<samp>rbc</samp> element is itself a container for one or several ruby base 2.279 +box (<samp>rb</samp> element), while each <samp>rtc</samp> element is a 2.280 +container for one or several ruby text box (rt element). The position of the 2.281 +<samp>rtc</samp> element in relation to the related <samp>rbc</samp> element 2.282 +is controlled by the <a href="#rubypos">'ruby-position'</a> property. The two 2.283 +following figures show examples of these complex ruby.</p> 2.284 + 2.285 +<div class="figure"> 2.286 +<img src="images/r-box-g.gif" 2.287 +alt="Diagram of a group ruby with a full ruby text above and partial ruby text below" width="408" height="170" /> 2.288 + 2.289 +<p><b>Figure 3.2.2</b>: Ruby box model (complex ruby with an empty rt element 2.290 +after)</p> 2.291 +</div> 2.292 + 2.293 +<p>In the example above, the ruby text after (below) the ruby bases contains two <samp>rt</samp> elements with the first one 2.294 +being empty, the empty <samp>rt</samp> element corresponds to the first part 2.295 +of the ruby base collection (the first part is identified by the first <samp>rb</samp> element 2.296 +within the <samp> rbc</samp> element).</p> 2.297 + 2.298 +<div class="figure"> 2.299 +<img src="images/r-box-h.gif" 2.300 +alt="Diagram of a group ruby with a spanning ruby text above and partial ruby text below" width="400" height="173" /> 2.301 + 2.302 +<p><b>Figure 3.2.3</b>: Ruby box model (complex ruby with a spanning ruby text 2.303 +element)</p> 2.304 +</div> 2.305 + 2.306 +<p>In the example above, the ruby text before (above) the ruby bases spans the whole ruby base collection. The 2.307 +ruby text after (below) the ruby bases still contain two <samp>rt</samp> elements, one of 2.308 +which is empty. The spanning behavior of <samp>rt</samp> text elements is 2.309 +controlled by the <a 2.310 +href="http://www.w3.org/TR/ruby/#ruby"><samp>rbspan</samp></a> attribute in a 2.311 +way similar to the <samp>colspan</samp> attribute used for table column.</p> 2.312 + 2.313 +<p class="issue"><span class="issuehead">Issue: </span> The examples above contain the term 'group ruby', which is not used elsewhere in this specification. It appears to be used in a way that is different to the use of the term in JLREQ. I propose to replace it with just 'ruby'.</p> 2.314 +<p class="note"><span class="note-label">Note:</span> The visual description of the ruby elements does not refer 2.315 +necessarily to the logical orders of the elements</p> 2.316 + 2.317 +<p>The width of the ruby box is by default determined by its widest child 2.318 +element, whose width in turn is determined by its content. The width of all direct 2.319 +children of the <samp>ruby</samp> element is the width of the widest children. In this respect, the ruby 2.320 +box is much like a two or three row <samp>table</samp> element, with the 2.321 +following exceptions:</p> 2.322 +<ul> 2.323 + <li>the ruby box is an inline element, like an image, even though it itself, 2.324 + like a table, is a container of other boxes</li> 2.325 + <li>the equivalent of the cells: the <samp>rb</samp> element and the 2.326 + <samp>rt</samp> text element can only contain inline-level elements.</li> 2.327 + <li>the content of each 'cell' is always measured at its maximum width</li> 2.328 + <li>unlike a table, a ruby element doesn't have to fit in a line, the ruby 2.329 + box may be split into several boxes at line boundary, depending of the 2.330 + spanning of the ruby texts. This is however only possible for the complex 2.331 + ruby and can only happen at the boundary of non spanning elements.</li> 2.332 + <li>both the ruby text and the ruby base boxes may overlap with adjacent 2.333 + text (outside of the ruby element) if an appropriate <a 2.334 + href="#rubyover">'ruby-overhang'</a> parameter is set via CSS. Note 2.335 + however that the actual content of the ruby base cannot overlap with that 2.336 + adjacent text. The distribution of the content of the ruby base within the 2.337 + ruby base box is controlled by the <a href="#rubyalign">'ruby-align'</a> 2.338 + property.</li> 2.339 +</ul> 2.340 + 2.341 +<p>If the ruby text is not allowed to overhang, then the ruby behaves like a 2.342 +traditional box, i.e. only its contents are rendered within its boundaries and 2.343 +adjacent elements do not cross the box boundary:</p> 2.344 + 2.345 +<div class="figure"> 2.346 +<p><img class="example" width="220" height="91" 2.347 +alt="Diagram showing the ruby boxes interacting with adjacent text" 2.348 +src="images/ro-n.gif" /></p> 2.349 + 2.350 +<p><b>Figure 3.2.4</b>: Simple ruby whose text is not allowed to overhang 2.351 +adjacent text</p> 2.352 +</div> 2.353 + 2.354 +<p>However, if ruby text is allowed to overhang adjacent elements and it 2.355 +happens to be wider than its base, then the adjacent content is partially 2.356 +rendered within the area of the ruby base box, while the ruby text may be 2.357 +partially overlapping with the upper blank parts of the adjacent content:</p> 2.358 + 2.359 +<div class="figure"> 2.360 +<p><img class="example" width="177" height="91" 2.361 +alt="Diagram showing the ruby boxes interacting with adjacent text" 2.362 +src="images/ro-a.gif" /></p> 2.363 + 2.364 +<p><b>Figure 3.2.5</b>: Simple ruby whose text is allowed to overhang adjacent 2.365 +text</p> 2.366 +</div> 2.367 + 2.368 +<p>The ruby text related to a ruby base can never overhang another ruby 2.369 +base.</p> 2.370 + 2.371 +<p>The alignment of the contents of the base or the ruby text is not affected 2.372 +by the overhanging behavior. The alignment is achieved the same way regardless 2.373 +of the overhang behavior setting and it is computed before the space available 2.374 +for overlap is determined. It is controlled by the <a 2.375 +href="#rubyalign">'ruby-align'</a> property.</p> 2.376 + 2.377 +<p>The exact circumstances in which the ruby text will overhang other 2.378 +elements, and to what degree it will do so, will be controlled by the <a 2.379 +href="#rubyover">'ruby-overhang'</a> property.</p> 2.380 + 2.381 +<p>This entire logic applies the same way in vertical ideographic layout, only 2.382 +the dimension in which it works in such a layout is vertical, instead of 2.383 +horizontal.</p> 2.384 + 2.385 +<p class="note"><span class="note-label">Note:</span> Because the purpose of the XHTML <samp>rp</samp> element 2.386 +[[RUBY]] is to allow pre-existing user agents 2.387 +to parenthesize ruby text content, an XHTML user agent should use a styling rule 2.388 +for these elements that avoids rendering them such as <samp>rp {display: 2.389 +none}</samp>.</p> 2.390 + 2.391 +<h3 id="ruby-line-height"> 2.392 +Ruby box and line stacking</h3> 2.393 + 2.394 +<p>The interaction of the ruby box and line stacking is controlled by the 2.395 +'line-stacking-ruby' property described in the CSS3 Line Module. That property 2.396 +takes two values: 'include-ruby' and 'exclude-ruby. Depending on the property 2.397 +value, the ruby box is considered or excluded for line stacking. Even if the 2.398 +ruby box is considered for line stacking, some values of the 2.399 +'line-stacking-strategy' property (also described in the CSS3 Line module) can 2.400 +still create occurrences where a the ruby box will eventually be ignored (e.g. 2.401 +case where the 'line-stacking-strategy' value is 'block-line-height').</p> 2.402 + 2.403 +<p>In the following figure, each line box is shown with leading space 2.404 +distributed before and after the two text segments ('Previous line' and 'Ruby 2.405 +base'); the dotted lines show the line box for each line. The 2.406 +'line-stacking-ruby' property is set to 'exclude-ruby'. The achieved effect is 2.407 +that the ruby box does not affect the line to line spacing. It is however the 2.408 +responsibility of the style author to avoid 'bleeding' effects between the ruby 2.409 +text and the surrounding text of images.</p> 2.410 + 2.411 +<div class="figure"> 2.412 +<p> 2.413 +<img class="example" 2.414 +alt="Diagram showing the ruby text using 2 half leading" 2.415 +src="images/rlh-a.gif" width="210" height="138" /></p> 2.416 + 2.417 +<p><b>Figure 3.3.1</b>: Excluded Ruby text</p> 2.418 +</div> 2.419 + 2.420 + 2.421 +<p>In the following figure, the line boxes have no extra leading space. The 2.422 +'line-stacking-ruby' property is set to 'include-ruby' and the 2.423 +'line-stacking-strategy' property is set to a value where inline boxes are 2.424 +considered for line stacking. In this case, the line box with 2.425 +the ruby text is affected and has its 'stack-height' increased by the amount 2.426 +necessary to fit the ruby text.</p> 2.427 + 2.428 +<div class="figure"> 2.429 +<p> 2.430 +<img class="example" 2.431 +alt="Diagram showing the ruby text expanding above base text" 2.432 +src="images/rlh-b.gif" width="210" height="111" /></p> 2.433 + 2.434 +<p><b>Figure 3.3.2</b>: Ruby text increasing line height</p> 2.435 +</div> 2.436 +<p>This mechanism allows rendering of evenly spaced lines of text within a 2.437 +block-level element, whether a line contains ruby or not. The authors need 2.438 +only to set for the block-level element a line height value larger than the 2.439 +computed line-height of the largest ruby element within the block.</p> 2.440 + 2.441 +<h3 id="ruby-line-breaking"> 2.442 +Ruby box and line breaking</h3> 2.443 + 2.444 +<p>When a ruby falls at the end of a line where there is not sufficient room for the entire ruby to fit on the line, the complex ruby may be broken at locations where boxes of the ruby container align. Some examples are provided below to provide more clarity.</p> 2.445 + 2.446 +<p> 2.447 +<img class="example" 2.448 +alt="Diagram showing the line breaking opportunity in a complex ruby" 2.449 +src="images/r-break-a.gif" width="408" height="201" /></p> 2.450 + 2.451 +<p><b>Figure 3.4.1</b>: Complex ruby line breaking opportunity</p> 2.452 + 2.453 +<p> 2.454 +<img class="example" 2.455 +alt='Diagram showing the line breaking opportunity in a "Bopomofo" ruby' 2.456 +src="images/r-break-b.gif" width="300" height="90" /></p> 2.457 + 2.458 +<p><b>Figure 3.4.1</b>: "Bopomofo" ruby line breaking opportunity</p> 2.459 +<p class="issue"><span class="issuehead">Issue: </span> Line breaks should only be allowed within ruby if the ruby base text can be broken at that point. E.g. if complex Ruby is used to annotate the two morphemes of "butterfly", the fact that we have added ruby annotations should not cause a line breaking opportunity to be present between "butter" and "fly" </p> 2.460 +<h2 id="ruby-props"> 2.461 +Ruby Properties</h2> 2.462 + 2.463 +<p>All properties, in addition to the noted values, take 'initial' and 2.464 +'inherit'. These values are not repeated in each of the property value 2.465 +enumeration. </p> 2.466 + 2.467 +<h3 id="rubypos"> 2.468 +Ruby positioning: the 'ruby-position' property</h3> 2.469 + 2.470 + <table class="propdef"> 2.471 + <tr> 2.472 + <th>Name: 2.473 + <td><dfn>ruby-position</dfn> 2.474 + <tr> 2.475 + <th>Value: 2.476 + <td>before | after | inter-character | inline 2.477 + <tr> 2.478 + <th>Initial: 2.479 + <td>before 2.480 + <tr> 2.481 + <th>Applies to: 2.482 + <td>the parent of elements with display: ruby-text. 2.483 + <tr> 2.484 + <th>Inherited: 2.485 + <td>yes 2.486 + <tr> 2.487 + <th>Percentages: 2.488 + <td>N/A 2.489 + <tr> 2.490 + <th>Media: 2.491 + <td>visual 2.492 + <tr> 2.493 + <th>Computed value: 2.494 + <td>specified value (except for initial and inherit) 2.495 + <tr> 2.496 + <th>Animatable: 2.497 + <td>no 2.498 + <tr> 2.499 + <th>Canonical order: 2.500 + <td><abbr title="follows order of property value definition">per grammar</abbr> 2.501 + </table> 2.502 +<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.503 +<p>This property is used by the parent of elements with display: ruby-text to 2.504 + control the position of the ruby text with respect to its base. Such parents 2.505 + are typically either the <samp>ruby</samp> element itself (simple ruby) or the 2.506 + <samp>rtc</samp> element (complex ruby). This assures that all parts of a <samp>rtc</samp> 2.507 +element will be displayed in the same position. Possible values:</p> 2.508 +<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.509 +<dl> 2.510 + <dt><strong>before</strong></dt> 2.511 + <dd>The ruby text appears before the base. This is the most common setting 2.512 + used in ideographic East Asian writing systems. This is the initial 2.513 + value. 2.514 + 2.515 + <div class="figure"> 2.516 + <p> 2.517 + <img 2.518 + alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing above the base" 2.519 + class="example" src="images/shinkansen-top.gif" width="140" height="33" /></p> 2.520 + <p><b>Figure 4.1.1</b>: Top ruby in horizontal layout applied to 2.521 + Japanese text</p> 2.522 + </div> 2.523 + <p>If the base appears in a vertical-ideographic layout mode, the ruby 2.524 + appears on the right side of the base and is rendered in the same layout 2.525 + mode as the base (i.e. vertical-ideographic).</p> 2.526 + 2.527 + <div class="figure"> 2.528 + <p> 2.529 + <img 2.530 + alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the right of the base" 2.531 + class="example" src="images/shinkansen-right.gif" width="33" height="141" /></p> 2.532 + <p><b>Figure 4.1.2</b>: Top ruby in vertical ideographic layout applied 2.533 + to Japanese text</p> 2.534 + </div> 2.535 +</dd> 2.536 + <dt><strong>after</strong></dt> 2.537 + <dd>The ruby text appears after the base. This is a relatively rare 2.538 + setting used in ideographic East Asian writing systems, most easily 2.539 + found in educational text. 2.540 + 2.541 + <div class="figure"> 2.542 + <p> 2.543 + <img 2.544 + alt="Diagram of ruby glyph layout in horizontal mode with ruby text appearing below the base" 2.545 + class="example" src="images/shinkansen-bottom.gif" width="142" height="36" /></p> 2.546 + <p><b>Figure 4.1.3</b>: Bottom ruby in horizontal layout applied to 2.547 + Japanese text</p> 2.548 + </div> 2.549 + <p>If the base appears in a vertical ideographic mode, the bottom ruby 2.550 + appears on the left side of the base and is rendered in the same layout 2.551 + mode as the base (i.e. vertical).</p> 2.552 + 2.553 + <div class="figure"> 2.554 + <p> 2.555 + <img 2.556 + alt="Diagram of ruby glyph layout in vertical mode with ruby text apearing vertically on the left of the base" 2.557 + class="example" src="images/shinkansen-left.gif" width="37" height="141" /></p> 2.558 + <p><b>Figure 4.1.4</b>: Bottom ruby in vertical ideographic layout applied 2.559 + to Japanese text</p> 2.560 + </div> 2.561 + </dd> 2.562 + <dt><strong>inter-character</strong></dt> 2.563 + <dd> 2.564 + <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.565 + <p>The ruby text appears on the right of the base. Unlike 'before' and 2.566 + 'after', this value is visual and is not relative to the text flow direction.</p> 2.567 + 2.568 + <p>This value is provided for the special case of traditional Chinese as used especially in 2.569 + Taiwan: ruby (made of <a href="#g-bopomofo"><span 2.570 + lang="zh">bopomofo</span></a> glyphs) in that context appears vertically along 2.571 + the right side of the base glyph, whether the layout of the base characters is vertical or horizontal:</p> 2.572 + 2.573 + <div class="figure"> 2.574 + <p><img alt="Example of Taiwanese-style ruby" class="example" 2.575 + width="138" height="42" src="images/bopomofo.gif" /></p> 2.576 + <p><b>Figure 4.1.5</b>: "<span lang="zh">Bopomofo</span>" ruby in 2.577 + traditional Chinese (ruby text shown in blue for clarity) in horizontal 2.578 + layout</p> 2.579 + </div> 2.580 + <p class="note"><span class="note-label">Note:</span> The bopomofo 2.581 + transcription is written in the normal way as part of the ruby text. 2.582 + The user agent is responsible for ensuring the correct relative alignment 2.583 + and positioning of the glyphs, including those corresponding to the 2.584 + 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.585 + <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.586 + <p>It is not defined how a user-agent should handle ruby text that is not bopomofo when the value of ruby-position is set to 'right'.</p> 2.587 + <!-- See Taiwanese requirements doc for EPUB at http://epub-revision.googlecode.com/files/EGLS_TW_eng.ppt --> 2.588 + </dd> 2.589 +<dt><strong>inline</strong></dt> 2.590 +<dd> 2.591 +<p>Ruby text follows the ruby base with no special styling. The value can be used to disable ruby text positioning.</p> 2.592 +<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.593 +<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.594 +</dd> 2.595 +</dl> 2.596 + 2.597 +<p>If two rtc elements are set with the same ruby-position value, (for example 2.598 +both 'before'), the relative position of the two elements is undefined. This 2.599 +setting should not be used.</p> 2.600 + 2.601 +<h3 id="rubyalign"> 2.602 +Ruby alignment: the 'ruby-align' property</h3> 2.603 + 2.604 + <table class="propdef"> 2.605 + <tr> 2.606 + <th>Name: 2.607 + <td><dfn>ruby-align</dfn> 2.608 + <tr> 2.609 + <th>Value: 2.610 + <td>auto | start | left | center | end | right | distribute-letter | 2.611 + distribute-space | line-edge 2.612 + <tr> 2.613 + <th>Initial: 2.614 + <td>auto 2.615 + <tr> 2.616 + <th>Applies to: 2.617 + <td>all elements and generated content 2.618 + <tr> 2.619 + <th>Inherited: 2.620 + <td>yes 2.621 + <tr> 2.622 + <th>Percentages: 2.623 + <td>N/A 2.624 + <tr> 2.625 + <th>Media: 2.626 + <td>visual 2.627 + <tr> 2.628 + <th>Computed value: 2.629 + <td>specified value (except for initial and inherit) 2.630 + </table> 2.631 + 2.632 +<p>This property can be used on any element to control the text alignment of 2.633 +the ruby text and ruby base contents relative to each other. It applies to all 2.634 +the rubys in the element. For simple ruby, the alignment is applied to the 2.635 +ruby child element whose content is shorter: either the <a 2.636 +href="http://www.w3.org/TR/ruby/#rb"><samp>rb</samp></a> element or the <a 2.637 +href="http://www.w3.org/TR/ruby/#rt"><samp>rt</samp></a> element [[RUBY]]. 2.638 +For complex ruby, the alignment is also applied to the 2.639 +ruby child elements whose content is shorter: either the <samp>rb</samp> 2.640 +element and/or one or two <samp>rt</samp> elements for each related ruby text 2.641 +and ruby base element within the <samp>rtc</samp> and <samp>rbc</samp> 2.642 +element.</p> 2.643 + 2.644 +<p>Possible values:</p> 2.645 +<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.646 +<dl> 2.647 + <dt><strong>auto</strong></dt> 2.648 + <dd>The user agent determines how the ruby contents are aligned. This is 2.649 + the initial value. The behavior recommended by [[JLREQ]] is for wide-cell ruby to be aligned in the 'distribute-space' mode: 2.650 +<div class="figure"> 2.651 + <p><img class="example" width="145" height="91" 2.652 + alt="Diagram of glyph layout in auto aligned ruby when ruby text is shorter than base" 2.653 + src="images/ra-ds.gif" /><img class="example" width="145" height="91" 2.654 + alt="Diagram of glyph layout in auto aligned ruby when ruby text is longer than base" 2.655 + src="images/ra-ds-rb.gif" /></p> 2.656 + <p><b>Figure 4.2.1</b>: Wide-cell text in 'auto' ruby alignment is 2.657 + 'distribute-space' justified</p> 2.658 + </div> 2.659 + <p>The recommended behavior for narrow-cell glyph ruby is to be 2.660 + aligned in the 'center' mode.</p> 2.661 + 2.662 + <div class="figure"> 2.663 + <p><img 2.664 + alt="Diagram of glyph layout in auto aligned ruby when halfwidth ruby text is shorter than base" 2.665 + class="example" width="145" height="91" 2.666 + src="images/ra-c-h.gif" /><img 2.667 + alt="Diagram of character layout in auto aligned ruby when ruby text is longer than narrow-width base" 2.668 + class="example" width="145" height="91" 2.669 + src="images/ra-c-rb-h.gif" /></p> 2.670 + <p><b>Figure 4.2.2</b>: Narrow-width ruby text in 'auto' ruby alignment 2.671 + is centered</p> 2.672 + </div> 2.673 + </dd> 2.674 + <dt><strong>left</strong></dt> 2.675 + <dd>The ruby text content is aligned with the start edge of the base. 2.676 + 2.677 + <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.678 + 2.679 + <div class="figure"> 2.680 + <p><img 2.681 + alt="Diagram of glyph layout in left aligned ruby when ruby text is shorter than base" 2.682 + class="example" width="145" height="91" src="images/ra-l.gif" /><img 2.683 + class="example" width="145" height="91" 2.684 + alt="Diagram of glyph layout in left aligned ruby when ruby text is longer than base" 2.685 + src="images/ra-l-rb.gif" /></p> 2.686 + <p><b>Figure 4.2.3</b>: Start ruby alignment</p> 2.687 + </div> 2.688 + </dd> 2.689 + <dt><strong>center</strong></dt> 2.690 + <dd>The ruby text content is centered within the width of the base. If the 2.691 + length of the base is smaller than the length of the ruby text, then the 2.692 + base is centered within the width of the ruby text. 2.693 + 2.694 + <div class="figure"> 2.695 + <p><img class="example" width="145" height="91" 2.696 + alt="Diagram of glyph layout in center aligned ruby when ruby text is shorter than base" 2.697 + src="images/ra-c.gif" /><img class="example" width="145" height="91" 2.698 + alt="Diagram of glyph layout in center aligned ruby when ruby text is longer than base" 2.699 + src="images/ra-c-rb.gif" /></p> 2.700 + <p><b>Figure 4.2.4</b>: Center ruby alignment</p> 2.701 + </div> 2.702 + </dd> 2.703 + <dt><strong>right</strong></dt> 2.704 + <dd>The ruby text content is aligned with the end edge of the base. 2.705 + <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> 2.706 +<div class="figure"> 2.707 + <p><img class="example" width="145" height="91" 2.708 + alt="Diagram of glyph layout in right aligned ruby when ruby text is shorter than base" 2.709 + src="images/ra-r.gif" /><img class="example" width="145" height="91" 2.710 + alt="Diagram of glyph layout in right aligned ruby when ruby text is longer than base" 2.711 + src="images/ra-r-rb.gif" /></p> 2.712 + <p><b>Figure 4.2.5</b>: End ruby alignment</p> 2.713 +</div> 2.714 + </dd> 2.715 + <dt><strong>distribute-letter</strong></dt> 2.716 + <dd>If the width of the ruby text is smaller than that of the base, then 2.717 + the ruby text contents are evenly distributed across the width of the 2.718 + base, with the first and last ruby text glyphs lining up with the 2.719 + corresponding first and last base glyphs. If the width of the ruby text 2.720 + is at least the width of the base, then the letters of the base are 2.721 + evenly distributed across the width of the ruby text. 2.722 + 2.723 + <div class="figure"> 2.724 + <p><img class="example" width="145" height="91" 2.725 + alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is shorter than base" 2.726 + src="images/ra-dl.gif" /><img class="example" width="145" height="91" 2.727 + alt="Diagram of glyph layout in distribute-letter aligned ruby when ruby text is longer than base" 2.728 + src="images/ra-dl-rb.gif" /></p> 2.729 + <p><b>Figure 4.2.6</b>: Distribute-letter ruby alignment</p> 2.730 + </div> 2.731 + </dd> 2.732 + <dt><strong>distribute-space</strong></dt> 2.733 + <dd>If the width of the ruby text is smaller than that of the base, then 2.734 + the ruby text contents are evenly distributed across the width of the 2.735 + base, with a certain amount of white space preceding the first and 2.736 + following the last character in the ruby text. That amount of white 2.737 + space is normally equal to half the amount of inter-character space of 2.738 + the ruby text. If the width of the ruby text is at least the width of 2.739 + the base, then the same type of space distribution applies to the base. 2.740 + In other words, if the base is shorter than the ruby text, the base is 2.741 + distribute-space aligned. This type of alignment 2.742 + is described by [[JLREQ]]. 2.743 + <div class="figure"> 2.744 + <p><img class="example" width="145" height="91" 2.745 + alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is shorter than base" 2.746 + src="images/ra-ds.gif" /><img class="example" width="145" height="91" 2.747 + alt="Diagram of glyph layout in distribute-space aligned ruby when ruby text is longer than base" 2.748 + src="images/ra-ds-rb.gif" /></p> 2.749 + <p><b>Figure 4.2.7</b>: Distribute-space ruby alignment</p> 2.750 + </div> 2.751 + </dd> 2.752 + <dt><strong>line-edge</strong></dt> 2.753 + <dd>If the ruby text is not adjacent to a line edge, it is aligned as in 2.754 + 'auto'. If it is adjacent to a line edge, then it is still aligned as in 2.755 + auto, but the side of the ruby text that touches the end of the line is 2.756 + lined up with the corresponding edge of the base. This type of alignment 2.757 + is described by [[JLREQ]]. This type of alignment is 2.758 + relevant only to the scenario where the ruby text is longer than the 2.759 + ruby base. In the other scenarios, this is just 'auto'. 2.760 + <div class="figure"> 2.761 + <p><img class="example" width="146" height="109" 2.762 + alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is shorter than base" 2.763 + src="images/ra-le-l.gif" /><img class="example" width="146" 2.764 + height="110" 2.765 + alt="Diagram of glyph layout in line-edge aligned ruby when ruby text is longer than base" 2.766 + src="images/ra-le-r.gif" /></p> 2.767 + <p><b>Figure 4.2.8</b>: Line edge ruby alignment</p> 2.768 + </div> 2.769 + </dd> 2.770 +</dl> 2.771 + 2.772 +<p>For a complex ruby with spanning elements, one additional consideration is 2.773 +required. If the spanning element spans multiple 'rows' (other rbc or rtc 2.774 +elements), and the ruby alignment requires space distribution among the 2.775 +'spanned' elements, a ratio must be determined among the 'columns' of spanned 2.776 +elements. This ratio is computed by taking into consideration the widest 2.777 +element within each column.</p> 2.778 + 2.779 +<p>In the context of this property, the 'left' and 'right' values are 2.780 +synonymous with the 'start' and 'end' values respectively. I.e. their meaning 2.781 +is relative according to the text layout flow. Most of the other CSS 2.782 +properties interpret 'left' and 'right' on an 'absolute' term. See Appendix A 2.783 +of the <a href="#CSS3TEXT">CSS3 Text Module</a> for further details.</p> 2.784 + 2.785 +<h3 id="rubyover"> 2.786 +Ruby overhanging: the 'ruby-overhang' property</h3> 2.787 + 2.788 + <table class="propdef"> 2.789 + <tr> 2.790 + <th>Name: 2.791 + <td><dfn>ruby-overhang</dfn> 2.792 + <tr> 2.793 + <th>Value: 2.794 + <td>auto | start | end | none 2.795 + <tr> 2.796 + <th>Initial: 2.797 + <td>none 2.798 + <tr> 2.799 + <th>Applies to: 2.800 + <td>the parent of elements with display: ruby-text 2.801 + <tr> 2.802 + <th>Inherited: 2.803 + <td>yes 2.804 + <tr> 2.805 + <th>Percentages: 2.806 + <td>N/A 2.807 + <tr> 2.808 + <th>Media: 2.809 + <td>visual 2.810 + <tr> 2.811 + <th>Computed value: 2.812 + <td>specified value (except for initial and inherit) 2.813 + </table> 2.814 + 2.815 +<p>This property determines whether, and on which side, ruby text is allowed 2.816 +to partially overhang any adjacent text in addition to its own base, when the 2.817 +ruby text is wider than the ruby base. Note that ruby text is never allowed to 2.818 +overhang glyphs belonging to another ruby base. <span class="issue"><span class="issuehead">Issue: </span> This rule must be broken if we are to allow support for jukugo ruby.</span> Also the user agent is free to assume 2.819 +a maximum amount by which ruby text may overhang adjacent text. The user agent may use 2.820 +the [[JIS4051]] recommendation of using one ruby text character 2.821 +length as the maximum overhang length. Detailed rules for how ruby text can overhang adjacent characters for Japanese are described by [[JLREQ]].</p> 2.822 + 2.823 +<p>Possible values:</p> 2.824 +<dl> 2.825 + <dt><strong>auto</strong></dt> 2.826 + <dd>The ruby text can overhang text adjacent to the base on either side. [[JLREQ]] and [[JIS4051]] specify the categories of characters that 2.827 + ruby text can overhang. The user agent is free to follow those recommendations or specify its own classes of 2.828 + characters to overhang. This is the initial value. 2.829 + <div class="figure"> 2.830 + <p><img class="example" width="177" height="91" 2.831 + alt="Diagram of glyph layout in overhanging ruby" src="images/ro-a.gif" /></p> 2.832 + <p><b>Figure 4.3.1</b>: Ruby overhanging adjacent text</p> 2.833 + </div> 2.834 + </dd> 2.835 + <dt><strong>start</strong></dt> 2.836 + <dd>The ruby text can only overhang the text that precedes it. That means, for 2.837 + example, that ruby cannot overhang text that is to the right of it in 2.838 + horizontal LTR layout, and it cannot overhang text that is below it in 2.839 + vertical-ideographic layout. 2.840 + <div class="figure"> 2.841 + <p><img class="example" width="199" height="91" 2.842 + alt="Diagram of glyph layout when ruby overhangs the preceding glyphs only" 2.843 + src="images/ro-s.gif" /></p> 2.844 + <p><b>Figure 4.3.2</b>: Ruby overhanging preceding text only</p> 2.845 + </div> 2.846 + </dd> 2.847 + <dt><strong>end</strong></dt> 2.848 + <dd>The ruby text can only overhang the text that follows it. That means, for 2.849 + example, that ruby cannot overhang text that is to the left of it in 2.850 + horizontal LTR layout, and it cannot overhang text that is above it in 2.851 + vertical-ideographic layout. 2.852 + <div class="figure"> 2.853 + <p><img class="example" width="198" height="91" 2.854 + alt="Diagram of glyph layout when ruby overhangs the following characters only" 2.855 + src="images/ro-e.gif" /></p> 2.856 + <p><b>Figure 4.3.3</b>: Ruby overhanging following text only</p> 2.857 + </div> 2.858 + </dd> 2.859 + <dt><strong>none</strong></dt> 2.860 + <dd>The ruby text cannot overhang any text adjacent to its base, only its 2.861 + own base. 2.862 + 2.863 + <div class="figure"> 2.864 + <p><img class="example" width="220" height="91" 2.865 + alt="Diagram of glyph layout in non-overhanging ruby" 2.866 + src="images/ro-n.gif" /></p> 2.867 + <p><b>Figure 4.3.4</b>: Ruby not allowed to overhang adjacent text</p> 2.868 + </div> 2.869 + </dd> 2.870 +</dl> 2.871 + 2.872 +<h3 id="rubyspan"> 2.873 +Ruby annotation spanning: the 'ruby-span' property</h3> 2.874 + 2.875 + <table class="propdef"> 2.876 + <tr> 2.877 + <th>Name: 2.878 + <td><dfn>ruby-span</dfn> 2.879 + <tr> 2.880 + <th>Value: 2.881 + <td>attr(x) | none 2.882 + <tr> 2.883 + <th>Initial: 2.884 + <td>none 2.885 + <tr> 2.886 + <th>Applies to: 2.887 + <td>elements with display: ruby-text 2.888 + <tr> 2.889 + <th>Inherited: 2.890 + <td>no 2.891 + <tr> 2.892 + <th>Percentages: 2.893 + <td>N/A 2.894 + <tr> 2.895 + <th>Media: 2.896 + <td>visual 2.897 + <tr> 2.898 + <th>Computed value: 2.899 + <td><number> 2.900 + </table> 2.901 + 2.902 +<p>This property controls the spanning behavior of annotation elements. </p> 2.903 + 2.904 +<p class="note"><span class="note-label">Note:</span> A XHTML user agent may also use the <samp>rbspan</samp> 2.905 +attribute to get the same effect.</p> 2.906 + 2.907 +<p>Possible values:</p> 2.908 + 2.909 +<dl> 2.910 + <dt><strong>attr(x)</strong></dt> 2.911 + <dd>The value of attribute 'x' as a string value. The string value is 2.912 + evaluated as a <number> to determine the number of ruby base elements to be 2.913 + spanned by the annotation element. If the <number> is '0', it is replaced by 2.914 + '1'.The <number> is the computed value. </dd> 2.915 + <dt>none</dt> 2.916 + <dd>No spanning. The computed value is '1'.</dd> 2.917 +</dl> 2.918 + 2.919 +<p>The following example shows an XML example using the 'display' property 2.920 +values associated with the 'ruby structure and the 'ruby-span' property</p> 2.921 +<pre class="xml">myruby { display: ruby; } 2.922 +myrbc { display: ruby-base-container; } 2.923 +myrb { display: ruby-base; } 2.924 +myrtc.before { display: ruby-text-container; ruby-position: before} 2.925 +myrtc.after { display: ruby-text-container; ruby-position: after} 2.926 +myrt { display: ruby-text; ruby-span: attr(rbspan); } 2.927 +... 2.928 +<myruby> 2.929 + <myrbc> 2.930 + <myrb>10</myrb> 2.931 + <myrb>31</myrb> 2.932 + <myrb>2002</myrb> 2.933 + </myrbc> 2.934 + <myrtc class="before"> 2.935 + <myrt>Month</myrt> 2.936 + <myrt>Day</myrt> 2.937 + <myrt>Year</myrt> 2.938 + </myrtc> 2.939 + <myrtc class="after"> 2.940 + <myrt rbspan="3">Expiration Date</myrt> 2.941 + </myrtc> 2.942 +</myruby></pre> 2.943 + 2.944 +<p class="issue"><span class="issuehead">Issue: </span> The i18n WG has requested the addition of a sample user agent default style sheet, as promised by Ruby Annotation section 3.4. See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=[CSS3+Ruby]%20Default+stylesheet&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.945 + 2.946 +<h2 id="profiles"> 2.947 +Profiles</h2> 2.948 + 2.949 +<p>There are two modules defined by this module:</p> 2.950 + 2.951 +<p>CSS3 Simple Ruby model</p> 2.952 + 2.953 +<p>CSS3 Complex Ruby model.</p> 2.954 + 2.955 +<p>They both contain all the properties specified by this CSS chapter, i.e. <a 2.956 +href="#rubyalign">'ruby-align'</a>, <a href="#rubyover">'ruby-overhang'</a>, <a href="#rubypos">'ruby-position'</a> 2.957 +and <a href="#rubyspan">'ruby-span'</a>. They differ by the required 2.958 +'display' property values. The Simple Ruby model requires the values: 'ruby', 2.959 +'ruby-base' and 'ruby-text'. The Complex Ruby model requires in addition the 2.960 +values: 'ruby-base-container' and 'ruby-text-container'.</p> 2.961 + 2.962 +<h2 id="glossary"> 2.963 +Glossary</h2> 2.964 +<dl> 2.965 + <dt><a id="g-bopomofo"><strong><span 2.966 + lang="zh">Bopomofo</span></strong></a></dt> 2.967 + <dd>37 characters and 4 tone markings used as phonetics in Chinese, 2.968 + especially standard Mandarin.</dd> 2.969 + <dt><a id="g-hanja"><strong><span 2.970 + lang="ko">Hanja</span></strong></a></dt> 2.971 + <dd>Subset of the Korean writing system that utilizes ideographic 2.972 + characters borrowed or adapted from the Chinese writing system. Also see 2.973 + <a href="#g-kanji"><span lang="ja">Kanji</span></a>.</dd> 2.974 + <dt><a id="g-hiragana"><strong><span 2.975 + lang="ja">Hiragana</span></strong></a></dt> 2.976 + <dd>Japanese syllabic script, or character of that script. Rounded and 2.977 + cursive in appearance. Subset of the Japanese writing system, used together 2.978 + with kanji and katakana. In recent times, mostly used to write Japanese 2.979 + words when kanji are not available or appropriate, and word endings and 2.980 + particles. Also see <a 2.981 + href="#g-katakana"><span lang="ja">Katakana</span></a>.</dd> 2.982 + <dt><a id="g-ideogram"><strong>Ideograph</strong></a></dt> 2.983 + <dd>A character that is used to represent an idea, word, or word component, 2.984 + in contrast to a character from an alphabetic or syllabic script. The most 2.985 + well-known ideographic script is used (with some variation) in East Asia 2.986 + (China, Japan, Korea,...).</dd> 2.987 + <dt><a id="g-kana"><strong><span lang="ja">Kana</span></strong></a></dt> 2.988 + <dd>Collective term for hiragana and katakana.</dd> 2.989 + <dt><a id="g-kanji"><strong>Kanji</strong></a></dt> 2.990 + <dd>Japanese term for ideographs; ideographs used in Japanese. Subset of the 2.991 + Japanese writing system, used together with hiragana and katakana. Also see <a 2.992 + href="#g-hanja"><span lang="ko">Hanja</span></a>.</dd> 2.993 + <dt><a id="g-katakana"><strong><span 2.994 + lang="ja">Katakana</span></strong></a></dt> 2.995 + <dd>Japanese syllabic script, or character of that script. Angular in 2.996 + appearance. Subset of the Japanese writing system, used together with 2.997 + kanji and hiragana. In recent times, mainly used to write foreign words. Also see <a 2.998 + href="#g-hiragana"><span lang="ja">Hiragana</span></a>.</dd> 2.999 + <dt><a id="g-monoruby" name="g-monoruby"><strong>Mono-ruby</strong></a></dt> 2.1000 + <dd>In Japanese typography: Ruby associated with a single character of 2.1001 + the base text.</dd> 2.1002 + <dt><a id="g-ruby"><strong>Ruby</strong></a></dt> 2.1003 + <dd>A run of text that appears in the vicinity of another run of text and 2.1004 + serves as an annotation or a pronunciation guide for that text.</dd> 2.1005 +</dl> 2.1006 + 2.1007 +<h2 id="conformance"> 2.1008 +Conformance</h2> 2.1009 + 2.1010 +<h3 id="conventions"> 2.1011 +Document conventions</h3> 2.1012 + 2.1013 + <p>Conformance requirements are expressed with a combination of 2.1014 + descriptive assertions and RFC 2119 terminology. The key words “MUST”, 2.1015 + “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, 2.1016 + “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this 2.1017 + document are to be interpreted as described in RFC 2119. 2.1018 + However, for readability, these words do not appear in all uppercase 2.1019 + letters in this specification. 2.1020 + 2.1021 + <p>All of the text of this specification is normative except sections 2.1022 + explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p> 2.1023 + 2.1024 + <p>Examples in this specification are introduced with the words “for example” 2.1025 + or are set apart from the normative text with <code>class="example"</code>, 2.1026 + like this: 2.1027 + 2.1028 + <div class="example"> 2.1029 + <p>This is an example of an informative example.</p> 2.1030 + </div> 2.1031 + 2.1032 + <p>Informative notes begin with the word “Note” and are set apart from the 2.1033 + normative text with <code>class="note"</code>, like this: 2.1034 + 2.1035 + <p class="note">Note, this is an informative note.</p> 2.1036 + 2.1037 +<h3 id="conformance-classes"> 2.1038 +Conformance classes</h3> 2.1039 + 2.1040 + <p>Conformance to CSS Ruby Module 2.1041 + is defined for three conformance classes: 2.1042 + <dl> 2.1043 + <dt><dfn title="style sheet!!as conformance class">style sheet</dfn> 2.1044 + <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS 2.1045 + style sheet</a>. 2.1046 + <dt><dfn>renderer</dfn></dt> 2.1047 + <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> 2.1048 + that interprets the semantics of a style sheet and renders 2.1049 + documents that use them. 2.1050 + <dt><dfn id="authoring-tool">authoring tool</dfn></dt> 2.1051 + <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> 2.1052 + that writes a style sheet. 2.1053 + </dl> 2.1054 + 2.1055 + <p>A style sheet is conformant to CSS Ruby Module 2.1056 + if all of its statements that use syntax defined in this module are valid 2.1057 + according to the generic CSS grammar and the individual grammars of each 2.1058 + feature defined in this module. 2.1059 + 2.1060 + <p>A renderer is conformant to CSS Ruby Module 2.1061 + if, in addition to interpreting the style sheet as defined by the 2.1062 + appropriate specifications, it supports all the features defined 2.1063 + by CSS Ruby Module by parsing them correctly 2.1064 + and rendering the document accordingly. However, the inability of a 2.1065 + UA to correctly render a document due to limitations of the device 2.1066 + does not make the UA non-conformant. (For example, a UA is not 2.1067 + required to render color on a monochrome monitor.) 2.1068 + 2.1069 + <p>An authoring tool is conformant to CSS Ruby Module 2.1070 + if it writes style sheets that are syntactically correct according to the 2.1071 + generic CSS grammar and the individual grammars of each feature in 2.1072 + this module, and meet all other conformance requirements of style sheets 2.1073 + as described in this module. 2.1074 + 2.1075 +<h3 id="partial"> 2.1076 +Partial implementations</h3> 2.1077 + 2.1078 + <p>So that authors can exploit the forward-compatible parsing rules to 2.1079 + assign fallback values, CSS renderers <strong>must</strong> 2.1080 + treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore 2.1081 + as appropriate</a>) any at-rules, properties, property values, keywords, 2.1082 + and other syntactic constructs for which they have no usable level of 2.1083 + support. In particular, user agents <strong>must not</strong> selectively 2.1084 + ignore unsupported component values and honor supported values in a single 2.1085 + multi-value property declaration: if any value is considered invalid 2.1086 + (as unsupported values must be), CSS requires that the entire declaration 2.1087 + be ignored.</p> 2.1088 + 2.1089 +<h3 id="experimental"> 2.1090 +Experimental implementations</h3> 2.1091 + 2.1092 + <p>To avoid clashes with future CSS features, the CSS2.1 specification 2.1093 + reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed 2.1094 + syntax</a> for proprietary and experimental extensions to CSS. 2.1095 + 2.1096 + <p>Prior to a specification reaching the Candidate Recommendation stage 2.1097 + in the W3C process, all implementations of a CSS feature are considered 2.1098 + experimental. The CSS Working Group recommends that implementations 2.1099 + use a vendor-prefixed syntax for such features, including those in 2.1100 + W3C Working Drafts. This avoids incompatibilities with future changes 2.1101 + in the draft. 2.1102 + </p> 2.1103 + 2.1104 +<h3 id="testing"> 2.1105 +Non-experimental implementations</h3> 2.1106 + 2.1107 + <p>Once a specification reaches the Candidate Recommendation stage, 2.1108 + non-experimental implementations are possible, and implementors should 2.1109 + release an unprefixed implementation of any CR-level feature they 2.1110 + can demonstrate to be correctly implemented according to spec. 2.1111 + 2.1112 + <p>To establish and maintain the interoperability of CSS across 2.1113 + implementations, the CSS Working Group requests that non-experimental 2.1114 + CSS renderers submit an implementation report (and, if necessary, the 2.1115 + testcases used for that implementation report) to the W3C before 2.1116 + releasing an unprefixed implementation of any CSS features. Testcases 2.1117 + submitted to W3C are subject to review and correction by the CSS 2.1118 + Working Group. 2.1119 + 2.1120 + <p>Further information on submitting testcases and implementation reports 2.1121 + can be found from on the CSS Working Group's website at 2.1122 + <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>. 2.1123 + Questions should be directed to the 2.1124 + <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a> 2.1125 + mailing list. 2.1126 + 2.1127 +<h2 class=no-num id="acknowledgments"> 2.1128 +Acknowledgments</h2> 2.1129 + 2.1130 +<p>This specification would not have been possible without the help from:</p> 2.1131 + 2.1132 +<p>Stephen Deach, Martin Dürst, Hideki Hiura(<span lang="ja">樋浦 秀樹</span>), Masayasu Ishikawa(<span lang="ja">石川 2.1133 +雅康</span>), Chris 2.1134 +Pratley, Takao Suzuki(<span lang="ja">鈴木 孝雄</span>), Frank Yung-Fong Tang, Chris Thrasher, Masafumi Yabe<span lang="ja">家辺 2.1135 +勝文</span>), Steve Zilles.</p> 2.1136 + 2.1137 +<h2 class=no-num id="references"> 2.1138 +References</h2> 2.1139 + 2.1140 +<h3 class="no-num" id="normative-references"> 2.1141 +Normative references</h3> 2.1142 +<!--normative--> 2.1143 + 2.1144 +<h3 class="no-num" id="other-references"> 2.1145 +Other references</h3> 2.1146 +<!--informative--> 2.1147 + 2.1148 +<h2 class="no-num" id="index"> 2.1149 +Index</h2> 2.1150 +<!--index--> 2.1151 + 2.1152 +<h2 class="no-num" id="property-index"> 2.1153 +Property index</h2> 2.1154 +<!-- properties --> 2.1155 + 2.1156 +</body> 2.1157 +</html> 2.1158 +<!-- Keep this comment at the end of the file 2.1159 +Local variables: 2.1160 +mode: sgml 2.1161 +sgml-declaration:"~/SGML/HTML4.decl" 2.1162 +sgml-default-doctype-name:"html" 2.1163 +sgml-minimize-attributes:t 2.1164 +sgml-nofill-elements:("pre" "style" "br") 2.1165 +sgml-live-element-indicator:t 2.1166 +sgml-omittag:nil 2.1167 +sgml-shorttag:nil 2.1168 +sgml-namecase-general:t 2.1169 +sgml-general-insert-case:lower 2.1170 +sgml-always-quote-attributes:t 2.1171 +sgml-indent-step:nil 2.1172 +sgml-indent-data:t 2.1173 +sgml-parent-document:nil 2.1174 +sgml-exposed-tags:nil 2.1175 +sgml-local-catalogs:nil 2.1176 +sgml-local-ecat-files:nil 2.1177 +End: 2.1178 +--> 2.1179 +
