- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 25 Mar 2011 22:46:33 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv24355
Modified Files:
Overview.html Overview.src.html
Log Message:
Changes to address feedback:
- Add module boilerplate, including values definition
<http://lists.w3.org/Archives/Public/www-style/2011Mar/0202.html>
- Fix inline-level / inline / block container terminology to match CSS2.1
- Address some editorial/clarifying comments from I18N
<http://lists.w3.org/Archives/Public/www-style/2011Mar/0199.html>
<http://lists.w3.org/Archives/Public/www-style/2011Mar/0200.html>
<http://lists.w3.org/Archives/Public/www-style/2011Mar/0201.html
- Clarify rotate-left
<http://lists.w3.org/Archives/Public/www-style/2011Mar/0541.html>
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- Overview.html 25 Mar 2011 08:02:08 -0000 1.89
+++ Overview.html 25 Mar 2011 22:46:31 -0000 1.90
@@ -142,6 +142,15 @@
<ul class=toc>
<li><a href="#text-flow"><span class=secno>1. </span>Introduction to
Writing Modes</a>
+ <ul class=toc>
+ <li><a href="#placement"><span class=secno>1.1. </span>Module
+ Interactions</a>
+
+ <li><a href="#conventions"><span class=secno>1.2. </span>Document
+ Conventions</a>
+
+ <li><a href="#values"><span class=secno>1.3. </span>Values</a>
+ </ul>
<li><a href="#text-direction"><span class=secno>2. </span>Inline Direction
and Bidirectionality</a>
@@ -366,6 +375,61 @@
<p class=issue>Point at Intro to Text Orientation section once it's
written.
+ <h3 id=placement><span class=secno>1.1. </span>Module Interactions</h3>
+
+ <p>This module replaces and extends the ‘<a
+ href="#unicode-bidi0"><code class=property>unicode-bidi</code></a>’
+ and ‘<a href="#direction0"><code
+ class=property>direction</code></a>’ features defined in <a
+ href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> sections 8.6
+ and 9.10.
+
+ <h3 id=conventions><span class=secno>1.2. </span>Document Conventions</h3>
+
+ <p>Conformance requirements are expressed with a combination of descriptive
+ assertions and RFC 2119 terminology. The key words “MUST”, “MUST
+ NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
+ “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the
+ normative parts of this document are to be interpreted as described in RFC
+ 2119. However, for readability, these words do not appear in all uppercase
+ letters in this specification.
+
+ <p>All of the text of this specification is normative except sections
+ explicitly marked as non-normative, examples, and notes. <a
+ href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>
+
+ <p>Examples in this specification are introduced with the words “for
+ example” or are set apart from the normative text with
+ <code>class="example"</code>, like this:
+
+ <div class=example>
+ <p>This is an example of an informative example.</p>
+ </div>
+
+ <p>Informative notes begin with the word “Note” and are set apart from
+ the normative text with <code>class="note"</code>, like this:
+
+ <p class=note>Note, this is an informative note.
+
+ <h3 id=values><span class=secno>1.3. </span>Values</h3>
+
+ <p>This specification follows the <a
+ href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
+ definition conventions</a> from <a href="#CSS21"
+ rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. Value types not defined in
+ this specification are defined in CSS Level 2 Revision 1 <a
+ href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. Other CSS
+ modules may expand the definitions of these value types: for example <a
+ href="#CSS3COLOR" rel=biblioentry>[CSS3COLOR]<!--{{CSS3COLOR}}--></a>,
+ when combined with this module, expands the definition of the
+ <color> value type as used in this specification.
+
+ <p>In addition to the property-specific values listed in their definitions,
+ all properties defined in this specification also accept the <a
+ href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
+ keyword as their property value. For readability it has not been repeated
+ explicitly.
+
<h2 id=text-direction><span class=secno>2. </span>Inline Direction and
Bidirectionality</h2>
@@ -585,35 +649,21 @@
<dt><strong>normal</strong>
<dd>The element does not open an additional level of embedding with
- respect to the bidirectional algorithm. For inline-level elements,
- implicit reordering works across element boundaries.
+ respect to the bidirectional algorithm. For inline elements, implicit
+ reordering works across element boundaries.
<dt><strong>embed</strong>
- <dd>If the element is inline-level, this value opens an additional level
- of embedding with respect to the bidirectional algorithm. The direction
- of this embedding level is given by the ‘<a
- href="#direction0"><code class=property>direction</code></a>’
- property. Inside the element, reordering is done implicitly. This
- corresponds to adding a LRE (U+202A; for ‘<code
- class=css>direction: ltr</code>’) or RLE (U+202B; for ‘<code
- class=css>direction: rtl</code>’) at the start of the element and a
- PDF (U+202C) at the end of the element.
-
- <dt><strong>bidi-override</strong>
-
- <dd>For inline-level elements this creates an override. For block-level,
- table-cell, table-caption, or inline-block elements this creates an
- override for inline-level descendants not within another block-level,
- table-cell, table-caption, or inline-block element. This means that
- inside the element, reordering is strictly in sequence according to the
- <span class=propinst-direction>‘<a href="#direction0"><code
- class=property>direction</code></a>’</span> property; the implicit
- part of the bidirectional algorithm is ignored. This corresponds to
- adding a LRO (U+202D; for ‘<code class=css>direction:
- ltr</code>’) or RLO (U+202E; for ‘<code class=css>direction:
- rtl</code>’) at the start of the element and a PDF (U+202C) at the
- end of the element.
+ <dd>If the element is inline, this value opens an additional level of
+ embedding with respect to the bidirectional algorithm. The direction of
+ this embedding level is given by the ‘<a href="#direction0"><code
+ class=property>direction</code></a>’ property. Inside the element,
+ reordering is done implicitly. This corresponds to adding a LRE (U+202A),
+ for ‘<code class=css>direction: ltr</code>’, or RLE (U+202B),
+ for ‘<code class=css>direction: rtl</code>’, at the start of
+ the element and a PDF (U+202C) at the end of the element. <span
+ class=note>This value has no effect on elements that are not
+ inline.</span>
<dt><strong>isolate</strong>
@@ -629,11 +679,24 @@
<dd>
<p>For the purposes of the Unicode bidirectional algorithm, the base
- directionality of each "paragraph" for which the element forms the
+ directionality of each bidi paragraph for which the element forms the
containing block is determined not by the element's computed ‘<a
href="#direction0"><code class=property>direction</code></a>’ as
usual, but by following rules P2 and P3 of the Unicode bidirectional
algorithm. Note this value has no effect on inline elements.
+
+ <dt><strong>bidi-override</strong>
+
+ <dd>For inline elements this creates an override. For block-container
+ elements this creates an override for inline-level descendants not within
+ another block container element. This means that inside the element,
+ reordering is strictly in sequence according to the ‘<a
+ href="#direction0"><code class=property>direction</code></a>’
+ property; the implicit part of the bidirectional algorithm is ignored.
+ This corresponds to adding a LRO (U+202D), for ‘<code
+ class=css>direction: ltr</code>’, or RLO (U+202E), for ‘<code
+ class=css>direction: rtl</code>’, at the start of the element and a
+ PDF (U+202C) at the end of the element.
</dl>
<p>The final order of characters within in each bidi paragraph is the same
@@ -807,9 +870,9 @@
<h2 id=vertical-intro><span class=secno>3. </span> Introduction to Vertical
Text</h2>
- <p>In addition to extensions to CSS2.1's support for bidirectional
- text, this module introduces the rules and properties needed to support
- vertical text layout in CSS.
+ <p>In addition to extensions to CSS2.1‘<code class=css>s support for
+ bidirectional text, this module introduces the rules and properties needed
+ to support vertical text layout in CSS. </code>
<p>Unlike languages that use the Latin script which are primarily laid out
horizontally, Asian languages such as Chinese and Japanese can be laid out
@@ -846,8 +909,9 @@
<div class=figure>
<p><img alt="A dictionary definition for ヴィルス
- might write the English word 'virus' rotated 90° clockwise, but stack
- the letters of the initialisms 'RNA' and 'DNA' upright."
+ might write the English word ‘<code
+ class=property>virus</code>’ rotated 90° clockwise, but stack
+ the letters of the initialisms </code>’RNA' and 'DNA' upright."
src=vert-latin-layouts.png></p>
<p class=caption>Examples of Latin in vertical Japanese: Daijirin Viewer
@@ -1466,12 +1530,16 @@
computed value of ‘<a href="#unicode-bidi0"><code
class=property>unicode-bidi</code></a>’. Layout of text is exactly
as for ‘<a href="#rotate-right"><code
- class=css>rotate-right</code></a>’ except that the entire text
- content and baseline table of the element is mirrored: each box of the
- inline is mirrored around a vertical axis such that its content box does
- not move. (However the contents of atomic inlines are not mirrored; only
- their alignment is changed.) Similarly, if a child of the element has a
- ‘<a href="#text-orientation0"><code
+ class=css>rotate-right</code></a>’ except that the text content
+ and baseline table of each of the element's inline boxes is mirrored
+ around a vertical axis along the center of its content box. The
+ positions of text decorations propagated from an ancestor inline
+ (including the block container's root inline) are not mirrored, but any
+ text decorations introduced by the element are positioned using the
+ mirrored baseline table.
+
+ <p>Similarly, if an inline child of the element has a ‘<a
+ href="#text-orientation0"><code
class=property>text-orientation</code></a>’ value other than
‘<a href="#rotate-left"><code
class=css>rotate-left</code></a>’, an analogous transformation is
@@ -2716,6 +2784,15 @@
</dd>
<!---->
+ <dt id=RFC2119>[RFC2119]
+
+ <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key
+ words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet
+ RFC 2119. URL: <a
+ href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+ </dd>
+ <!---->
+
<dt id=SVG11>[SVG11]
<dd>Erik Dahlström; et al. <a
@@ -2767,6 +2844,16 @@
<dt style="display: none"><!-- keeps the doc valid if the DL is empty -->
<!---->
+ <dt id=CSS3COLOR>[CSS3COLOR]
+
+ <dd>Tantek Çelik; Chris Lilley; L. David Baron. <a
+ href="http://www.w3.org/TR/2010/PR-css3-color-20101028"><cite>CSS Color
+ Module Level 3.</cite></a> 28 October 2010. W3C Proposed Recommendation.
+ (Work in progress.) URL: <a
+ href="http://www.w3.org/TR/2010/PR-css3-color-20101028">http://www.w3.org/TR/2010/PR-css3-color-20101028</a>
+ </dd>
+ <!---->
+
<dt id=CSS3PAGE>[CSS3PAGE]
<dd>Melinda Grant; Håkon Wium Lie. <a
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -d -r1.93 -r1.94
--- Overview.src.html 25 Mar 2011 08:02:08 -0000 1.93
+++ Overview.src.html 25 Mar 2011 22:46:31 -0000 1.94
@@ -148,6 +148,54 @@
<p class="issue">Point at Intro to Text Orientation section once it's written.</p>
+<h3 id="placement">Module Interactions</h3>
+
+ <p>This module replaces and extends the 'unicode-bidi' and 'direction'
+ features defined in [[!CSS21]] sections 8.6 and 9.10</var>.
+
+<h3 id="conventions">Document Conventions</h3>
+
+ <p>Conformance requirements are expressed with a combination of
+ descriptive assertions and RFC 2119 terminology. The key words “MUST”,
+ “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
+ “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
+ document are to be interpreted as described in RFC 2119.
+ However, for readability, these words do not appear in all uppercase
+ letters in this specification.
+
+ <p>All of the text of this specification is normative except sections
+ explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
+
+ <p>Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text with <code>class="example"</code>,
+ like this:
+
+ <div class="example">
+ <p>This is an example of an informative example.</p>
+ </div>
+
+ <p>Informative notes begin with the word “Note” and are set apart from the
+ normative text with <code>class="note"</code>, like this:
+
+ <p class="note">Note, this is an informative note.</p>
+
+<h3 id="values">Values</h3>
+
+ <p>This specification follows the
+ <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
+ definition conventions</a> from [[!CSS21]]. Value types not defined in
+ this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
+ Other CSS modules may expand the definitions of these value types: for
+ example [[CSS3COLOR]], when combined with this module, expands the
+ definition of the <color> value type as used in this specification.</p>
+
+ <p>In addition to the property-specific values listed in their definitions,
+ all properties defined in this specification also accept the
+ <a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
+ keyword as their property value. For readability it has not been repeated
+ explicitly.
+
+
<h2 id="text-direction">Inline Direction and Bidirectionality</h2>
<p>While the characters in most scripts are written from left to right,
@@ -325,28 +373,18 @@
<dl>
<dt><strong>normal</strong></dt>
<dd>The element does not open an additional level of embedding with
- respect to the bidirectional algorithm. For inline-level elements,
+ respect to the bidirectional algorithm. For inline elements,
implicit reordering works across element boundaries.</dd>
<dt><strong>embed</strong></dt>
- <dd>If the element is inline-level, this value
- opens an additional level of embedding with respect to the
- bidirectional algorithm. The direction of this embedding level is
- given by the 'direction'
+ <dd>If the element is inline, this value opens an additional level
+ of embedding with respect to the bidirectional algorithm.
+ The direction of this embedding level is given by the 'direction'
property. Inside the element, reordering is done implicitly. This
- corresponds to adding a LRE (U+202A; for 'direction: ltr') or RLE
- (U+202B; for 'direction: rtl') at the start of the element and a PDF
- (U+202C) at the end of the element.</dd>
- <dt><strong>bidi-override</strong></dt>
- <dd>For inline-level elements this creates an override.
- For block-level, table-cell, table-caption, or inline-block elements
- this creates an override for inline-level descendants not within
- another block-level, table-cell, table-caption, or inline-block
- element. This means that inside the element, reordering is strictly in sequence
- according to the <span class="propinst-direction">'direction'</span>
- property; the implicit part of the bidirectional algorithm is
- ignored. This corresponds to adding a LRO (U+202D; for 'direction:
- ltr') or RLO (U+202E; for 'direction: rtl') at the start of the
- element and a PDF (U+202C) at the end of the element.</dd>
+ corresponds to adding a LRE (U+202A), for 'direction: ltr', or RLE
+ (U+202B), for 'direction: rtl', at the start of the element and a PDF
+ (U+202C) at the end of the element.
+ <span class="note">This value has no effect on elements that are
+ not inline.</span></dd>
<dt><strong>isolate</strong></dt>
<dd>For the purposes of the Unicode bidirectional algorithm, the
contents of the element are considered to be inside a separate,
@@ -357,11 +395,20 @@
of the element is treated as an Object Replacement Character.)</dd>
<dt><strong>plaintext</strong></dt>
<dd><p>For the purposes of the Unicode bidirectional algorithm, the
- base directionality of each "paragraph" for which the element
+ base directionality of each bidi paragraph for which the element
forms the containing block is determined not by the element's
computed 'direction' as usual, but by following rules P2
and P3 of the Unicode bidirectional algorithm. Note this value
has no effect on inline elements.
+ <dt><strong>bidi-override</strong></dt>
+ <dd>For inline elements this creates an override. For block-container
+ elements this creates an override for inline-level descendants not
+ within another block container element. This means that inside the
+ element, reordering is strictly in sequence according to the
+ 'direction' property; the implicit part of the bidirectional algorithm
+ is ignored. This corresponds to adding a LRO (U+202D), for ''direction:
+ ltr'', or RLO (U+202E), for ''direction: rtl'', at the start of the
+ element and a PDF (U+202C) at the end of the element.</dd>
</dl>
<p>The final order of characters within in each bidi paragraph is the
@@ -525,7 +572,7 @@
<h2 id="vertical-intro">
Introduction to Vertical Text</h2>
- <p>In addition to extensions to CSS2.1's support for bidirectional text,
+ <p>In addition to extensions to CSS2.1's support for bidirectional text,
this module introduces the rules and properties needed to support vertical
text layout in CSS.
@@ -1066,12 +1113,14 @@
<p>If set on a non-replaced inline whose parent is not ''rotate-left'',
this forces ''isolate'' to be added to the computed value of 'unicode-bidi'.
Layout of text is exactly as for ''rotate-right'' except that the
- entire text content and baseline table of the element is mirrored:
- each box of the inline is mirrored around a vertical axis such that
- its content box does not move. (However the contents of atomic
- inlines are not mirrored; only their alignment is changed.)
- Similarly, if a child of the element has a 'text-orientation' value
- other than ''rotate-left'', an analogous transformation is applied.
+ text content and baseline table of each of the element's inline boxes
+ is mirrored around a vertical axis along the center of its content box.
+ The positions of text decorations propagated from an ancestor inline
+ (including the block container's root inline) are not mirrored, but any
+ text decorations introduced by the element are positioned using the
+ mirrored baseline table.
+ <p>Similarly, if an inline child of the element has a 'text-orientation'
+ value other than ''rotate-left'', an analogous transformation is applied.
<dt><dfn>rotate-normal</dfn></dt>
<dd><p>This value is equivalent to ''rotate-right'' in ''vertical-rl''
writing mode and equivalent to ''rotate-left'' in ''vertical-lr''
Received on Friday, 25 March 2011 22:46:36 UTC