- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 02 Jun 2011 15:33:29 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv27829
Modified Files:
Overview.html Overview.src.html
Log Message:
Rename 'auto' to be more awkward, since it's for deprecated stuff. Mark it at-risk.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.151
retrieving revision 1.152
diff -u -d -r1.151 -r1.152
--- Overview.html 2 Jun 2011 15:27:10 -0000 1.151
+++ Overview.html 2 Jun 2011 15:33:27 -0000 1.152
@@ -192,10 +192,6 @@
<li><a href="#text-baselines"><span class=secno>4.2. </span> Text
Baselines</a>
- <ul class=toc>
- <li><a href="#opentype-baselines"><span class=secno>4.2.1. </span>
- Baselines in TrueType/OpenType fonts</a>
- </ul>
<li><a href="#replaced-baselines"><span class=secno>4.3. </span> Atomic
Inline Baselines</a>
@@ -1304,27 +1300,6 @@
<p class=note>A future CSS module will deal with baselines in more detail
and allow the choice of other dominant baselines and alignment options.
- <h4 id=opentype-baselines><span class=secno>4.2.1. </span> Baselines in
- TrueType/OpenType fonts</h4>
-
- <p><em>This section is non-normative.</em>
-
- <p>The alphabetic baseline is listed as the <var>romn</var> baseline in
- TrueType/OpenType baseline tables. If missing, it can sometimes be
- computed from the ascender and descender metrics. If it cannot be computed
- from other metrics, it may be assumed to correspond to the zero
- coordinate.
-
- <p>For the ascender and descender metrics, it is recommended to use the
- <var>sTypoAscender</var> and <var>sTypoDescender</var> metrics from the
- font's OS/2 table. These should match the <var>idtp</var> and
- <var>ideo</var> baselines (respectively), which, if present, may be used
- instead. In the absence of these metrics, the <var>Ascent</var> and
- <var>Descent</var> metrics from the HHEA/VHEA table should be used. The
- Win metrics can be used as a fallback; however these are intended as
- clipping bounds and are not always appropriate for use as em box
- measurements.
-
<h3 id=replaced-baselines><span class=secno>4.3. </span> Atomic Inline
Baselines</h3>
@@ -1505,7 +1480,7 @@
<th>Value:
<td>vertical-right | upright | sideways-right | sideways-left | sideways
- | auto
+ | use-glyph-orientation
<tr>
<th>Initial:
@@ -1638,7 +1613,7 @@
writing mode. It can be useful when setting horizontal script text
vertically in a primarily horizontal-only document.
- <dt><dfn id=auto>auto</dfn>
+ <dt><dfn id=use-glyph-orientation>use-glyph-orientation</dfn>
<dd>
<p><a href="#SVG11" rel=biblioentry>[SVG11]<!--{{!SVG11}}--></a> defines
@@ -1647,20 +1622,24 @@
properties that were intended to control text orientation. These
properties are <em>deprecated</em> and do not apply to non-SVG elements.
If an implementation supports these properties, the ‘<a
- href="#auto"><code class=css>auto</code></a>’ value when set on
- SVG elements indicates that the SVG ‘<code
+ href="#use-glyph-orientation"><code
+ class=css>use-glyph-orientation</code></a>’ value when set on SVG
+ elements indicates that the SVG ‘<code
class=property>glyph-orientation-vertical</code>’ and ‘<code
class=property>glyph-orientation-horizontal</code>’ behavior
control the layout of text. Such UAs must set ‘<code
- class=css>text-orientation: auto</code>’ on all <a
+ class=css>text-orientation: glyph-orientation</code>’ on all <a
href="http://www.w3.org/TR/SVG/intro.html#TermTextContentElement">SVG
text content elements</a> in their default UA style sheet for SVG.
<p>In all other contexts, and for implementations that do not support the
- glyph orientation properties, the ‘<a href="#auto"><code
- class=css>auto</code></a>’ behavior is the same as for ‘<a
- href="#vertical-right"><code class=css>vertical-right</code></a>’.
-
+ glyph orientation properties, the ‘<a
+ href="#use-glyph-orientation"><code
+ class=css>use-glyph-orientation</code></a>’ behavior is the same
+ as for ‘<a href="#vertical-right"><code
+ class=css>vertical-right</code></a>’.
+
+ <p class=note>This value is at-risk and may be dropped during CR.
</dl>
<div class=figure> <img alt="text-orientation: vertical-right, upright,
@@ -2203,9 +2182,8 @@
class=property>margin-left</code>’ and ‘<code
class=property>margin-right</code>’ would collapse with margins
before (on the right) and after (on the left) the table, respectively,
- and if the table had ‘<a href="#auto"><code
- class=css>auto</code></a>’ values for ‘<code
- class=property>margin-top</code>’ and ‘<code
+ and if the table had ‘<code class=css>auto</code>’ values for
+ ‘<code class=property>margin-top</code>’ and ‘<code
class=property>margin-bottom</code>’ it would be centered
vertically within its block flow.
@@ -2338,9 +2316,8 @@
<p>It is common in CSS for a containing block to have a defined measure,
but not a defined extent. This typically happens in CSS2.1 when a
- containing block has an ‘<a href="#auto"><code
- class=css>auto</code></a>’ height, for example: its width is given
- by the calculations in <a
+ containing block has an ‘<code class=css>auto</code>’ height,
+ for example: its width is given by the calculations in <a
href="http://www.w3.org/TR/CSS21/visudet.html#blockwidth">10.3.3</a>, but
its extent depends on its contents. In such cases the <dfn
id=available-measure>available measure</dfn> is defined as the measure of
@@ -2360,10 +2337,10 @@
Orthogonal Flows</h4>
<p>If the computed measure of an element establishing an orthogonal flow is
- ‘<a href="#auto"><code class=css>auto</code></a>’, then the
- used measure is calculated as the <a
- href="#fit-content"><i>fit-content</i></a> (shrink-to-fit) size using the
- initial containing block's size as the available measure.
+ ‘<code class=css>auto</code>’, then the used measure is
+ calculated as the <a href="#fit-content"><i>fit-content</i></a>
+ (shrink-to-fit) size using the initial containing block's size as the
+ available measure.
<h4 id=orthogonal-multicol><span class=secno>7.3.2. </span> Multi-column
Layout in Orthogonal Flows</h4>
@@ -2371,12 +2348,12 @@
<p>If the UA supports CSS Multi-column Layout <a href="#CSS3COL"
rel=biblioentry>[CSS3COL]<!--{{!CSS3COL}}--></a>, then for the case where
the element's extent or available extent is defined but the element's
- measure is ‘<a href="#auto"><code class=css>auto</code></a>’:
+ measure is ‘<code class=css>auto</code>’:
<ol>
<li>If ‘<code class=property>column-count</code>’ and
- ‘<code class=property>column-width</code>’ are both ‘<a
- href="#auto"><code class=css>auto</code></a>’, a used ‘<code
+ ‘<code class=property>column-width</code>’ are both
+ ‘<code class=css>auto</code>’, a used ‘<code
class=property>column-width</code>’ is calculated for the element
as the <a href="#fill-available-measure"><i>fill-available
measure</i></a> using the <a href="#fallback-measure"><i>fallback
@@ -3309,9 +3286,8 @@
<p>For replaced elements, the <a href="#min-content"><i>min-content</i></a>
and <a href="#max-content"><i>max-content</i></a> sizes are the same and
- correspond used size of the replaced element according to the ‘<a
- href="#auto"><code class=css>auto</code></a>’ width and height
- calculations.
+ correspond used size of the replaced element according to the ‘<code
+ class=css>auto</code>’ width and height calculations.
<h3 class=no-num id=multicol-intrinsic> Intrinsic Sizes in Multi-column
Layout</h3>
@@ -3717,7 +3693,7 @@
<td><a class=property href="#text-orientation0">text-orientation</a>
<td>vertical-right | upright | sideways-right | sideways-left | sideways
- | auto
+ | use-glyph-orientation
<td>vertical-right
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.159
retrieving revision 1.160
diff -u -d -r1.159 -r1.160
--- Overview.src.html 2 Jun 2011 15:27:10 -0000 1.159
+++ Overview.src.html 2 Jun 2011 15:33:27 -0000 1.160
@@ -920,26 +920,6 @@
detail and allow the choice of other dominant baselines and alignment
options.</p>
-<h4 id="opentype-baselines">
-Baselines in TrueType/OpenType fonts</h4>
-
- <p><em>This section is non-normative.</em></p>
-
- <p>The alphabetic baseline is listed as the <var>romn</var>
- baseline in TrueType/OpenType baseline tables. If missing, it can
- sometimes be computed from the ascender and descender metrics. If it
- cannot be computed from other metrics, it may be assumed to correspond
- to the zero coordinate.</p>
-
- <p>For the ascender and descender metrics, it is recommended to use the
- <var>sTypoAscender</var> and <var>sTypoDescender</var> metrics from the
- font's OS/2 table. These should match the <var>idtp</var> and <var>ideo</var>
- baselines (respectively), which, if present, may be used instead. In the
- absence of these metrics, the <var>Ascent</var> and <var>Descent</var>
- metrics from the HHEA/VHEA table should be used. The Win metrics can be
- used as a fallback; however these are intended as clipping bounds and
- are not always appropriate for use as em box measurements.</em>
-
<h3 id="replaced-baselines">
Atomic Inline Baselines</h3>
@@ -1085,7 +1065,8 @@
</tr>
<tr>
<th>Value:</th>
- <td>vertical-right | upright | sideways-right | sideways-left | sideways | auto</td>
+ <td>vertical-right | upright | sideways-right | sideways-left | sideways
+ | use-glyph-orientation
</tr>
<tr>
<th>Initial:</th>
@@ -1178,20 +1159,22 @@
writing mode and equivalent to ''sideways-left'' in ''vertical-lr''
writing mode. It can be useful when setting horizontal script text
vertically in a primarily horizontal-only document.
- <dt><dfn>auto</dfn></dt>
+ <dt><dfn>use-glyph-orientation</dfn></dt>
<dd><p>[[!SVG11]] defines 'glyph-orientation-vertical' and
'glyph-orientation-horizontal' properties that were intended to control
text orientation. These properties are <em>deprecated</em> and do not
apply to non-SVG elements. If an implementation supports these properties,
- the ''auto'' value when set on SVG elements indicates that the SVG
- 'glyph-orientation-vertical' and 'glyph-orientation-horizontal' behavior
- control the layout of text. Such UAs must set ''text-orientation: auto''
- on all
+ the ''use-glyph-orientation'' value when set on SVG elements indicates
+ that the SVG
+ 'glyph-orientation-vertical' and 'glyph-orientation-horizontal'
+ behavior control the layout of text. Such UAs must set
+ ''text-orientation: glyph-orientation'' on all
<a href="http://www.w3.org/TR/SVG/intro.html#TermTextContentElement">SVG
text content elements</a> in their default UA style sheet for SVG.
<p>In all other contexts, and for implementations that do not support
- the glyph orientation properties, the ''auto'' behavior is the same
- as for ''vertical-right''.
+ the glyph orientation properties, the ''use-glyph-orientation'' behavior
+ is the same as for ''vertical-right''.
+ <p class="note">This value is at-risk and may be dropped during CR.
</dl>
<div class="figure">
Received on Thursday, 2 June 2011 15:33:31 UTC