W3C home > Mailing lists > Public > public-css-commits@w3.org > February 2011

csswg/css3-text Overview.html,1.59,1.60 Overview.src.html,1.153,1.154

From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 23 Feb 2011 05:09:20 +0000
To: public-css-commits@w3.org
Message-Id: <E1Ps6yW-000320-5K@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-text
In directory hutz:/tmp/cvs-serv11628

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Editorial edits to white space processing rules, cut out a paragraph that's no longer relevant and update informative summary to match previous substantive edits; also fix a text-justify example

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.html,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -d -r1.59 -r1.60
--- Overview.html	19 Feb 2011 14:54:46 -0000	1.59
+++ Overview.html	23 Feb 2011 05:09:17 -0000	1.60
@@ -83,15 +83,15 @@
 
    <h1>CSS Text Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 19 February
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 23 February
     2011</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a href="http://dev.w3.org/csswg/css3-text/Overview.html">$Date:
-     2011/02/14 11:42:29 $ (CVS $Revision$)</a> <!--
-      <dd><a href="http://www.w3.org/TR/2011/WD-css3-text-20110219/">http://www.w3.org/TR/2011/WD-css3-text-20110219/</a></dd>
+     2011/02/19 14:54:46 $ (CVS $Revision$)</a> <!--
+      <dd><a href="http://www.w3.org/TR/2011/WD-css3-text-20110223/">http://www.w3.org/TR/2011/WD-css3-text-20110223/</a></dd>
     -->
      
 
@@ -366,7 +366,7 @@
       Kerning: the &lsquo;<code class=property>text-trim</code>&rsquo;
       property</a>
 
-     <li><a href="#text-autospace"><span class=secno>9.4. </span> Adding
+     <li><a href="#text-autospace-prop"><span class=secno>9.4. </span> Adding
       space: the &lsquo;<code class=property>text-autospace</code>&rsquo;
       property</a>
     </ul>
@@ -663,7 +663,7 @@
     title="text-transform:fullwidth"><code>fullwidth</code></dfn>
 
    <dd>Puts all characters in fullwidth form. If the character does not have
-    corresponding fullwidth form, it is left as is. This value is typically
+    a corresponding fullwidth form, it is left as is. This value is typically
     used to typeset Latin characters and digits like ideographic characters.
 
    <dt><dfn id=large-kana
@@ -709,21 +709,21 @@
    allows the author to control interpretation of such formatting: to
    preserve or collapse it away when rendering the document.
 
-  <p>Segments in the document source can be separated by a carriage return
-   (U+000D), a linefeed (U+000A) or both (U+000D U+000A), or by some other
-   mechanism that identifies the beginning and end of document segments, such
-   as the SGML RECORD-START and RECORD-END tokens. If no segmentation rules
-   are specified for the document language, each line feed (U+000A), carriage
-   return (U+000D) and CRLF sequence (U+000D U+000A) in the text is
-   considered a segment break. (This default rule also applies to generated
-   content.) In CSS, each such segment break is treated as a single line feed
-   character (U+000A).
-
   <p>White space processing in CSS interprets white space characters for
-   rendering: it has no effect on the underlying document data. In the
-   context of CSS, the document white space set is defined to be any space
-   characters (Unicode value U+0020), tab characters (U+0009), and line feeds
-   (U+000A).
+   rendering: it has no effect on the underlying document data.
+
+  <p>In the context of CSS, the document white space set is defined to be any
+   space characters (Unicode value U+0020), tab characters (U+0009), and line
+   feeds (U+000A).
+
+  <p>However in the document source, segments can be delimited by carriage
+   returns (U+000D), linefeeds (U+000A) or a combination (U+000D U+000A), or
+   by some other mechanism, such as the SGML RECORD-START and RECORD-END
+   tokens. In CSS, each such segment break is treated as a single line feed
+   character (U+000A). If no segmentation rules are specified for the
+   document language, each line feed (U+000A), carriage return (U+000D) and
+   CRLF sequence (U+000D U+000A) in the text is considered a segment break.
+   (This default rule also applies to generated content.)
 
   <p class=note>Note that the document parser may have not only normalized
    segment breaks, but also collapsed other space characters or otherwise
@@ -810,14 +810,14 @@
     title="white-space-collapsing:preserve"><code>preserve</code></dfn>
 
    <dd>This value prevents user agents from collapsing sequences of white
-    space. Segment breaks are preserved as forced line breaks.
+    space. Line feeds are preserved as forced line breaks.
 
    <dt><dfn id=preserve-breaks
     title="white-space-collapsing:preserve-breaks"><code>preserve-breaks</code></dfn>
 
    <dd>This value collapses white space as for &lsquo;<code
