More uppercasing issues

Author: fantasai

css3-text/Overview.html

@@ -90,7 +90,7 @@ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 21 July 2011</h2>
     <dt>This version:
 
     <dd><a href="http://dev.w3.org/csswg/css3-text/Overview.html">$Date:
-     2011/07/21 20:00:30 $ (CVS $Revision$)</a> <!--
+     2011/07/21 20:53:38 $ (CVS $Revision$)</a> <!--
       <dd><a href="http://www.w3.org/TR/2011/WD-css3-text-20110721/">http://www.w3.org/TR/2011/WD-css3-text-20110721/</a></dd>
     -->
 
@@ -663,6 +663,24 @@ <h3 id=text-transform><span class=secno>2.1. </span> <a name=caps-prop></a>
    <pre>abbr:lang(ja) { text-transform: fullwidth; }</pre>
   </div>
 
+  <p class=issue>All-caps text sometimes has special typographic
+   considerations. For example: Punctuation and number glyphs might be
+   adjusted for the higher "center of gravity" (see the <a
+   href="http://www.microsoft.com/typography/otspec/features_ae.htm#case">case</a>
+   feature in OpenType). Should we turn that on by default, as they suggest?
+   Or spacing might be adjusted for the increased visual weight of the glyphs
+   (see the <a
+   href="http://www.microsoft.com/typography/otspec/features_ae.htm#cpsp">cpsp</a>
+   feature in OpenType). Should we turn that on when &lsquo;<a
+   href="#letter-spacing0"><code
+   class=property>letter-spacing</code></a>&rsquo; is &lsquo;<code
+   class=css>normal</code>&rsquo;?
+
+  <p>A more complicated problem is the <a
+   href="http://blogs.msdn.com/b/michkap/archive/2006/08/18/706383.aspx">greek
+   uppercasing rules</a> which actually alter the diacritics. How should we
+   handle that?
+
   <p class=note>A future level of CSS may introduce an &lsquo;<a
    href="#text-transform0"><code class=css>@text-transform</code></a>&rsquo;
    rule similar to &lsquo;<code class=css>@counter-style</code>&rsquo; from

css3-text/Overview.src.html

@@ -267,7 +267,7 @@ <h3 id="text-transform">
         <dd>Puts the first <i>character</i> of each word in titlecase; other characters
           are unaffected.</dd>
       <dt><dfn title="text-transform:uppercase"><code>uppercase</code></dfn></dt>
-        <dd>Puts all characters in uppercase.</dd>
+        <dd>Puts all characters in uppercase.
       <dt><dfn title="text-transform:lowercase"><code>lowercase</code></dfn></dt>
         <dd>Puts all characters in lowercase.</dd>
       <dt><dfn title="text-transform:full-width"><code>full-width</code></dfn></dt>
@@ -331,6 +331,18 @@ <h3 id="text-transform">
       <pre>abbr:lang(ja) { text-transform: fullwidth; }</pre>
     </div>
 
+    <p class="issue">All-caps text sometimes has special typographic considerations.
+      For example: Punctuation and number glyphs might be adjusted for the
+      higher "center of gravity" (see the
+        <a href="http://www.microsoft.com/typography/otspec/features_ae.htm#case">case</a>
+      feature in OpenType). Should we turn that on by default, as they suggest?
+      Or spacing might be adjusted for the increased visual weight of the glyphs
+      (see the <a href="http://www.microsoft.com/typography/otspec/features_ae.htm#cpsp">cpsp</a>
+      feature in OpenType). Should we turn that on when 'letter-spacing' is ''normal''?</p>
+      
+    <p>A more complicated problem is the <a href="http://blogs.msdn.com/b/michkap/archive/2006/08/18/706383.aspx">greek uppercasing rules</a>
+      which actually alter the diacritics. How should we handle that?
+
     <p class="note">A future level of CSS may introduce an ''@text-transform''
       rule similar to ''@counter-style'' from [[CSS3LISTS]] to create mapping
       tables for less common text transforms.