csswg/css3-text Overview.html,1.49,1.50 Overview.src.html,1.144,1.145

Update of /sources/public/csswg/css3-text
In directory hutz:/tmp/cvs-serv1352

Modified Files:
	Overview.html Overview.src.html 
Log Message:
mark @hyphenate-resource as issue

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- Overview.html	9 Feb 2011 09:18:59 -0000	1.49
+++ Overview.html	9 Feb 2011 17:54:16 -0000	1.50
@@ -90,7 +90,7 @@
     <dt>This version:
 
     <dd><a href="http://dev.w3.org/csswg/css3-text/Overview.html">$Date:
-     2011/02/09 09:07:55 $ (CVS $Revision$)</a> <!--<dd><a
+     2011/02/09 09:19:00 $ (CVS $Revision$)</a> <!--<dd><a
       href="http://www.w3.org/TR/2010/WD-css3-text-20101005/">http://www.w3.org/TR/2010/WD-css3-text-20101005/</a></dd> -->
      
 
@@ -306,9 +306,6 @@
        <li><a href="#the-hyphenate-resource"><span class=secno>6.5.2.
         </span>The &lsquo;<code
         class=property>hyphenate-resource</code>&rsquo; property</a>
-
-       <li><a href="#hyphenation-issue"><span class=secno>6.5.3.
-        </span>Hyphenation Resource Issue</a>
       </ul>
     </ul>
 
@@ -1211,6 +1208,11 @@
   <p class=issue>Any guidance for appropriate references here would be much
    appreciated.
 
+  <p class=issue>Information on line-breaking in the absence of dictionaries:
+   <a
+   href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">for
+   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 a Latin character.
@@ -1872,45 +1874,99 @@
   <h3 id=hyphenation-resource><span class=secno>6.5. </span> Hyphenation
    Resources</h3>
 
-  <h4 id=at-hyphenate-resource><span class=secno>6.5.1. </span>the &lsquo;<a
-   href="#hyphenate-resource"><code
-   class=css>@hyphenate-resource</code></a>&rsquo; rule</h4>
+  <div class=issue>
+   <p>This &lsquo;<a href="#hyphenate-resource"><code
+    class=css>@hyphenate-resource</code></a>&rsquo; property is a proposal
+    that would replace the &lsquo;<a href="#hyphenate-resource"><code
+    class=property>hyphenate-resource</code></a>&rsquo; property.
 
-  <p>The &lsquo;<a href="#hyphenate-resource"><code
-   class=css>@hyphenate-resource</code></a>&rsquo; <a
-   href="http://www.w3.org/TR/CSS21/syndata.html#at-rules">at-rule</a> allows
-   the author to specify hyphenation resources that the UA may use to help it
-   hyphenate text correctly.
+   <dl>
+    <dt>advantages of &lsquo;<a href="#hyphenate-resource"><code
+     class=css>@hyphenate-resource</code></a>&rsquo;
 
-  <p>The &lsquo;<a href="#hyphenate-resource"><code
-   class=css>@hyphenate-resource</code></a>&rsquo; rule consists of the
-   &lsquo;<a href="#hyphenate-resource"><code
-   class=css>@hyphenate-resource</code></a>&rsquo; at-keyword followed by a
-   hyphenation mapping declaration block, which has the same syntax as a
-   declaration block, except that the properties are language codes and the
-   property values are comma-separated lists of &lt;url&gt; component values
-   indicating the location of author-suggested hyphenation resources ordered
-   from most to least preferred. The keyword value &lsquo;<code
-   class=css>local</code>&rsquo; may be used in place of one of the
-   &lt;url&gt; values to suggest the use of a local (UA-provided) hyphenation
-   resource. If the &lsquo;<code class=css>local</code>&rsquo; value is
-   missing, it is assumed to be the first (most-preferred) resource in the
-   list.
+    <dd>
+     <ul>
+      <li>Minimal data storage (set per-language, not per-element).
 
-  <p>The hyphenation resource list that applies to the text in an element is
-   the one given by the last hyphenation mapping declaration whose language
-   code matches the language of the element. Language code matching must be
-   performed using RFC4647 [[!RFC4647]] <span class=issue>explain exactly
-   how</span>.
+      <li>Requires language-tagging, which also enables the correct use of
+       local dictionaries (and can also trigger other typographic
+       improvements).
 
