csswg/css3-writing-modes Overview.html,1.201,1.202 Overview.src.html,1.212,1.213

Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv504

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Split out scaling options into 'text-combine-mode' property. <http://lists.w3.org/Archives/Public/www-style/2011Aug/0427.html>

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.201
retrieving revision 1.202
diff -u -d -r1.201 -r1.202
--- Overview.html	20 Aug 2011 06:40:36 -0000	1.201
+++ Overview.html	26 Aug 2011 04:30:35 -0000	1.202
@@ -32,7 +32,7 @@
 
    <h1>CSS Writing Modes Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 20 August 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 26 August 2011</h2>
 
    <dl>
     <dt>This version:
@@ -40,7 +40,7 @@
     <dd><a
      href="http://dev.w3.org/csswg/css3-writing-modes/">http://dev.w3.org/csswg/css3-writing-modes/</a>
      <!--
-    <dd><a href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110820">http://www.w3.org/TR/2011/ED-css3-writing-modes-20110820/</a>
+    <dd><a href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110826">http://www.w3.org/TR/2011/ED-css3-writing-modes-20110826/</a>
 -->
      
 
@@ -156,13 +156,13 @@
    <li>The &lsquo;<code class=css>ascii-digits</code>&rsquo;, &lsquo;<code
     class=css>digits</code>&rsquo;, &lsquo;<code
     class=css>alpha</code>&rsquo;, &lsquo;<code
-    class=css>latin</code>&rsquo;, &lsquo;<code
-    class=css>alphanumeric</code>&rsquo;, &lsquo;<code
-    class=css>compress</code>&rsquo;, &lsquo;<code
-    class=css>no-compress</code>&rsquo;, and &lsquo;<code
-    class=css>use-glyphs</code>&rsquo; values of &lsquo;<a
-    href="#text-combine-horizontal"><code
+    class=css>latin</code>&rsquo;, and &lsquo;<code
+    class=css>alphanumeric</code>&rsquo; values of &lsquo;<a
+    href="#text-combine-horizontal0"><code
     class=property>text-combine-horizontal</code></a>&rsquo;.
+
+   <li>The &lsquo;<a href="#text-combine-mode"><code
+    class=property>text-combine-mode</code></a>&rsquo; property
   </ul>
 
   <h2 class="no-num no-toc" id=Contents> Table of Contents</h2>
@@ -295,8 +295,16 @@
     page progression direction</a>
 
    <li><a href="#text-combine"><span class=secno>9. </span> Glyph
-    Composition: the &lsquo;<code
-    class=property>text-combine-horizontal</code>&rsquo; property</a>
+    Composition</a>
+    <ul class=toc>
+     <li><a href="#text-combine-horizontal"><span class=secno>9.1. </span>
+      Horizonal-in-Vertical Composition: the &lsquo;<code
+      class=property>text-combine-horizontal</code>&rsquo; property</a>
+
+     <li><a href="#text-combine-horizontal"><span class=secno>9.2. </span>
+      Horizonal-in-Vertical Glyph Scaling: the &lsquo;<code
+      class=property>text-combine-mode</code>&rsquo; property</a>
+    </ul>
 
    <li class=no-num><a href="#changes">Changes</a>
     <ul class=toc>
@@ -2839,23 +2847,26 @@
    second half of a spread, e.g. on the right page in a left-to-right page
    progression.)
 
-  <h2 id=text-combine><span class=secno>9. </span> Glyph Composition: the
-   &lsquo;<a href="#text-combine-horizontal"><code
-   class=property>text-combine-horizontal</code></a>&rsquo; property</h2>
+  <h2 id=text-combine><span class=secno>9. </span> Glyph Composition</h2>
+
+  <h3 id=text-combine-horizontal><span class=secno>9.1. </span>
+   Horizonal-in-Vertical Composition: the &lsquo;<a
+   href="#text-combine-horizontal0"><code
+   class=property>text-combine-horizontal</code></a>&rsquo; property</h3>
 
   <table class=propdef>
    <tbody>
     <tr>
      <th>Name:
 
-     <td><dfn id=text-combine-horizontal>text-combine-horizontal</dfn>
+     <td><dfn id=text-combine-horizontal0>text-combine-horizontal</dfn>
 
     <tr>
      <th>Value:
 
      <td>none | all | [ [digits &lt;integer> | ascii-digits &lt;integer> ] ||
       [ alpha &lt;integer> | latin &lt;integer> ] || alphanumeric
-      &lt;integer> ] && [ compress | [ no-compress || use-glyphs ] ]?
+      &lt;integer> ]
 
     <tr>
      <th>Initial:
