- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 03 May 2011 02:20:37 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv1205
Modified Files:
Overview.html Overview.src.html
Log Message:
Address Aharon's editorial suggestions <http://lists.w3.org/Archives/Public/www-style/2011Feb/0729.html>
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- Overview.html 3 May 2011 01:58:28 -0000 1.102
+++ Overview.html 3 May 2011 02:20:35 -0000 1.103
@@ -710,13 +710,7 @@
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. 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.)
+ produced the same line-breaks as the styled text.
<p>In this process, replaced elements with ‘<code class=css>display:
inline</code>’ are treated as neutral characters, unless their
@@ -728,6 +722,14 @@
class=property>direction</code></a>’ specified for the element. All
other atomic inline-level boxes are treated as neutral characters always.
+ <p>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>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
inline boxes (including anonymous inline boxes) may have to be created,
@@ -748,6 +750,9 @@
class=css>unicode-bidi: isolate</code>’ is preferred to keep the
element together in case display is changed to inline (see example below).
+ <h3 id=bidi-example><span class=secno>2.3. </span>Example of Bidirectional
+ Text</h3>
+
<p>The following example shows an XML document with bidirectional text. It
illustrates an important design principle: document language designers
should take bidi into account both in the language proper (elements and
@@ -756,9 +761,6 @@
such rules should not be overridden by other style sheets so that the
document language's bidi behavior is preserved.
- <h3 id=bidi-example><span class=secno>2.3. </span>Example of Bidirectional
- Text</h3>
-
<div class=example>
<p>In this example, lowercase letters stand for inherently left-to-right
characters and uppercase letters represent inherently right-to-left
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -d -r1.106 -r1.107
--- Overview.src.html 3 May 2011 01:58:28 -0000 1.106
+++ Overview.src.html 3 May 2011 02:20:35 -0000 1.107
@@ -419,13 +419,7 @@
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. 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.)
+ styled text.
<p>In this process, replaced elements with 'display: inline' are treated
as neutral characters, unless their 'unicode-bidi' property has a
@@ -434,6 +428,14 @@
All other atomic inline-level boxes are treated as neutral characters
always.</p>
+ <p>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>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 inline boxes (including anonymous inline boxes)
@@ -451,6 +453,8 @@
'unicode-bidi: isolate' is preferred to keep the element together in
case display is changed to inline (see example below).</p>
+<h3 id="bidi-example">Example of Bidirectional Text</h3>
+
<p>The following example shows an XML document with bidirectional
text. It illustrates an important design principle: document language
designers should take bidi into account both in the language proper
@@ -459,8 +463,6 @@
other style rules, and such rules should not be overridden by other
style sheets so that the document language's bidi behavior is preserved.</p>
-<h3 id="bidi-example">Example of Bidirectional Text</h3>
-
<div class="example">
<p>In this example, lowercase letters stand for inherently left-to-right
characters and uppercase letters represent inherently right-to-left
Received on Tuesday, 3 May 2011 02:20:39 UTC