-  <p class=note>Since the last matching declaration takes effect, authors
-   should list the most general mapping first, and the most specific last.
-   Note also that declarations are not concatenated, so if multiple
-   dictionaries are needed, they must be listed completely in each
-   declaration.
+      <li>Can use RFC4647 language-mapping, which is more intelligent than
+       :lang()'s prefix-matching. (Could also argue that :lang() should use
+       RFC4647.)
+     </ul>
 
-  <div class=example>
-   <pre>
+    <dt>disadvantages of &lsquo;<a href="#hyphenate-resource"><code
+     class=css>@hyphenate-resource</code></a>&rsquo;
+
+    <dd>
+     <ul>
+      <li>Requires language-tagging; cannot select on any other criteria.
+       Variations in hyphenation rules within the same language in a given
+       document will require use of subtags.
+     </ul>
+
+    <dt>advantages of &lsquo;<a href="#hyphenate-resource"><code
+     class=property>hyphenate-resource</code></a>&rsquo;
+
+    <dd>
+     <ul>
+      <li>Can use any selector, not just language-mapping.
+
+      <li>Implemented in Prince.
+     </ul>
+
+    <dt>disadvantages of &lsquo;<a href="#hyphenate-resource"><code
+     class=property>hyphenate-resource</code></a>&rsquo;
+
+    <dd>
+     <ul>
+      <li>Requires per-element data storage.
+     </ul>
+   </dl>
+
+   <p>Feedback on this issue is requested.</p>
+
+   <h4 id=at-hyphenate-resource><span class=secno>6.5.1. </span>the &lsquo;<a
+    href="#hyphenate-resource"><code
+    class=css>@hyphenate-resource</code></a>&rsquo; rule</h4>
+
+   <p>The &lsquo;<a href="#hyphenate-resource"><code
+    class=css>@hyphenate-resource</code></a>&rsquo; <a
+    href="http://www.w3.org/TR/CSS21/syndata.html#at-rules">at-rule</a>
+    allows the author to specify hyphenation resources that the UA may use to
+    help it hyphenate text correctly.
+
+   <p>The &lsquo;<a href="#hyphenate-resource"><code
+    class=css>@hyphenate-resource</code></a>&rsquo; rule consists of the
+    &lsquo;<a href="#hyphenate-resource"><code
+    class=css>@hyphenate-resource</code></a>&rsquo; at-keyword followed by a
+    hyphenation mapping declaration block, which has the same syntax as a
+    declaration block, except that the properties are language codes and the
+    property values are comma-separated lists of &lt;url&gt; component values
+    indicating the location of author-suggested hyphenation resources ordered
+    from most to least preferred. The keyword value &lsquo;<code
+    class=css>local</code>&rsquo; may be used in place of one of the
+    &lt;url&gt; values to suggest the use of a local (UA-provided)
+    hyphenation resource. If the &lsquo;<code class=css>local</code>&rsquo;
+    value is missing, it is assumed to be the first (most-preferred) resource
+    in the list.
+
+   <p>The hyphenation resource list that applies to the text in an element is
+    the one given by the last hyphenation mapping declaration whose language
+    code matches the language of the element. Language code matching must be
+    performed using RFC4647 [[!RFC4647]] <span class=issue>explain exactly
+    how</span>.</p>
+
+   <p class=note>Since the last matching declaration takes effect, authors
+    should list the most general mapping first, and the most specific last.
+    Note also that declarations are not concatenated, so if multiple
+    dictionaries are needed, they must be listed completely in each
+    declaration.</p>
+
+   <div class=example>
+    <pre>
 <!-- -->@hyphenate-resource {
 <!-- -->  /* English */
 <!-- -->  en:    url(en-GB.hy);
@@ -1922,19 +1978,21 @@
 <!-- -->}
     </pre>
 
