Address jdaggett's comments on text-transform

Author: fantasai

css3-text/Overview.html

@@ -83,14 +83,14 @@
 
    <h1>CSS Text Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 9 March 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 10 March 2011</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a href="http://dev.w3.org/csswg/css3-text/Overview.html">$Date:
-     2011/03/07 17:16:19 $ (CVS $Revision$)</a> <!--
-      <dd><a href="http://www.w3.org/TR/2011/WD-css3-text-20110309/">http://www.w3.org/TR/2011/WD-css3-text-20110309/</a></dd>
+     2011/03/09 06:22:25 $ (CVS $Revision$)</a> <!--
+      <dd><a href="http://www.w3.org/TR/2011/WD-css3-text-20110310/">http://www.w3.org/TR/2011/WD-css3-text-20110310/</a></dd>
     -->
 
 
@@ -617,7 +617,7 @@ <h3 id=text-transform><span class=secno>3.1. </span> <a name=caps-prop></a>
      <th>Value:
 
      <td>none | [ [ capitalize | uppercase | lowercase ] || fullwidth ||
-      large-kana ]
+      full-size-kana ]
 
     <tr>
      <th>Initial:
@@ -681,8 +681,8 @@ <h3 id=text-transform><span class=secno>3.1. </span> <a name=caps-prop></a>
     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
-    title="text-transform:large-kana"><code>large-kana</code></dfn>
+   <dt><dfn id=full-size-kana
+    title="text-transform:full-size-kana"><code>full-size-kana</code></dfn>
 
    <dd>Converts all small Kana characters to normal Kana. This value is
     typically used for ruby annotation text, where all small Kana should be
@@ -702,10 +702,6 @@ <h3 id=text-transform><span class=secno>3.1. </span> <a name=caps-prop></a>
    href="#UNICODE" rel=biblioentry>[UNICODE]<!--{{!UNICODE}}--></a> Only
    characters belonging to bicameral scripts are affected.
 
-  <p>The definition of fullwidth and halfwidth forms can be found on the
-   Unicode consortium web site at <a href="#UAX11"
-   rel=biblioentry>[UAX11]<!--{{!UAX11}}--></a>.
-
   <p>The definition of "word" used for &lsquo;<code
    class=css>captilize</code>&rsquo; is UA-dependent; <a href="#UAX29"
    rel=biblioentry>[UAX29]<!--{{UAX29}}--></a> is suggested (but not
@@ -718,6 +714,14 @@ <h3 id=text-transform><span class=secno>3.1. </span> <a name=caps-prop></a>
       past any starting non-letters (as an example of why UAX29 is not ideal) -->
 
 
+  <p>The definition of fullwidth and halfwidth forms can be found on the
+   Unicode consortium web site at <a href="#UAX11"
+   rel=biblioentry>[UAX11]<!--{{!UAX11}}--></a>. <span class=issue>Find
+   equivalency tables at Unicode (or make them).</span>
+
+  <p class=issue>Should all characters be transformed, or only letters (i.e.
+   not symbols, punctuation, or white space)
+
   <p>Text transformation happens after <a href="#white-space-rules">white
    space processing</a>. (This only matters when &lsquo;<code
    class=css>fullwidth</code>&rsquo; transforms U+0020 space characters to
@@ -3663,9 +3667,6 @@ <h3 id=text-trim-prop><span class=secno>9.3. </span> <a
     rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a>.</span>
   </dl>
 
-  <p class=issue>Figure out proper interaction with text-align: end. Does
-   allow-end behavior make sense? Do we want allow-start instead?
-
   <p>In all cases, the UA must trim (kern) the blank half of fullwidth
    opening punctuation if its previous adjacent character is a fullwidth
    opening punctuation, fullwidth middle dot punctuation, fullwidth closing
@@ -6182,7 +6183,7 @@ <h2 class=no-num id=appendix-b-property-index> Appendix B: Property index</h2>
      <td><a class=property href="#text-transform0">text-transform</a>
 
      <td>none | [ [ capitalize | uppercase | lowercase ] || fullwidth ||
-      large-kana ]
+      full-size-kana ]
 
      <td>none
 
@@ -6703,12 +6704,12 @@ <h2 class=no-num id=index>Index</h2>
    <li>text-transform:capitalize, <a href="#capitalize"
     title="text-transform:capitalize"><strong>3.1.</strong></a>
 
+   <li>text-transform:full-size-kana, <a href="#full-size-kana"
+    title="text-transform:full-size-kana"><strong>3.1.</strong></a>
+
    <li>text-transform:fullwidth, <a href="#fullwidth"
     title="text-transform:fullwidth"><strong>3.1.</strong></a>
 
-   <li>text-transform:large-kana, <a href="#large-kana"
-    title="text-transform:large-kana"><strong>3.1.</strong></a>
-
    <li>text-transform:lowercase, <a href="#lowercase"
     title="text-transform:lowercase"><strong>3.1.</strong></a>
 

css3-text/Overview.src.html

@@ -314,7 +314,7 @@ <h3 id="text-transform">
         <tr>
           <th>Value:</th>
           <td>none |
-            [ [ capitalize | uppercase | lowercase ] || fullwidth || large-kana ]
+            [ [ capitalize | uppercase | lowercase ] || fullwidth || full-size-kana ]
           </td>
         </tr>
         <tr>
@@ -363,7 +363,7 @@ <h3 id="text-transform">
           it is left as is.
           This value is typically used to typeset Latin characters and digits
           like ideographic characters.
-      <dt><dfn title="text-transform:large-kana"><code>large-kana</code></dfn></dt>
+      <dt><dfn title="text-transform:full-size-kana"><code>full-size-kana</code></dfn></dt>
         <dd>Converts all small Kana characters to normal Kana.
           This value is typically used for ruby annotation text,
           where all small Kana should be drawn as large Kana.
@@ -380,9 +380,6 @@ <h3 id="text-transform">
       [[!UNICODE]] Only characters belonging to bicameral scripts are
       affected.</p>
 
-    <p>The definition of fullwidth and halfwidth forms can be found on the
-      Unicode consortium web site at [[!UAX11]].</p>
-
     <p>The definition of "word" used for ''captilize'' is UA-dependent;
       [[UAX29]] is suggested (but not required) for determining such word
       boundaries. Authors should not expect ''capitalize'' to follow
@@ -392,6 +389,13 @@ <h3 id="text-transform">
       the UA might want to use UAX29 to split into words, but skip forward
       past any starting non-letters (as an example of why UAX29 is not ideal) -->
 
+    <p>The definition of fullwidth and halfwidth forms can be found on the
+      Unicode consortium web site at [[!UAX11]]. <span class="issue">Find
+      equivalency tables at Unicode (or make them).</p>
+
+    <p class="issue">Should all characters be transformed, or only letters
+      (i.e. not symbols, punctuation, or white space)</p>
+
     <p>Text transformation happens after <a href="#white-space-rules">white
       space processing</a>. (This only matters when ''fullwidth'' transforms
       U+0020 space characters to U+3000.) <span class="issue">This requirement