- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 24 Feb 2011 07:42:13 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv23335
Modified Files:
Overview.html Overview.src.html
Log Message:
Copy over updated CSS2.1 wording. Try to address <http://lists.w3.org/Archives/Public/www-style/2010Dec/0333.html>. (This is a first pass; it probably requires some editorial cleanup later.)
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -d -r1.80 -r1.81
--- Overview.html 24 Feb 2011 06:39:39 -0000 1.80
+++ Overview.html 24 Feb 2011 07:42:10 -0000 1.81
@@ -398,19 +398,28 @@
bidirectional algorithm to every sequence of inline boxes uninterrupted by
a forced (<a
href="http://www.unicode.org/reports/tr9/#Bidirectional_Character_Types">bidi
- class B</a>) line break or block boundary. This sequence forms the
- "paragraph" unit in the bidirectional algorithm. The paragraph embedding
- level is set according to the value of the ‘<a
+ class B</a>) line break or block boundary. This sequence forms the <dfn
+ id=paragraph>paragraph</dfn> unit in the bidirectional algorithm.
+
+ <p>Except when the ‘<code class=css>plaintext</code>’ value of
+ ‘<a href="#unicode-bidi0"><code
+ class=property>unicode-bidi</code></a>’ is in effect, the paragraph
+ embedding level is set according to the value of the ‘<a
href="#direction0"><code class=property>direction</code></a>’
- property of the containing block rather than by the heuristic given in
- steps P2 and P3 of the Unicode algorithm.
+ property of the paragraph's element rather than by the heuristic given in
+ steps P2 and P3 of the Unicode algorithm. The paragraph's element is
+ usually the containing block, but in the case of a paragraph contained by
+ bidi <a href="#isolate">isolation</a> it is the isolating inline element
+ instead.
<p>Because the base directionality of a text depends on the structure and
- semantics of the document, these properties should in most cases be used
- only to map bidi information in the markup to its corresponding CSS
- styles. If a document language provides markup features to control bidi,
- authors and users should use those features and not specify CSS rules to
- override them.
+ semantics of the document, the ‘<a href="#direction0"><code
+ class=property>direction</code></a>’ and ‘<a
+ href="#unicode-bidi0"><code class=property>unicode-bidi</code></a>’
+ properties should in most cases be used only to map bidi information in
+ the markup to its corresponding CSS styles. If a document language
+ provides markup features to control bidi, authors and users should use
+ those features and not specify CSS rules to override them.
<p>The HTML 4 specification (<a href="#HTML401"
rel=biblioentry>[HTML401]<!--{{HTML401}}--></a>, section 8.2) defines
@@ -615,28 +624,33 @@
<dd>
<p>For the purposes of the Unicode bidirectional algorithm, the base
- directionality of each "paragraph" for which the element is the
- containing block element is determined not by the element's computed
- ‘<a href="#direction0"><code
- class=property>direction</code></a>’ as usual, but by following
- rules P1, P2, and P3 of the Unicode bidirectional algorithm. Note this
- value has no effect on inline elements.
+ directionality of each "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.
</dl>
- <p>The final order of characters in each block-level element is the same as
- if the bidi control codes had been added as described above, markup had
+ <p>The final order of characters within in each bidi paragraph is the same
+ as if the bidi control codes had been added as described above, markup had
been stripped, and the resulting character sequence had been passed to an
implementation of the Unicode bidirectional algorithm for plain text that
- produced the same line-breaks as the styled text. In this process,
- non-textual entities such as images are treated as neutral characters,
- unless their <span class=propinst-unicode-bidi>‘<a
- href="#unicode-bidi0"><code
- class=property>unicode-bidi</code></a>’</span> property has a value
- other than ‘<code class=property>normal</code>’, in which case
- they are treated as strong characters in the <span
- class=propinst-direction>‘<a href="#direction0"><code
- class=property>direction</code></a>’</span> specified for the
- element.
+ produced the same line-breaks as the styled text. If an inline element is
+ broken around a bidi paragraph boundary (e.g. if split by a block or
+ forced paragraph break), then the bidi control codes corresponding to the
+ end of the element are added before the interruption and the codes
+ corresponding to the start of the element are added after it. (In other
+ words, any embedding levels or overrides started by the element are closed
+ at the paragraph break and reopened on the other side of it.)
+
+ <p>In this process, replaced elements with ‘<code class=css>display:
+ inline</code>’ are treated as neutral characters, unless their
+ ‘<a href="#unicode-bidi0"><code
+ class=property>unicode-bidi</code></a>’ property has a value other
+ than ‘<code class=property>normal</code>’, in which case they
+ are treated as strong characters in the ‘<a href="#direction0"><code
+ class=property>direction</code></a>’ specified for the element. All
+ other atomic inline-level boxes are treated as neutral characters always.
<p>Please note that in order to be able to flow inline boxes in a uniform
direction (either entirely left-to-right or entirely right-to-left), more
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -d -r1.84 -r1.85
--- Overview.src.html 24 Feb 2011 06:39:39 -0000 1.84
+++ Overview.src.html 24 Feb 2011 07:42:10 -0000 1.85
@@ -174,14 +174,20 @@
<p>User agents that support bidirectional text must apply the Unicode
bidirectional algorithm to every sequence of inline boxes uninterrupted
by a forced (<a href="http://www.unicode.org/reports/tr9/#Bidirectional_Character_Types">bidi class B</a>)
- line break or block boundary. This sequence forms the "paragraph" unit
- in the bidirectional algorithm. The paragraph embedding level is set
- according to the value of the 'direction' property of the containing
- block rather than by the heuristic given in steps P2 and P3 of the Unicode
- algorithm.</p>
+ line break or block boundary. This sequence forms the <dfn>paragraph</dfn>
+ unit in the bidirectional algorithm.
+
+ <p>Except when the ''plaintext'' value of 'unicode-bidi' is in effect,
+ the paragraph embedding level is set according to the value of the
+ 'direction' property of the paragraph's element rather than by the
+ heuristic given in steps P2 and P3 of the Unicode algorithm. The
+ paragraph's element is usually the containing block, but in the case
+ of a paragraph contained by bidi <a href="#isolate">isolation</a> it
+ is the isolating inline element instead.
<p>Because the base directionality of a text depends on the structure and
- semantics of the document, these properties should in most cases be
+ semantics of the document, the 'direction' and 'unicode-bidi' properties
+ should in most cases be
used only to map bidi information in the markup to its corresponding
CSS styles. If a document language provides markup features to control
bidi, authors and users should use those features and not specify CSS
@@ -347,23 +353,31 @@
<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
- is the containing block element is determined not by the element's
- computed 'direction' as usual, but by following rules P1, P2,
+ 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.
</dl>
- <p>The final order of characters in each block-level element is the
+ <p>The final order of characters within in each bidi paragraph is the
same as if the bidi control codes had been added as described above,
markup had been stripped, and the resulting character sequence had
been passed to an implementation of the Unicode bidirectional
algorithm for plain text that produced the same line-breaks as the
- styled text. In this process, non-textual entities such as images are
- treated as neutral characters, unless their <span
- class="propinst-unicode-bidi">'unicode-bidi'</span> property has a
+ styled text. If an inline element is broken around a bidi paragraph
+ boundary (e.g. if split by a block or forced paragraph break), then
+ the bidi control codes corresponding to the end of the element are
+ added before the interruption and the codes corresponding to the
+ start of the element are added after it. (In other words, any embedding
+ levels or overrides started by the element are closed at the paragraph
+ break and reopened on the other side of it.)
+
+ <p>In this process, replaced elements with 'display: inline' are treated
+ as neutral characters, unless their 'unicode-bidi' property has a
value other than 'normal', in which case they are treated as strong
- characters in the <span class="propinst-direction">'direction'</span>
- specified for the element.</p>
+ characters in the 'direction' specified for the element.
+ All other atomic inline-level boxes are treated as neutral characters
+ always.</p>
<p>Please note that in order to be able to flow inline boxes in a
uniform direction (either entirely left-to-right or entirely
Received on Thursday, 24 February 2011 07:42:14 UTC