-   <p>In the example above, the &lsquo;<code
-    class=css>en-x-hixie</code>&rsquo; rule is used for both &lsquo;<code
-    class=css>en-x-hixie</code>&rsquo; and &lsquo;<code
-    class=css>en-GB-x-hixie</code>&rsquo;. It is not used for &lsquo;<code
-    class=css>en-US-x-hixie</code>&rsquo; because the &lsquo;<code
-    class=css>en-US-x-hixie</code>&rsquo; rule is given last. If the order
-    were reversed, the &lsquo;<code class=css>en-US-x-hixie</code>&rsquo;
-    rule would never be used.
-  </div>
+    <p>In the example above, the &lsquo;<code
+     class=css>en-x-hixie</code>&rsquo; rule is used for both &lsquo;<code
+     class=css>en-x-hixie</code>&rsquo; and &lsquo;<code
+     class=css>en-GB-x-hixie</code>&rsquo;. It is not used for &lsquo;<code
+     class=css>en-US-x-hixie</code>&rsquo; because the &lsquo;<code
+     class=css>en-US-x-hixie</code>&rsquo; rule is given last. If the order
+     were reversed, the &lsquo;<code class=css>en-US-x-hixie</code>&rsquo;
+     rule would never be used.
+   </div>
 
-  <p class=issue>Use a format specifier, like @font-face? What is the format?
+   <p class=issue>Use a format specifier, like @font-face? What is the
+    format?</p>
 
-  <p>UAs are not required to support this at-rule.
+   <p>UAs are not required to support this at-rule.</p>
+  </div>
 
   <h4 id=the-hyphenate-resource><span class=secno>6.5.2. </span>The &lsquo;<a
    href="#hyphenate-resource"><code
@@ -2005,64 +2063,7 @@
 
   <p>UAs are not required to support this property.
 
-  <h4 id=hyphenation-issue><span class=secno>6.5.3. </span>Hyphenation
-   Resource Issue</h4>
-
-  <div class=issue>
-   <p>&lsquo;<a href="#hyphenate-resource"><code
-    class=property>hyphenate-resource</code></a>&rsquo; and &lsquo;<a
-    href="#hyphenate-resource"><code
-    class=css>@hyphenate-resource</code></a>&rsquo; are both proposed to
-    solve the same problem; only one is needed.</p>
-
-   <dl>
-    <dt>advantages of &lsquo;<a href="#hyphenate-resource"><code
-     class=css>@hyphenate-resource</code></a>&rsquo;
-
-    <dd>
-     <ul>
-      <li>Minimal data storage (set per-language, not per-element).
-
-      <li>Requires language-tagging, which also enables the correct use of
-       local dictionaries (and can also trigger other typographic
-       improvements).
-
-      <li>Can use RFC4647 language-mapping, which is more intelligent than
-       :lang()'s prefix-matching. (Could also argue that :lang() should use
-       RFC4647.)
-     </ul>
-
-    <dt>disadvantages of &lsquo;<a href="#hyphenate-resource"><code
-     class=css>@hyphenate-resource</code></a>&rsquo;
-
-    <dd>
-     <ul>
-      <li>Requires language-tagging; cannot select on any other criteria.
-       Variations in hyphenation rules within the same language in a given
-       document will require use of subtags.
-     </ul>
-
-    <dt>advantages of &lsquo;<a href="#hyphenate-resource"><code
-     class=property>hyphenate-resource</code></a>&rsquo;
-
-    <dd>
-     <ul>
-      <li>Can use any selector, not just language-mapping.
-
-      <li>Implemented in Prince.
-     </ul>
-
-    <dt>disadvantages of &lsquo;<a href="#hyphenate-resource"><code
-     class=property>hyphenate-resource</code></a>&rsquo;
-
-    <dd>
-     <ul>
-      <li>Requires per-element data storage.
-     </ul>
-   </dl>
-
-   <p>Feedback on this issue is requested.</p>
-  </div>
+  <p class=issue>Use a format specifier, like @font-face? What is the format?
 
   <h2 id=wrapping><span class=secno>7. </span> Text Wrapping</h2>
 

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.src.html,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -d -r1.144 -r1.145
--- Overview.src.html	9 Feb 2011 09:19:00 -0000	1.144
+++ Overview.src.html	9 Feb 2011 17:54:16 -0000	1.145
@@ -789,6 +789,9 @@
   <p class="issue">Any guidance for appropriate references here would be
     much appreciated.</p>
 