-    class=css>collapse</code>&rsquo;, but preserves segment breaks as forced
-    line breaks.
+    class=css>collapse</code>&rsquo;, but preserves line feeds as forced line
+    breaks.
 
    <dt><dfn id=discard
     title="white-space-collapsing:discard"><code>discard</code></dfn>
@@ -829,9 +829,9 @@
     title="white-space-collapsing:trim-inner"><code>trim-inner</code></dfn>
 
    <dd>This value directs UAs to discard all whitespace at the beginning of a
-    block up to and including the last line break before the first
+    block up to and including the last line feed before the first
     non-white-space character in the block as well as to discard all white
-    space at the end of a block starting with the first line break after the
+    space at the end of a block starting with the first line feed after the
     last non-white-space character in the block.
   </dl>
 
@@ -853,10 +853,8 @@
      performing the following steps:</p>
 
     <ol>
-     <li>All spaces and tabs immediately following a line feed character are
-      removed. (This has the effect of discarding all white space at the
-      start of a line but preserving a trailing space if one exists at the
-      end.)
+     <li>All spaces and tabs immediately preceding or following a line feed
+      character are removed.
 
      <li>If <span class=property>&lsquo;<a
       href="#white-space-collapsing0"><code
@@ -917,6 +915,10 @@
     class=property>avoid</code>&rsquo; the UA may visually collapse them.
   </ol>
 
+  <p class=issue>There was a proposal for a &lsquo;<code
+   class=property>tab-size</code>&rsquo; property to control the size of tab
+   stops. Is there implementation interest in this property?
+
   <div class=example>
    <h4 id=egbidiwscollapse><span class=secno>4.2.1. </span> Example of
     bidirectionality with white space collapsing</h4>
@@ -964,16 +966,6 @@
    transformed into a space (U+0020) or removed depending on the script
    context before and after the line break.
 
-  <p>The script context is determined by the Unicode-given script value <a
-   href="#UAX24" rel=biblioentry>[UAX24]<!--{{!UAX24}}--></a> of the first
-   character that side of the line feed. However, characters such as
-   punctuation that belong to the COMMON and INHERITED scripts are ignored in
-   this check; the next character is examined instead. The UA must not
-   examine characters outside the block and may limit its examination to as
-   few as four characters on each side of the line feed. If the check fails
-   to find an acceptable script value (i.e. it has hit the check limits),
-   then the script context is neutral.
-
   <p class=note>Note that the white space processing rules have already
    removed any tabs and spaces after the line feed before these checks take
    place.
@@ -991,7 +983,7 @@
     and after the line feed is F, W, or H (not A), then the line feed is
     removed.
 
-   <li>Otherwise, if &lsquo;<a href="#text-autospace0"><code
+   <li>Otherwise, if &lsquo;<a href="#text-autospace"><code
     class=property>text-autospace</code></a>&rsquo; property is set to add
     extra spaces for the combination of the character before the line feed
     and after, then the line break is removed.
@@ -1009,13 +1001,13 @@
   <ul>
    <li>Consecutive white space collapses into a single space.
 
-   <li>A sequence of line breaks and other white space between two
-    ideographic characters collapses into nothing unless there is a space
-    before the first line break in the sequence.
+   <li>A sequence of newlines and other white space between two ideographic
+    characters collapses into nothing unless there is a space before the
+    first newline in the sequence.
 
-   <li>A zero width space immediately before or anywhere after a line break
-    causes the entire sequence of white space beginning with the line break
-    to collapse into a zero width space.
+   <li>A zero width space within a white space sequence containing a newline
+    causes the entire sequence of white space to collapse into a zero width
+    space.
   </ul>
 
   <h3 id=white-space><span class=secno>4.3. </span> White Space and Text
@@ -3168,14 +3160,14 @@
    behavior is not defined by CSS.
 
   <div class=example>
-   <p>Japanese is one of the languages for which compression is preferred to
-    expansion in applying justification.</p>
-
    <p>3.8 Line Adjustment in <a href="#JLREQ"
     rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> gives an example of a set of
     rules for how a text formatter can justify Japanese text. It describes
     rules for cases where the &lsquo;<a href="#text-justify0"><code
     class=property>text-justify</code></a>&rsquo; property is &lsquo;<code
+    class=css>inter-ideograph</code>&rsquo;. It describes rules for cases
+    where the &lsquo;<a href="#text-justify0"><code
+    class=property>text-justify</code></a>&rsquo; property is &lsquo;<code
     class=css>inter-ideograph</code>&rsquo; and the &lsquo;<a
     href="#text-trim"><code class=property>text-trim</code></a>&rsquo;
     property does not specify &lsquo;<code