@@ -2955,34 +2966,11 @@
     and/or letters that has as many or fewer characters than the integer
     given is treated as if it were in an anonymous inline box with
     &lsquo;<code class=css>text-combine-horizontal: all</code>&rsquo;.
-
-   <dt><dfn id=use-glyphs
-    title="text-combine-horizontal:use-glyphs">use-glyphs</dfn>
-
-   <dd>If the UA has alternate-width glyphs available for the contents of the
-    element, then it must use those glyphs to attempt sizing the contents to
-    1em square. See below.
-
-   <dt><dfn id=compress
-    title="text-combine-horizontal:compress">compress</dfn>
-
-   <dd>Compress the composition (horizontally) as a whole until it fits
-    within 1em. Do not substitute alternate-width glyphs.
-
-   <dt><dfn id=no-compress
-    title="text-combine-horizontal:no-compress">no-compress</dfn>
-
-   <dd>Do not compress the composition or perform any glyph substitution in
-    order to make the composition fit within 1em. This may cause the glyphs
-    to overflow the line significantly. When combined with &lsquo;<code
-    class=css>use-glyphs</code>&rsquo;, this indicates to perform glyph
-    substitution if possible per &lsquo;<code
-    class=css>use-glyphs</code>&rsquo; but not to compress the glyphs if they
-    do not fit within the size constraints.
   </dl>
 
   <p class=issue>All values except &lsquo;<code class=css>all</code>&rsquo;
-   are marked at-risk. Which ones should we take to CR?
+   and &lsquo;<code class=css>none</code>&rsquo; are marked at-risk. Which
+   ones should we take to CR?
 
   <p>When combining text as for &lsquo;<code
    class=css>text-combine-horizontal: all</code>&rsquo;, the glyphs of the
@@ -3000,36 +2988,6 @@
    composition is treated as a single glyph representing the Object
    Replacement Character U+FFFC.
 
-  <p>If none of &lsquo;<code class=css>compress</code>&rsquo;, &lsquo;<code
-   class=css>no-compress</code>&rsquo;, or &lsquo;<code
-   class=css>use-glyphs</code>&rsquo; are specified and the contents are
-   wider than 1em, the UA must attempt to fit the contents within 1em, but
-   may use any method to do so.
-
-  <p>If &lsquo;<code class=css>use-glyphs</code>&rsquo; is specified the UA
-   must attempt to substitute narrower glyphs as necessary to make the
-   composition fit within 1em:
-
-  <ul>
-   <li>a two-character composition would use 1/2-em or proportional glyphs
-
-   <li>a three-character composition would use 1/3-em glyphs (if the font
-    supports this feature, else fall back to 1/2-em or proportional glyphs)
-
-   <li>etc.
-  </ul>
-
-  <p>Since even fonts that have fractional-width glyphs available do not have
-   such glyphs for all characters, if &lsquo;<code
-   class=css>no-compress</code>&rsquo; is not specified, the UA must ensure
-   the expected advance width for &lsquo;<code
-   class=css>use-glyphs</code>&rsquo; by either compressing or padding
-   (equally on both sides) each glyph individually if it does not match the
-   required advance width. If &lsquo;<code
-   class=css>no-compress</code>&rsquo; is specified, then the UA must not
-   attempt to adjust the width of the glyph even if it differs from the
-   expected dimension. This may cause the combined text to overflow.
-
   <p>In some fonts, the ideographic glyphs are given a compressed design such
    that they are 1em wide but shorter than 1em tall. To accommodate such
    fonts, the UA may vertically scale the contents of the composition to
@@ -3049,7 +3007,7 @@
 
   <div class=example>
    <p>In East Asian documents, the &lsquo;<a
-    href="#text-combine-horizontal"><code
+    href="#text-combine-horizontal0"><code
     class=css>text-combine-horizontal</code></a>&rsquo; effect is often used
     to display Latin-based strings such as components of a date or letters of
     an initialism, always in a horizontal writing mode regardless of the
@@ -3097,6 +3055,106 @@
    </div>
   </div>
 