+  <p class="issue">Information on line-breaking in the absence of dictionaries:
+    <a href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">for 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 a Latin character.</p>
@@ -1271,6 +1274,42 @@
 
   <h3 id="hyphenation-resource">
     Hyphenation Resources</h3>
+    
+<div class="issue">
+
+  <p>This ''@hyphenate-resource'' property is a proposal that would replace
+    the 'hyphenate-resource' property.
+
+  <dl>
+    <dt>advantages of ''@hyphenate-resource''</dt>
+    <dd><ul>
+      <li>Minimal data storage (set per-language, not per-element).
+      <li>Requires language-tagging, which also enables the correct use
+        of local dictionaries (and can also trigger other typographic
+        improvements).
+      <li>Can use RFC4647 language-mapping, which is more intelligent
+        than :lang()'s prefix-matching. (Could also argue that :lang()
+        should use RFC4647.)
+    </ul></dd>
+    <dt>disadvantages of ''@hyphenate-resource''</dt>
+    <dd><ul>
+      <li>Requires language-tagging; cannot select on any other criteria.
+        Variations in hyphenation rules within the same language in a given
+        document will require use of subtags.
+    </ul></dd>
+    <dt>advantages of 'hyphenate-resource'</dt>
+    <dd><ul>
+      <li>Can use any selector, not just language-mapping.
+      <li>Implemented in Prince.
+    </ul></dd>
+    <dt>disadvantages of 'hyphenate-resource'</dt>
+    <dd><ul>
+      <li>Requires per-element data storage.
+    </ul></dd>
+  </dl>
+  
+  <p>Feedback on this issue is requested.</p>
+
   <h4 id="at-hyphenate-resource">the ''@hyphenate-resource'' rule</h3>
 
   <p>The ''@hyphenate-resource'' <a href="http://www.w3.org/TR/CSS21/syndata.html#at-rules">at-rule</a>
@@ -1323,6 +1362,7 @@
   <p class="issue">Use a format specifier, like @font-face? What is the format?</p>
 
   <p>UAs are not required to support this at-rule.</p>
+</div>
 
   <h4 id="the-hyphenate-resource">The 'hyphenate-resource' property</h4>
 
@@ -1373,42 +1413,7 @@
 
     <p>UAs are not required to support this property.</p>
     
-  <h4 id="hyphenation-issue">Hyphenation Resource Issue</h4>
-    
-    <div class="issue">
-      <p>'hyphenate-resource' and ''@hyphenate-resource'' are both proposed
-        to solve the same problem; only one is needed.</p>
-
-      <dl>
-        <dt>advantages of ''@hyphenate-resource''</dt>
-        <dd><ul>
-          <li>Minimal data storage (set per-language, not per-element).
-          <li>Requires language-tagging, which also enables the correct use
-            of local dictionaries (and can also trigger other typographic
-            improvements).
-          <li>Can use RFC4647 language-mapping, which is more intelligent
-            than :lang()'s prefix-matching. (Could also argue that :lang()
-            should use RFC4647.)
-        </ul></dd>
-        <dt>disadvantages of ''@hyphenate-resource''</dt>
-        <dd><ul>
-          <li>Requires language-tagging; cannot select on any other criteria.
-            Variations in hyphenation rules within the same language in a given
-            document will require use of subtags.
-        </ul></dd>
-        <dt>advantages of 'hyphenate-resource'</dt>
-        <dd><ul>
-          <li>Can use any selector, not just language-mapping.
-          <li>Implemented in Prince.
-        </ul></dd>
-        <dt>disadvantages of 'hyphenate-resource'</dt>
-        <dd><ul>
-          <li>Requires per-element data storage.
-        </ul></dd>
-      </dl>
-      
-      <p>Feedback on this issue is requested.</p>
-    </div>
+    <p class="issue">Use a format specifier, like @font-face? What is the format?</p>
 
 <h2 id="wrapping">
   Text Wrapping</h2>

Received on Wednesday, 9 February 2011 17:54:20 UTC