@@ -3772,16 +3764,16 @@
     standard convention is often not followed.</p>
   </div>
 
-  <h3 id=text-autospace><span class=secno>9.4. </span> <a
-   name=text-autospace-prop></a> <a name=text-autospace>Adding space: the
-   &lsquo;<code class=property>text-autospace</code>&rsquo; property</a></h3>
+  <h3 id=text-autospace-prop><span class=secno>9.4. </span> Adding space: the
+   &lsquo;<a href="#text-autospace"><code
+   class=property>text-autospace</code></a>&rsquo; property</h3>
 
   <table class=propdef>
    <tbody>
     <tr>
      <th>Name:
 
-     <td><dfn id=text-autospace0>text-autospace</dfn>
+     <td><dfn id=text-autospace>text-autospace</dfn>
 
     <tr>
      <th>Value:
@@ -5397,13 +5389,13 @@
 
    <li>Removed &lsquo;<code class=css>ideograph-space</code>&rsquo; and
     &lsquo;<code class=css>ideograph-parenthesis</code>&rsquo; values of
-    &lsquo;<a href="#text-autospace0"><code
+    &lsquo;<a href="#text-autospace"><code
     class=property>text-autospace</code></a>&rsquo;.
 
    <li>Changed definitions of <a href="#ideographic-letters">ideographic
     letters</a>, <a href="#non-ideographic-letters">non-ideographic
     letters</a>, and <a href="#non-ideographic-numerals">non-ideographic
-    numerals</a> for &lsquo;<a href="#text-autospace0"><code
+    numerals</a> for &lsquo;<a href="#text-autospace"><code
     class=property>text-autospace</code></a>&rsquo;.
 
    <li>Changed values of &lsquo;<a href="#text-emphasis-position0"><code
@@ -5810,7 +5802,7 @@
      <td>visual
 
     <tr valign=baseline>
-     <td><a class=property href="#text-autospace0">text-autospace</a>
+     <td><a class=property href="#text-autospace">text-autospace</a>
 
      <td>none | [ ideograph-numeric || ideograph-alpha || punctuation ]
 
@@ -6405,7 +6397,7 @@
    <li>text-align:&lt;string>, <a href="#ltstringgt"
     title="text-align:&lt;string>"><strong>8.1.</strong></a>
 
-   <li>text-autospace, <a href="#text-autospace0"
+   <li>text-autospace, <a href="#text-autospace"
     title=text-autospace><strong>9.4.</strong></a>
 
    <li>text-autospace:ideograph-alpha, <a href="#ideograph-alpha"

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.src.html,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- Overview.src.html	19 Feb 2011 14:54:46 -0000	1.153
+++ Overview.src.html	23 Feb 2011 05:09:17 -0000	1.154
@@ -350,7 +350,7 @@
         <dd>Puts all characters in lowercase.</dd>
       <dt><dfn title="text-transform:fullwidth"><code>fullwidth</code></dfn></dt>
         <dd>Puts all characters in fullwidth form.
-          If the character does not have corresponding fullwidth form,
+          If the character does not have a corresponding fullwidth form,
           it is left as is.
           This value is typically used to typeset Latin characters and digits
           like ideographic characters.
@@ -392,24 +392,24 @@
     control interpretation of such formatting: to preserve or
     collapse it away when rendering the document.
 
-  <p>Segments in the document source can be separated by a carriage
-    return (U+000D), a linefeed (U+000A) or both (U+000D U+000A),
-    or by some other mechanism that identifies the beginning
-    and end of document segments, such as the SGML RECORD-START
-    and RECORD-END tokens.
-    If no segmentation rules are specified for the document language,
-    each line feed (U+000A), carriage return (U+000D) and CRLF sequence
-    (U+000D U+000A) in the text is considered a segment break. (This
-    default rule also applies to generated content.)
-    In CSS, each such segment break is treated as a single line feed
-    character (U+000A).
-
   <p>White space processing in CSS interprets white space characters
     for rendering: it has no effect on the underlying document data.
-    In the context of CSS, the document white space set is defined
+
+  <p>In the context of CSS, the document white space set is defined
     to be any space characters (Unicode value U+0020), tab characters
     (U+0009), and line feeds (U+000A).
 
+  <p>However in the document source, segments can be delimited by carriage
+    returns (U+000D), linefeeds (U+000A) or a combination (U+000D U+000A),
+    or by some other mechanism, such as the SGML RECORD-START
+    and RECORD-END tokens. In CSS, each such segment break is treated as
+    a single line feed character (U+000A).
+    
+    If no segmentation rules are specified for the document language,
+    each line feed (U+000A), carriage return (U+000D) and CRLF sequence
+    (U+000D U+000A) in the text is considered a segment break. (This
+    default rule also applies to generated content.)
+
   <p class="note">Note that the document parser may have not only normalized
     segment breaks, but also collapsed other space characters or
     otherwise processed white space according to markup rules. Because CSS