+  <h3 id=text-combine-horizontal><span class=secno>9.2. </span>
+   Horizonal-in-Vertical Glyph Scaling: the &lsquo;<a
+   href="#text-combine-mode"><code
+   class=property>text-combine-mode</code></a>&rsquo; property</h3>
+
+  <table class=propdef>
+   <tbody>
+    <tr>
+     <th>Name:
+
+     <td><dfn id=text-combine-mode>text-combine-mode</dfn>
+
+    <tr>
+     <th>Value:
+
+     <td>auto | compress | [ no-compress || use-glyphs ]
+
+    <tr>
+     <th>Initial:
+
+     <td>none
+
+    <tr>
+     <th>Applies to:
+
+     <td>non-replaced inline elements
+
+    <tr>
+     <th>Inherited:
+
+     <td>yes
+
+    <tr>
+     <th>Percentages:
+
+     <td>N/A
+
+    <tr>
+     <th>Media:
+
+     <td>visual
+
+    <tr>
+     <th>Computed&#160;value:
+
+     <td>specified value
+  </table>
+
+  <p>This property controls how multiple characters are combined into the
+   space of a single character when specified to do so via &lsquo;<a
+   href="#text-combine-horizontal0"><code
+   class=property>text-combine-horizontal</code></a>&rsquo;. Values have the
+   following meanings:
+
+  <dl>
+   <dt><dfn id=auto title="text-combine-mode:auto">auto</dfn>
+
+   <dd>If the contents are wider than 1em, the UA must attempt to fit the
+    contents within 1em, but may use any method to do so.
+
+   <dt><dfn id=compress title="text-combine-mode:compress">compress</dfn>
+
+   <dd>Compress the composition (horizontally) as a whole until it fits
+    within 1em. Do not substitute alternate-width glyphs.
+
+   <dt><dfn id=use-glyphs
+    title="text-combine-mode:use-glyphs">use-glyphs</dfn>
+
+   <dd>Attempt to substitute narrower glyphs as necessary to make the
+    composition fit within 1em:
+    <ul>
+     <li>a two-character composition uses 1/2-em or proportional glyphs
+
+     <li>a three-character composition uses 1/3-em glyphs (if the font
+      supports this feature, else fall back to 1/2-em or proportional glyphs)
+      
+
+     <li>etc.
+    </ul>
+
+    <p>Since even fonts that have fractional-width glyphs available do not
+     have such glyphs for all characters, the UA must ensure the expected
+     advance width for &lsquo;<code class=css>use-glyphs</code>&rsquo; by
+     either compressing or padding (equally on both sides) each glyph
+     individually if it does not match the required advance width. (This step
+     does not apply if &lsquo;<code class=css>no-compress</code>&rsquo; is
+     specified.)
+
+   <dt><dfn id=no-compress
+    title="text-combine-mode:no-compress">no-compress</dfn>
+
+   <dd>Do not compress the composition or perform any glyph substitution in
+    order to make the composition fit within 1em. When combined with
+    &lsquo;<code class=css>use-glyphs</code>&rsquo;, however, this indicates
+    to perform glyph substitution if possible per &lsquo;<code
+    class=css>use-glyphs</code>&rsquo; but not to compress the glyphs if they
+    do not fit the size requirements. This value may cause the glyphs to
+    overflow the line significantly.
+  </dl>
+
   <h2 class=no-num id=changes>Changes</h2>
 
   <h3 class=no-num id=recent-changes> Changes from the <a
@@ -3135,7 +3193,7 @@
     href="#vertical-typesetting-details">synthesis rules</a>, etc.
 
    <li>Renamed &lsquo;<code class=property>text-combine</code>&rsquo;
-    property to &lsquo;<a href="#text-combine-horizontal"><code
+    property to &lsquo;<a href="#text-combine-horizontal0"><code
     class=property>text-combine-horizontal</code></a>&rsquo; and added
     ability to auto-combine by character classes. Added many more details on
     how to compose horizontal-in-vertical text.
@@ -3435,9 +3493,9 @@
    of these are present, the font is considered to have vertical font
    settings available.
 
-  <p class=issue>It is a Unicode error that ScriptExt.txt does not include
-   the Aegean and Common Indic characters listed above as exceptions; they
-   shouldn't need special treatment once this is fixed.
+  <p class=issue>It is a Unicode error that ScriptExtensions.txt does not
+   include the Aegean and Common Indic characters listed above as exceptions;
+   they shouldn't need special treatment once this is fixed.
 
   <h2 class=no-num id=intrinsic-sizing>Appendix D: Intrinsic Dimensions</h2>
 
@@ -4041,11 +4099,26 @@
 
     <tr>
      <th><a class=property
