- From: poot <cvsmail@w3.org>
- Date: Thu, 5 Feb 2009 10:56:05 +0900 (JST)
- To: public-html-diffs@w3.org
Filling in the rendering section: embedded content section. (whatwg
r2757)
4.9.2 The table element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#the-table-element
Status of this document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#status-of-this-document
width
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#dom-dim-width
A vocabulary and associated APIs for HTML and XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
10.3.7 Resetting rules for inherited properties
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#resetting-rules-for-inherited-properties
10.4.2 Fragment identifiers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#fragment-identifiers
4.9 Tabular data
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#tabular-data
container frame element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#container-frame-element
4.8.17 Dimension attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#dimension-attributes
10.3.5 Fonts and colors
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#fonts-and-colors
10.4.3 Frames
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#frames
10.3.6 Punctuation and decorations
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#punctuation-and-decorations
Editor's Draft 5 February 2009
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#editor-s-draft-date-zzz-9-june-2008
10.4 Self-contained features
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#self-contained-features
10.3.4 Alignment
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1927.html#alignment
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1926&r2=1.1927&f=h
http://html5.org/tools/web-apps-tracker?from=2756&to=2757
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1926
retrieving revision 1.1927
diff -u -d -r1.1926 -r1.1927
--- Overview.html 4 Feb 2009 22:34:45 -0000 1.1926
+++ Overview.html 5 Feb 2009 01:52:46 -0000 1.1927
@@ -10,7 +10,7 @@
<p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
<h1>HTML 5</h1>
<h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->4 February 2009</h2>
+ <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->5 February 2009</h2>
<dl><!-- ZZZ: update the month/day
<dt>This Version:</dt>
<dd><a href="http://www.w3.org/TR/2009/WD-html5-20090610/">http://www.w3.org/TR/2009/WD-html5-20090610/</a></dd>
@@ -99,7 +99,7 @@
specification's progress along the W3C Recommendation
track.
<!--ZZZ:-->
- This specification is the 4 February 2009 <!--ZZZ "Working Draft"-->Editor's Draft.
+ This specification is the 5 February 2009 <!--ZZZ "Working Draft"-->Editor's Draft.
<!--:ZZZ-->
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -18058,17 +18058,11 @@
intrinsic width to the intrinsic height in the resource. The <var title="">specified width</var> and <var title="">specified
height</var> are the values of the <code title=attr-dim-width><a href=#attr-dim-width>width</a></code> and <code title=attr-dim-height><a href=#attr-dim-height>height</a></code> attributes respectively.<p>The two attributes must be omitted if the resource in question
does not have both an intrinsic width and an intrinsic height.<p class=note>Basically, the dimension attributes can't be used to
- stretch the image.<p>To parse the attributes, user agents must use the <a href=#rules-for-parsing-dimension-values>rules for
- parsing dimension values</a>. This will return either an integer
- length, a percentage value, or nothing. The user agent requirements
- for processing the values obtained from parsing these attributes are
- described <a href=#sizing-of-embedded-content title="sizing of embedded content">in the rendering
- section</a><!-- XXX xref -->. If one of these attributes, when
- parsing, returns no value, it must be treated, for the purposes of
- those requirements, as if it was not specified.<p>The <dfn id=dom-dim-width title=dom-dim-width><code>width</code></dfn> and <dfn id=dom-dim-height title=dom-dim-height><code>height</code></dfn> DOM attributes on
+ stretch the image.<p>The <dfn id=dom-dim-width title=dom-dim-width><code>width</code></dfn> and <dfn id=dom-dim-height title=dom-dim-height><code>height</code></dfn> DOM attributes on
the <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-object-element>object</a></code>,
and <code><a href=#video>video</a></code> elements must <a href=#reflect>reflect</a> the
- respective content attributes of the same name.<h3 id=tabular-data><span class=secno>4.9 </span>Tabular data</h3><h4 id=table-intro><span class=secno>4.9.1 </span>Introduction</h4><p><em>This section is non-normative.</em><p class=XXX>...examples, how to write tables accessibly, a
+ respective content attributes of the same name.</p><!-- XXX check
+ that this is defined right in the face of percentages --><h3 id=tabular-data><span class=secno>4.9 </span>Tabular data</h3><h4 id=table-intro><span class=secno>4.9.1 </span>Introduction</h4><p><em>This section is non-normative.</em><p class=XXX>...examples, how to write tables accessibly, a
brief mention of the table model, etc...<h4 id=the-table-element><span class=secno>4.9.2 </span>The <dfn><code>table</code></dfn> element</h4><dl class=element><dt>Categories</dt>
<dd><a href=#flow-content-0>Flow content</a>.</dd>
<dt>Contexts in which this element may be used:</dt>
@@ -46238,11 +46232,11 @@
properties</a> 'padding-top', 'padding-right', 'padding-bottom',
and 'padding-left' of any <code><a href=#the-td-element>td</a></code> and <code><a href=#the-th-element>th</a></code>
elements that have corresponding <a href=#concept-cell title=concept-cell>cells</a> in the <a href=#concept-table title=concept-table>table</a> corresponding to the
- <code><a href=#the-table-element>table</a></code> element.<p>The <code><a href=#the-table-element>table</a></code> element's <code title=attr-table-hspace>hspace</code> attribute <a href=#maps-to-the-pixel-length-property title="maps
- to the pixel length property">maps to the pixel length properties</a>
+ <code><a href=#the-table-element>table</a></code> element.<p>The <code><a href=#the-table-element>table</a></code> element's <code title=attr-table-hspace>hspace</code> attribute <a href=#maps-to-the-dimension-property title="maps
+ to the dimension property">maps to the dimension properties</a>
'margin-left' and 'margin-right' on the <code><a href=#the-table-element>table</a></code>
- element.<p>The <code><a href=#the-table-element>table</a></code> element's <code title=attr-table-vspace>vspace</code> attribute <a href=#maps-to-the-pixel-length-property title="maps
- to the pixel length property">maps to the pixel length properties</a>
+ element.<p>The <code><a href=#the-table-element>table</a></code> element's <code title=attr-table-vspace>vspace</code> attribute <a href=#maps-to-the-dimension-property title="maps
+ to the dimension property">maps to the dimension properties</a>
'margin-top' and 'margin-bottom' on the <code><a href=#the-table-element>table</a></code>
element.<p>The <code><a href=#the-table-element>table</a></code> element's <code title=attr-table-height>height</code> attribute <a href=#maps-to-the-dimension-property>maps to the
dimension property</a> 'height' on the <code><a href=#the-table-element>table</a></code>
@@ -46259,9 +46253,7 @@
on the element.</p><hr><p>In <a href=#quirks-mode>quirks mode</a>, the following rules are also
expected to apply:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
-form { margin-bottom: 1em; }
-img[align=left] { margin-right: 3px; }
-img[align=right] { margin-left: 3px; }</pre><p>When a <code>Document</code> is in <a href=#quirks-mode>quirks mode</a>,
+form { margin-bottom: 1em; }</pre><p>When a <code>Document</code> is in <a href=#quirks-mode>quirks mode</a>,
margins on <a href=#html-elements>HTML elements</a> that collapse with the top or
bottom of the initial containing block are expected to be collapsed
to zero.<h4 id=alignment><span class=secno>10.3.4 </span>Alignment</h4><pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
@@ -46273,8 +46265,8 @@
th { text-align: center; }</pre><hr><p>The following rules are also expected to apply, as
<a href=#presentational-hints>presentational hints</a>:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
-table[align=left], img[align=left] { float: left; }
-table[align=right], img[align=right] { float: right; }
+table[align=left] { float: left; }
+table[align=right] { float: right; }
table[align=center], table[align=abscenter],
table[align=abdmiddle], table[align=middle] {
margin-left: auto; margin-right: auto;
@@ -46599,10 +46591,10 @@
<td>xx-large
<td>
<tr><td>7
- <td>xxx-large
+ <td>x<!---->xx-large
<td><i>see below</i>
- </table><p>The 'xxx-large' value is a non-CSS value used here to indicate
- a font size one "step" larger than 'xx-large'.</p>
+ </table><p>The 'x<!---->xx-large' value is a non-CSS value used here to
+ indicate a font size one "step" larger than 'xx-large'.</p>
</li>
@@ -46651,7 +46643,6 @@
list-style-type: square;
}
-iframe { border: 2px inset; }
table { border-style: outset; }
td, th { border-style: inset; }
@@ -46788,23 +46779,143 @@
line-height: initial;
white-space: initial;
text-align: initial;
-}</pre><h3 id=self-contained-features><span class=secno>10.4 </span>Self-contained features</h3><h4 id=embedded-content-1><span class=secno>10.4.1 </span>Embedded content</h4><p class=XXX>...</p><!-- applet, canvas, embed, iframe, img, input type=image, object, video --><!-- <code>input</code> elements whose <code title="attr-input-type">type</code> attribute is in the <span title="attr-input-type-image">Image Button</span> state --><!--
- iframe:
- width, height = as <img>; frameborder, scrolling=as <frame>; align=as <img>; marginheight, marginwidth (int/%) (=?)
- img, input type=image, object:
- width, height (int/%); hspace, vspace => margins (int/%); border (int>=0) => border-width, with border-style: solid;
- align (left=float:left|right=float:right|top=v-a:t|bottom/baseline=v-a:b|center/middle=[1]|texttop=v-a:tt|absmiddle/abscenter=v-a:m|absbottom=v-a:b)
- [1] = position vertical middle with parent baseline
- --><!--
- img - how to handle alt text, img in link (no border)... Define
- that either the src="" is shown (as an image) or the alt="" is
- shown (inline) but should not ever have both at once.
- --><p class=XXX>Terms that need to be defined include: <dfn id=sizing-of-embedded-content>sizing
- of embedded content</dfn></p><!-- audio --><h4 id=fragment-identifiers><span class=secno>10.4.2 </span>Fragment identifiers</h4><p class=XXX>(need to remove "must" and reword) CSS UAs in visual
+}</pre><h3 id=self-contained-features><span class=secno>10.4 </span>Self-contained features</h3><h4 id=embedded-content-1><span class=secno>10.4.1 </span>Embedded content</h4><p>The <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-canvas-element>canvas</a></code>, <code><a href=#the-embed-element>embed</a></code>,
+ <code><a href=#the-iframe-element>iframe</a></code>, and <code><a href=#video>video</a></code> elements are expected to
+ be treated as replaced elements.</p><hr><p>When an <code><a href=#the-img-element>img</a></code> element or an <code><a href=#the-input-element>input</a></code> element
+ when its <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
+ the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state
+ <a href=#represents>represents</a> an image, it is expected to be treated as a
+ replaced element.<p>When an <code><a href=#the-img-element>img</a></code> element or an <code><a href=#the-input-element>input</a></code> element
+ when its <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
+ the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state
+ does not <a href=#represents title=represents>represent</a> an image, but the
+ element already has instrinsic dimensions (e.g. from the
+ <a href=#dimension-attributes>dimension attributes</a> or CSS rules), and either the user
+ agent has reason to believe that the image will become
+ <i>available</i> and be rendered in due course or the
+ <code>Document</code> is in <a href=#quirks-mode>quirks mode</a>, the element is
+ expected to be treated as a replaced element whose content is the
+ text that the element represents, if any, optionally alongside an
+ icon indicating that the image is being obtained. For
+ <code><a href=#the-input-element>input</a></code> elements, the text is expected to appear
+ button-like to indicate that the element is a <a href=#concept-button title=concept-button>button</a>.<p>When an <code><a href=#the-img-element>img</a></code> element <a href=#represents>represents</a> some
+ text and the user agent does not expect this to change, the element
+ is expected to be treated as an inline element whose content is the
+ text, optionally with an icon indicating that an image is
+ missing.<p>When an <code><a href=#the-img-element>img</a></code> element <a href=#represents>represents</a> nothing
+ and the user agent does not expect this to change, the element is
+ expected to not be rendered at all.<p>When an <code><a href=#the-img-element>img</a></code> element might be a key part of the
+ content, but neither the image nor any kind of alternative text is
+ available, and the user agent does not expect this to change, the
+ element is expected to be treated as an inline element whose content
+ is an icon indicating that an image is missing.</p><!-- there's
+ also a should requirement for this case in the <img> section itself
+ --><p>When an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state does not
+ <a href=#represents title=represents>represent</a> an image and the user
+ agent does not expect this to change, the element is expected to be
+ treated as a replaced element consisting of a button whose content
+ is the element's alternative text. The intrinsic dimensions of the
+ button are expected to be about one line in height and whatever
+ width is necessary to render the text on one line.<p>The icons mentioned above are expected to be relatively small so
+ as not to disrupt most text but be easily clickable, for instance 16
+ pixels by 16 pixels square, or 1em by 1em if the images are
+ scalable. The images are intended to indicate to the user that they
+ can be used to get to whatever options the UA provides for images,
+ and, where appropriate, are expected to provide access to the
+ context menu that would have come up if the user interacted with the
+ actual image.</p><hr><p>An <code><a href=#the-object-element>object</a></code> element that <a href=#represents>represents</a> an
+ image, plugin, or <a href=#nested-browsing-context>nested browsing context</a> is expected
+ to be treated as a replaced element. Other <code><a href=#the-object-element>object</a></code>
+ elements are expected to be treated as ordinary elements in the
+ rendering model.</p><hr><p>The <code><a href=#audio>audio</a></code> element, when it has a <code title=attr-media-controls><a href=#attr-media-controls>controls</a></code> attribute, is expected
+ to be treated as a replaced element about one line high, as wide as
+ is necessary to expose the user agent's user interface features.</p><hr><p>The following CSS rules are expected to apply:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
+
+iframe { border: 2px inset; }</pre><hr><p>The following CSS rules are expected to apply as
+ <a href=#presentational-hints>presentational hints</a>:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
+
+iframe[frameborder=0], iframe[frameborder=no] { border: none; }
+
+applet[align=left], embed[align=left], iframe[align=left],
+img[align=left], input[type=image][align=left], object[align=left] {
+ float: left;
+}
+
+applet[align=right], embed[align=right], iframe[align=right],
+img[align=right], input[type=image][align=right], object[align=right] {
+ float: right;
+}
+
+applet[align=top], embed[align=top], iframe[align=top],
+img[align=top], input[type=image][align=top], object[align=top] {
+ vertical-align: top;
+}
+
+applet[align=bottom], embed[align=bottom], iframe[align=bottom],
+img[align=bottom], input[type=image][align=bottom], object[align=bottom],
+applet[align=baseline], embed[align=baseline], iframe[align=baseline],
+img[align=baseline], input[type=image][align=baseline], object[align=baseline] {
+ vertical-align: baseline;
+}
+
+applet[align=texttop], embed[align=texttop], iframe[align=texttop],
+img[align=texttop], input[type=image][align=texttop], object[align=texttop] {
+ vertical-align: text-top;
+}
+
+applet[align=absmiddle], embed[align=absmiddle], iframe[align=absmiddle],
+img[align=absmiddle], input[type=image][align=absmiddle], object[align=absmiddle],
+applet[align=abscenter], embed[align=abscenter], iframe[align=abscenter],
+img[align=abscenter], input[type=image][align=abscenter], object[align=abscenter] {
+ vertical-align: middle;
+}
+
+applet[align=bottom], embed[align=bottom], iframe[align=bottom],
+img[align=bottom], input[type=image][align=bottom],
+object[align=bottom] {
+ vertical-align: bottom;
+}</pre><p>When an <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-embed-element>embed</a></code>,
+ <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, or <code><a href=#the-object-element>object</a></code>
+ element, or an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state, has an
+ <code title=attr-dim-align>align</code> attribute whose value is
+ an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string "<code title="">center</code>" or the string "<code title="">middle</code>", the user agent is expected to act as if the
+ element's 'vertical-align' property was set to a value that aligns
+ the vertical middle of the element with the parent element's
+ baseline.<p>The <code title=attr-dim-hspace>hspace</code> attribute of
+ <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+ <code><a href=#the-img-element>img</a></code>, or <code><a href=#the-object-element>object</a></code> elements, and
+ <code><a href=#the-input-element>input</a></code> elements with a <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state, <a href=#maps-to-the-dimension-property title="maps to the dimension property">maps to the dimension
+ properties</a> 'margin-left' and 'margin-right' on the
+ element.<p>The <code title=attr-dim-vspace>vspace</code> attribute of
+ <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+ <code><a href=#the-img-element>img</a></code>, or <code><a href=#the-object-element>object</a></code> elements, and
+ <code><a href=#the-input-element>input</a></code> elements with a <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state, <a href=#maps-to-the-dimension-property title="maps to the dimension property">maps to the dimension
+ properties</a> 'margin-top' and 'margin-bottom' on the
+ element.<p>When an <code><a href=#the-img-element>img</a></code> element, <code><a href=#the-object-element>object</a></code> element, or
+ <code><a href=#the-input-element>input</a></code> element with a <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state is contained
+ within a <a href=#hyperlink>hyperlink</a> and has a <code title=attr-dim-border>border</code> attribute whose value, when
+ parsed using the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative
+ integers</a>, is found to be a number greater than zero, the user
+ agent is expected to use the parsed value for eight
+ <a href=#presentational-hints>presentational hints</a>: four setting the parsed value as
+ a pixel length for the element's 'border-top-width',
+ 'border-right-width', 'border-bottom-width', and 'border-left-width'
+ properties, and four setting the element's 'border-top-style',
+ 'border-right-style', 'border-bottom-style', and 'border-left-style'
+ properties to the value 'solid'.<p>The <code title=attr-dim-width><a href=#attr-dim-width>width</a></code> and <code title=attr-dim-height><a href=#attr-dim-height>height</a></code> attributes on
+ <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-embed-element>embed</a></code>, <code><a href=#the-iframe-element>iframe</a></code>,
+ <code><a href=#the-img-element>img</a></code>, <code><a href=#the-object-element>object</a></code> or <code><a href=#video>video</a></code>
+ elements, and <code><a href=#the-input-element>input</a></code> elements with a <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state, <a href=#maps-to-the-pixel-length-property title="maps to the pixel length property">map to the dimension
+ properties</a> 'width' and 'height' on the element
+ respectively.</p><hr><p>The following CSS rules are expected to apply when the
+ <code>Document</code> is in <a href=#quirks-mode>quirks mode</a>:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
+
+img[align=left] { margin-right: 3px; }
+img[align=right] { margin-left: 3px; }</pre><h4 id=fragment-identifiers><span class=secno>10.4.2 </span>Fragment identifiers</h4><p class=XXX>(need to remove "must" and reword) CSS UAs in visual
media must, when scrolling a page to a fragment identifier, align
the top of the viewport with the target element's top border
edge.</p><!-- XXX horiz pos given bidi, and not scrolling when not
- required to? --><h4 id=frames><span class=secno>10.4.3 </span>Frames</h4><p class=XXX>...</p><!-- <frame>: bordercolor; frameborder (yes/1|no/0); marginwidth, marginheight (int/%); scrolling (yes/on/scroll|no/off/noscroll|auto) --><h4 id=ruby-annotations><span class=secno>10.4.4 </span>Ruby annotations</h4><p class=XXX>...</p><!-- XXX ruby, rt, rp
+ required to? --><h4 id=frames><span class=secno>10.4.3 </span>Frames</h4><p class=XXX>...</p><!-- <frame>: bordercolor; frameborder (yes/1|no/0); marginwidth, marginheight (int/%); scrolling (yes/on/scroll|no/off/noscroll|auto) --><!-- <frame>, <iframe>: scrolling (yes/on/scroll|no/off/noscroll|auto) --><h4 id=ruby-annotations><span class=secno>10.4.4 </span>Ruby annotations</h4><p class=XXX>...</p><!-- XXX ruby, rt, rp
> * note on rt rendering
>
> Since there are a number of documents with ruby but without rp, when you
Received on Thursday, 5 February 2009 01:56:48 UTC