@@ -480,18 +480,18 @@
         cases</a>, no character).</dd>
       <dt><dfn title="white-space-collapsing:preserve"><code>preserve</code></dfn></dt>
       <dd>This value prevents user agents from collapsing sequences
-      of white space. Segment breaks are preserved as forced line breaks.</dd>
+      of white space. Line feeds are preserved as forced line breaks.</dd>
       <dt><dfn title="white-space-collapsing:preserve-breaks"><code>preserve-breaks</code></dfn></dt>
       <dd>This value collapses white space as for ''collapse'', but preserves
-        segment breaks as forced line breaks.</dd>
+        line feeds as forced line breaks.</dd>
       <dt><dfn title="white-space-collapsing:discard"><code>discard</code></dfn></dt>
       <dd>This value directs user agents to "discard" all white space in the
         element.
       <dt><dfn title="white-space-collapsing:trim-inner"><code>trim-inner</code></dfn></dt>
       <dd>This value directs UAs to discard all whitespace at the beginning of
-        a block up to and including the last line break before the first
+        a block up to and including the last line feed before the first
         non-white-space character in the block as well as to discard all white
-        space at the end of a block starting with the first line break after
+        space at the end of a block starting with the first line feed after
         the last non-white-space character in the block.</dd>
     </dl>
 
@@ -508,10 +508,8 @@
       are considered <dfn>collapsible</dfn> and are processed by
       performing the following steps:</p>
       <ol>
-        <li>All spaces and tabs immediately following a line feed character
-          are removed. (This has the effect of discarding all white space
-          at the start of a line but preserving a trailing space if one
-          exists at the end.)</li>
+        <li>All spaces and tabs immediately preceding or following a line
+          feed character are removed.</li>
         <li>If <span class="property">'white-space-collapsing'</span> is not
           'preserve-breaks', line feed characters are transformed for
           rendering according to the <a href="#line-break-transform">line
@@ -555,6 +553,9 @@
         the UA may visually collapse them.
     </ol>
 
+    <p class="issue">There was a proposal for a 'tab-size' property to control
+      the size of tab stops. Is there implementation interest in this property?</p>
+
     <div class="example">
     <h4 id="egbidiwscollapse">
       Example of bidirectionality with white space collapsing</h4>
@@ -600,15 +601,6 @@
         either transformed into a space (U+0020) or removed depending on the
         script context before and after the line break.</p>
 
-      <p>The script context is determined by the Unicode-given script value
-        [[!UAX24]] of the first character that side of the line feed. However,
-        characters such as punctuation that belong to the COMMON and INHERITED
-        scripts are ignored in this check; the next character is examined
-        instead. The UA must not examine characters outside the block and may
-        limit its examination to as few as four characters on each side of the
-        line feed. If the check fails to find an acceptable script value
-        (i.e. it has hit the check limits), then the script context is neutral.</p>
-
       <p class="note">Note that the white space processing rules have already
         removed any tabs and spaces after the line feed before these checks
         take place.</p>
@@ -637,13 +629,12 @@
 
       <ul>
         <li>Consecutive white space collapses into a single space.
-        <li>A sequence of line breaks and other white space between
+        <li>A sequence of newlines and other white space between
           two ideographic characters collapses into nothing unless
-          there is a space before the first line break in the sequence.
-        <li>A zero width space immediately before or anywhere after
-          a line break causes the entire sequence of white space
-          beginning with the line break to collapse into a zero width
-          space.
+          there is a space before the first newline in the sequence.
+        <li>A zero width space within a white space sequence containing
+          a newline causes the entire sequence of white space
+          to collapse into a zero width space.
       </ul>
 
   <h3 id="white-space">
@@ -2274,9 +2265,9 @@
       any method. This behavior is not defined by CSS.</p>
 
     <div class="example">
-      <p>Japanese is one of the languages for which compression is preferred to expansion in applying justification.</p>
       <p>3.8 Line Adjustment in [[JLREQ]] gives an example of a set of rules for
         how a text formatter can justify Japanese text.
+        It describes rules for cases where the 'text-justify' property is ''inter-ideograph''.
         It describes rules for cases where the 'text-justify' property is ''inter-ideograph''
         and the 'text-trim' property does not specify ''no-justify''.</p>
       <p>It produces an effect similar to cases where
Received on Wednesday, 23 February 2011 05:09:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:26:01 UTC