-      href="#text-combine-horizontal">text-combine-horizontal</a>
+      href="#text-combine-horizontal0">text-combine-horizontal</a>
 
      <td>none | all | [ [digits &lt;integer> | ascii-digits &lt;integer> ] ||
       [ alpha &lt;integer> | latin &lt;integer> ] || alphanumeric
-      &lt;integer> ] && [ compress | [ no-compress || use-glyphs ] ]?
+      &lt;integer> ]
+
+     <td>none
+
+     <td>non-replaced inline elements
+
+     <td>yes
+
+     <td>N/A
+
+     <td>visual
+
+    <tr>
+     <th><a class=property href="#text-combine-mode">text-combine-mode</a>
+
+     <td>auto | compress | [ no-compress || use-glyphs ]
 
      <td>none
 

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.212
retrieving revision 1.213
diff -u -d -r1.212 -r1.213
--- Overview.src.html	20 Aug 2011 06:40:36 -0000	1.212
+++ Overview.src.html	26 Aug 2011 04:30:35 -0000	1.213
@@ -79,8 +79,9 @@
 <p>The following features are at-risk and may be dropped during CR:
 <ul>
   <li>The ''use-glyph-orientation'' of 'text-orientation'
-  <li>The ''ascii-digits'', ''digits'', ''alpha'', ''latin'', ''alphanumeric'',
-    ''compress'', ''no-compress'', and ''use-glyphs'' values of 'text-combine-horizontal'.
+  <li>The ''ascii-digits'', ''digits'', ''alpha'', ''latin'', and ''alphanumeric''
+    values of 'text-combine-horizontal'.
+  <li>The 'text-combine-mode' property
 </ul>
 
 <h2 class="no-num no-toc" id="Contents">
@@ -2113,7 +2114,10 @@
     progression.)
 
 <h2 id="text-combine">
-Glyph Composition: the 'text-combine-horizontal' property</h2>
+Glyph Composition</h2>
+
+<h3 id="text-combine-horizontal">
+Horizonal-in-Vertical Composition: the 'text-combine-horizontal' property</h3>
 
   <table class="propdef">
     <tbody>
@@ -2127,7 +2131,6 @@
             [  [digits &lt;integer> | ascii-digits &lt;integer> ]
             || [ alpha &lt;integer> | latin &lt;integer> ]
             || alphanumeric &lt;integer> ]
-            && [ compress | [ no-compress || use-glyphs ] ]?</td>
       </tr>
       <tr>
         <th>Initial:</th>
@@ -2206,24 +2209,10 @@
       letters that has as many or fewer characters than the integer given is treated
       as if it were in an anonymous inline box with
       ''text-combine-horizontal: all''.
-    <dt><dfn title="text-combine-horizontal:use-glyphs">use-glyphs</dfn>
-    <dd>If the UA has alternate-width glyphs available for the contents
-      of the element, then it must use those glyphs to attempt sizing the
-      contents to 1em square. See below.
-    <dt><dfn title="text-combine-horizontal:compress">compress</dfn>
-    <dd>Compress the composition (horizontally) as a whole until it fits within 1em.
-      Do not substitute alternate-width glyphs.
-    <dt><dfn title="text-combine-horizontal:no-compress">no-compress</dfn>
-    <dd>Do not compress the composition or perform any glyph substitution
-      in order to make the composition fit within 1em. This may
-      cause the glyphs to overflow the line significantly. When combined
-      with ''use-glyphs'', this indicates to perform glyph substitution
-      if possible per ''use-glyphs'' but not to compress the glyphs if
-      they do not fit within the size constraints.
   </dl>
 
