W3C home > Mailing lists > Public > public-css-commits@w3.org > January 2012

csswg/css3-text Overview.html,1.201,1.202 Overview.src.html,1.299,1.300

From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 10 Jan 2012 01:27:24 +0000
To: public-css-commits@w3.org
Message-Id: <E1RkQUm-0006c2-9p@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-text
In directory hutz:/tmp/cvs-serv25404

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Attempt to capture roc's line breaking control scoping rules

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.html,v
retrieving revision 1.201
retrieving revision 1.202
diff -u -d -r1.201 -r1.202
--- Overview.html	7 Jan 2012 01:20:41 -0000	1.201
+++ Overview.html	10 Jan 2012 01:27:21 -0000	1.202
@@ -29,14 +29,15 @@
 
    <h1>CSS Text Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 7 January 2012</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 10 January
+    2012</h2>
 
    <dl>
     <dt>This version:
 
-    <dd><a href="http://dev.w3.org/csswg/css3-text/">$Date: 2012/01/06
-     22:59:32 $ (CVS $Revision$)</a> <!--
-      <dd><a href="http://www.w3.org/TR/2012/WD-css3-text-20120107/">http://www.w3.org/TR/2012/WD-css3-text-20120107/</a></dd>
+    <dd><a href="http://dev.w3.org/csswg/css3-text/">$Date: 2012/01/07
+     01:20:41 $ (CVS $Revision$)</a> <!--
+      <dd><a href="http://www.w3.org/TR/2012/WD-css3-text-20120110/">http://www.w3.org/TR/2012/WD-css3-text-20120110/</a></dd>
     -->
      
 
@@ -258,9 +259,8 @@
       Settings: the &lsquo;<code class=property>text-wrap</code>&rsquo;
       property</a>
       <ul class=toc>
-       <li><a href="#example-avoid"><span class=secno>6.1.1. </span> Example
-        of using &lsquo;<code class=css>text-wrap: avoid</code>&rsquo; in
-        presenting a footer</a>
+       <li><a href="#example-avoid"><span class=secno>6.1.1. </span>
+        Phrase-controlled Breaking</a>
       </ul>
 
      <li><a href="#overflow-wrap"><span class=secno>6.2. </span> Emergency
@@ -1183,7 +1183,16 @@
    the typesetting style.
 
   <p>CSS does not fully define where line breaking opportunities occur,
-   however some controls are provided to distinguish common variations.
+   however some controls are provided to distinguish common variations. For
+   breaking opportunities created by characters that disappear at the line
+   break (i.e. spaces), properties on the element containing that character
+   control the line breaking at that opportunity. For breaking opportunities
+   defined by the boundary between two characters, the properties on the
+   element containing the boundary control breaking.
+   <!-- http://lists.w3.org/Archives/Public/www-style/2008Dec/0043.html -->
+   <span class=issue>What about Zs outside of U+0020?</span> For break
+   opportunities given by the first or last character of a box, the break
+   occurs immediately before/after the box rather than breaking the box.
 
   <p class=note>Further information on line breaking conventions can be found
    in <a href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> and <a
@@ -1198,10 +1207,6 @@
   <p class=issue>Any guidance for appropriate references here would be much
    appreciated.
 
-  <p>Floated and absolutely-positioned elements do not introduce a line
-   breaking opportunity. The line breaking behavior of a replaced element is
-   equivalent to that of the Object Replacement Character (U+FFFC).
-
   <p class=issue>It is not clear whether this section handles Southeast Asian
    scripts well. Additionally, some guidance should be provided on how to
    break or not break Southeast Asian in the absence of a dictionary. (See
@@ -1209,6 +1214,10 @@
    href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">notes
    on Thai</a>.)
 
+  <p>Floated and absolutely-positioned elements do not introduce a line
+   breaking opportunity. The line breaking behavior of a replaced element is
+   equivalent to that of the Object Replacement Character (U+FFFC).
+
   <h3 id=line-break><span class=secno>4.1. </span> Line Breaking Strictness:
    the &lsquo;<a href="#line-break0"><code
    class=property>line-break</code></a>&rsquo; property</h3>
@@ -1688,13 +1697,13 @@
    narrow measures.</p>
   <!-- add a sample prioritization algorithm -->
 
-  <h4 id=example-avoid><span class=secno>6.1.1. </span> Example of using
-   &lsquo;<code class=css>text-wrap: avoid</code>&rsquo; in presenting a
-   footer</h4>
+  <h4 id=example-avoid><span class=secno>6.1.1. </span> Phrase-controlled
+   Breaking</h4>
 
   <div class=example>
-   <p>The priority of breakpoints can be set to reflect the intended grouping
-    of text.</p>
+   <p>Using &lsquo;<code class=css>text-wrap: avoid</code>&rsquo;, the
+    priority of breakpoints can be set to reflect the intended grouping of
+    text.</p>
 
    <p>Given the rules</p>
 

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.src.html,v
retrieving revision 1.299
retrieving revision 1.300
diff -u -d -r1.299 -r1.300
--- Overview.src.html	7 Jan 2012 01:20:41 -0000	1.299
+++ Overview.src.html	10 Jan 2012 01:27:22 -0000	1.300
@@ -763,6 +763,17 @@
 
   <p>CSS does not fully define where line breaking opportunities occur,
     however some controls are provided to distinguish common variations.
+    For breaking opportunities created by characters that disappear at the
+    line break (i.e. spaces), properties on the element containing that
+    character control the line breaking at that opportunity.
+    For breaking opportunities defined by the boundary between two characters,
+    the properties on the element containing the boundary control breaking.
+    <!-- http://lists.w3.org/Archives/Public/www-style/2008Dec/0043.html -->
+    <span class="issue">What about Zs outside of U+0020?</span>
+    For break opportunities given by the first or last character of a
+    box, the break occurs immediately before/after the box rather than
+    breaking the box.
+
 
   <p class="note">Further information on line breaking conventions can be
       found in
@@ -776,15 +787,15 @@
   <p class="issue">Any guidance for appropriate references here would be
     much appreciated.</p>
 
-  <p>Floated and absolutely-positioned elements do not introduce a line
-    breaking opportunity. The line breaking behavior of a replaced element
-    is equivalent to that of the Object Replacement Character (U+FFFC).</p>
-
   <p class="issue">It is not clear whether this section handles Southeast Asian
     scripts well. Additionally, some guidance should be provided on how to
     break or not break Southeast Asian in the absence of a dictionary.
     (See e.g. <a href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">notes on Thai</a>.)</p>
 
+  <p>Floated and absolutely-positioned elements do not introduce a line
+    breaking opportunity. The line breaking behavior of a replaced element
+    is equivalent to that of the Object Replacement Character (U+FFFC).
+
   <h3 id="line-break">
     Line Breaking Strictness: the 'line-break' property</h3>
 
@@ -1166,11 +1177,11 @@
     <!-- add a sample prioritization algorithm -->
 
 <h4 id="example-avoid">
-Example of using 'text-wrap: avoid' in presenting a footer</h4>
+Phrase-controlled Breaking</h4>
 
     <div class="example">
-      <p>The priority of breakpoints can be set to reflect the intended
-        grouping of text.</p>
+      <p>Using ''text-wrap: avoid'', the priority of breakpoints can be set
+        to reflect the intended grouping of text.</p>
 
       <p>Given the rules</p>
       <pre>
Received on Tuesday, 10 January 2012 01:27:26 UTC

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