-  <p class="issue">All values except ''all'' are marked at-risk. Which
-    ones should we take to CR?</p>
+  <p class="issue">All values except ''all'' and ''none'' are marked at-risk.
+    Which ones should we take to CR?</p>
 
   <p>When combining text as for ''text-combine-horizontal: all'', the
     glyphs of the combined text are stacked horizontally (without line
@@ -2241,27 +2230,6 @@
     etc. the resulting composition is treated as a single glyph
     representing the Object Replacement Character U+FFFC.
 
-  <p>If none of ''compress'', ''no-compress'', or ''use-glyphs'' are specified
-    and the contents are wider than 1em, the UA must attempt to fit the
-    contents within 1em, but may use any method to do so.
-
-  <p>If ''use-glyphs'' is specified the UA must attempt to substitute
-    narrower glyphs as necessary to make the composition fit within 1em:
-    <ul>
-      <li>a two-character composition would use 1/2-em or proportional glyphs
-      <li>a three-character composition would use 1/3-em glyphs (if the font
-        supports this feature, else fall back to 1/2-em or proportional glyphs)
-      <li>etc.
-   </ul>
-   <p>Since even fonts that have fractional-width glyphs available do
-   not have such glyphs for all characters, if ''no-compress'' is not
-   specified, the UA must ensure the expected advance width for ''use-glyphs''
-   by either compressing or padding (equally on both sides) each glyph
-   individually if it does not match the required advance width. If
-   ''no-compress'' is specified, then the UA must not attempt to adjust
-   the width of the glyph even if it differs from the expected dimension.
-   This may cause the combined text to overflow.
-
   <p>In some fonts, the ideographic glyphs are given a compressed design
     such that they are 1em wide but shorter than 1em tall. To accommodate
     such fonts, the UA may vertically scale the contents of the composition
@@ -2315,6 +2283,81 @@
     </div>
   </div>
 
+<h3 id="text-combine-horizontal">
+Horizonal-in-Vertical Glyph Scaling: the 'text-combine-mode' property</h3>
+
+  <table class="propdef">
+    <tbody>
+      <tr>
+        <th>Name:
+        <td><dfn>text-combine-mode</dfn>
+      </tr>
+      <tr>
+        <th>Value:
+        <td>auto | compress | [ no-compress || use-glyphs ]
+      </tr>
+      <tr>
+        <th>Initial:
+        <td>none
+      </tr>
+      <tr>
+        <th>Applies to:
+        <td>non-replaced inline elements
+      </tr>
+      <tr>
+        <th>Inherited:
+        <td>yes
+      </tr>
+      <tr>
+        <th>Percentages:
+        <td>N/A
+      </tr>
+      <tr>
+        <th>Media:
+        <td>visual
+      </tr>
+      <tr>
+        <th>Computed&#160;value:
+        <td>specified value
+      </tr>
+    </tbody>
+  </table>
+
+  <p>This property controls how multiple characters are combined into the
+    space of a single character when specified to do so via
+    'text-combine-horizontal'. Values have the following meanings:</p>
+
+  <dl>
+    <dt><dfn title="text-combine-mode:auto">auto</dfn>
+    <dd>If the contents are wider than 1em, the UA must attempt to fit the
+      contents within 1em, but may use any method to do so.
+    <dt><dfn title="text-combine-mode:compress">compress</dfn>
+    <dd>Compress the composition (horizontally) as a whole until it fits within 1em.
+      Do not substitute alternate-width glyphs.
+    <dt><dfn title="text-combine-mode:use-glyphs">use-glyphs</dfn>
+    <dd>Attempt to substitute narrower glyphs as necessary to make the
+      composition fit within 1em:
+      <ul>
+        <li>a two-character composition uses 1/2-em or proportional glyphs
+        <li>a three-character composition uses 1/3-em glyphs (if the font
+          supports this feature, else fall back to 1/2-em or proportional glyphs)
+        <li>etc.
+      </ul>
+      <p>Since even fonts that have fractional-width glyphs available do
+      not have such glyphs for all characters, the UA must ensure the
+      expected advance width for ''use-glyphs'' by either compressing or
+      padding (equally on both sides) each glyph individually if it does
+      not match the required advance width. (This step does not apply if
+      ''no-compress'' is specified.)
+    <dt><dfn title="text-combine-mode:no-compress">no-compress</dfn>
+    <dd>Do not compress the composition or perform any glyph substitution
+      in order to make the composition fit within 1em.
+      When combined with ''use-glyphs'', however, this indicates to perform
+      glyph substitution if possible per ''use-glyphs'' but not to compress
+      the glyphs if they do not fit the size requirements.
+      This value may cause the glyphs to overflow the line significantly.
+  </dl>
+
 <h2 class="no-num" id="changes">Changes</h2>
   <h3 class="no-num" id="recent-changes">
   Changes from the <a href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110531/">May
@@ -2528,7 +2571,7 @@
     If any of these are present, the font is considered to have vertical
     font settings available.
 
-  <p class="issue">It is a Unicode error that ScriptExt.txt does not include the
+  <p class="issue">It is a Unicode error that ScriptExtensions.txt does not include the
     Aegean and Common Indic characters listed above as exceptions; they shouldn't
     need special treatment once this is fixed.
 

Received on Friday, 26 August 2011 04:30:39 UTC