- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 12 Jan 2012 01:48:27 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-text
In directory hutz:/tmp/cvs-serv26732
Modified Files:
Overview.html Overview.src.html
Log Message:
Consolidate/remove/defer some issues, fix some minor glitches.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.html,v
retrieving revision 1.202
retrieving revision 1.203
diff -u -d -r1.202 -r1.203
--- Overview.html 10 Jan 2012 01:27:21 -0000 1.202
+++ Overview.html 12 Jan 2012 01:48:25 -0000 1.203
@@ -29,15 +29,15 @@
<h1>CSS Text Level 3</h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 10 January
+ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 12 January
2012</h2>
<dl>
<dt>This version:
- <dd><a href="http://dev.w3.org/csswg/css3-text/">$Date: 2012/01/07
- 01:20:41 $ (CVS $Revision$)</a> <!--
- <dd><a href="http://www.w3.org/TR/2012/WD-css3-text-20120110/">http://www.w3.org/TR/2012/WD-css3-text-20120110/</a></dd>
+ <dd><a href="http://dev.w3.org/csswg/css3-text/">$Date: 2012/01/10
+ 01:27:22 $ (CVS $Revision$)</a> <!--
+ <dd><a href="http://www.w3.org/TR/2012/WD-css3-text-20120112/">http://www.w3.org/TR/2012/WD-css3-text-20120112/</a></dd>
-->
@@ -275,7 +275,7 @@
the ‘<code class=property>text-align</code>’ property</a>
<ul class=toc>
<li><a href="#character-alignment"><span class=secno>7.1.1.
- </span>Details on Character-based Alignment in a Table Column</a>
+ </span>Character-based Alignment in a Table Column</a>
</ul>
<li><a href="#text-align-last"><span class=secno>7.2. </span> Last Line
@@ -651,12 +651,6 @@
<pre>abbr:lang(ja) { text-transform: full-width; }</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?
-
<p class=issue>CSS may introduce the ability to create custom mapping
tables for less common text transforms, such as by an ‘<a
href="#text-transform0"><code class=css>@text-transform</code></a>’
@@ -698,11 +692,7 @@
<p>Control characters (Unicode class Cc) other than tab (U+0009), line feed
(U+000A), space (U+0020), and the bidi formatting characters
- (U+202<var>x</var>) should be rendered as invisible zero-width characters.
- UAs may instead treat them as visible characters. (Note, however, that
- this will usually result in them being rendered as missing glyphs.) <span
- class=issue>What's the line-breaking behavior? Effects on joining? Can we
- just copy the behavior of some zero-width Unicode character?</span>
+ (U+202<var>x</var>) are ignored for the purpose of rendering.
<h3 id=white-space-collapsing><span class=secno>3.1. </span> White Space
Collapsing: the ‘<a href="#text-space-collapse"><code
@@ -1190,29 +1180,28 @@
defined by the boundary between two characters, the properties on the
element containing the boundary control breaking.
<!-- http://lists.w3.org/Archives/Public/www-style/2008Dec/0043.html -->
- <span class=issue>What about Zs outside of U+0020?</span> For break
- opportunities given by the first or last character of a box, the break
- occurs immediately before/after the box rather than breaking the box.
+ For break opportunities given by the first or last character of a box, the
+ break occurs immediately before/after the box rather than breaking the
+ box.
- <p class=note>Further information on line breaking conventions can be found
- in <a href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> and <a
- href="#JIS4051" rel=biblioentry>[JIS4051]<!--{{JIS4051}}--></a> for
- Japanese, <a href="#ZHMARK" rel=biblioentry>[ZHMARK]<!--{{ZHMARK}}--></a>
- for Chinese, and in <a href="#UAX14"
- rel=biblioentry>[UAX14]<!--{{!UAX14}}--></a> for all scripts in Unicode.
- <!-- The CSS Working Group notes that although UAX 14 contains a wealth of
+ <div class=note>
+ <p>Further information on line breaking conventions can be found in <a
+ href="#JLREQ" rel=biblioentry>[JLREQ]<!--{{JLREQ}}--></a> and <a
+ href="#JIS4051" rel=biblioentry>[JIS4051]<!--{{JIS4051}}--></a> for
+ Japanese, <a href="#ZHMARK" rel=biblioentry>[ZHMARK]<!--{{ZHMARK}}--></a>
+ for Chinese, and in <a href="#UAX14"
+ rel=biblioentry>[UAX14]<!--{{!UAX14}}--></a> for all scripts in Unicode.
+ <!-- The CSS Working Group notes that although UAX 14 contains a wealth of
information about line breaking conventions, a literal implementation
of its algorithm has been found to be inadequate in multiple situations. -->
+
- <p class=issue>Any guidance for appropriate references here would be much
- appreciated.
-
- <p class=issue>It is not clear whether this section handles Southeast Asian
- scripts well. Additionally, some guidance should be provided on how to
- break or not break Southeast Asian in the absence of a dictionary. (See
- e.g. <a
- href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">notes
- on Thai</a>.)
+ <p class=issue>Any guidance for appropriate references here would be much
+ appreciated. <!-- Additionally, some guidance could be provided on how
+ to break or not break Southeast Asian in the absence of a dictionary.
+ (See e.g. <a href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">notes on Thai</a>.) -->
+
+ </div>
<p>Floated and absolutely-positioned elements do not introduce a line
breaking opportunity. The line breaking behavior of a replaced element is
@@ -1442,7 +1431,7 @@
<div class=example>
<p>Here's a mixed-script sample text:
- <pre>这是一些汉字, and some Latin text,<!--
+ <pre>这是一些汉字, and some Latin,<!--
--> و کمی نوشتنن عربی, <!--
-->and some complex LTR.</pre>
@@ -1453,21 +1442,21 @@
<dt>‘<code class=css>word-break: normal</code>’
<dd>
- <pre>这·是·一·些·汉·字,·and·some·Latin·text,<!--
+ <pre>这·是·一·些·汉·字,·and·some·Latin,<!--
-->·و·کمی·نوشتنن·عربی·<!--
-->and·some·complex·LTR.</pre>
<dt>‘<code class=css>word-break: break-all</code>’
<dd>
- <pre>这·是·一·些·汉·字·a·n·d·s·o·m·e·L·a·t·i·n·t·e·x·t,<!--
+ <pre>这·是·一·些·汉·字·a·n·d·s·o·m·e·L·a·t·i·n,<!--
-->·و·ﮐ·ﻤ·ﻰ·ﻧ·ﻮ·ﺷ·ﺘ·ﻦ·ﻋ·ﺮ·ﺑ·ﻰ,·<!--
-->a·n·d·s·o·m·e·c·o·m·p·l·e·x·L·T·R.</pre>
<dt>‘<code class=css>word-break: keep-all</code>’
<dd>
- <pre>这是一些汉字,·and·some·Latin·text,<!--
+ <pre>这是一些汉字,·and·some·Latin,<!--
-->·و·کمی·نوشتنن·عربی,·<!--
-->and·some·complex·LTR.</pre>
</dl>
@@ -1815,9 +1804,8 @@
<dd>An unbreakable "word" may be broken at an arbitrary point if there are
no otherwise-acceptable break points in the line. Shaping characters are
still shaped as if the word were not broken, and grapheme clusters must
- together stay as one unit. If specified together with ‘<code
- class=css>hyphenate</code>’, valid hyphenation takes precedence
- over ‘<code class=css>break-word</code>’ breaking.
+ together stay as one unit. No hyphenation character is inserted at the
+ break point.
</dl>
<p>Break opportunities not part of ‘<code class=css>overflow-wrap:
@@ -1882,9 +1870,9 @@
class=property>match-parent</code>’ (see prose)
</table>
- <p>This property describes how inline contents of a block are horizontally
- aligned if the contents do not completely fill the line box. Values have
- the following meanings:
+ <p>This property describes how inline contents of a block are aligned along
+ the inline axis if the contents do not completely fill the line box.
+ Values have the following meanings:
<dl>
<dt><dfn id=start title="text-align:start">‘<code
@@ -1900,18 +1888,18 @@
<dt><dfn id=left title="text-align:left">‘<code
class=css>left</code>’</dfn>
- <dd>The inline contents are aligned to the left edge of the line box. In
- vertical text, ‘<code class=property>left</code>’ aligns to
- the edge of the line box that would be the start edge for left-to-right
- text.
+ <dd>The inline contents are aligned to the left edge of the line box. (In
+ vertical writing modes, ‘<code class=property>left</code>’
+ aligns to the edge of the line box that would be the start edge for
+ left-to-right text.)
<dt><dfn id=right title="text-align:right">‘<code
class=css>right</code>’</dfn>
- <dd>The inline contents are aligned to the right edge of the line box. In
- vertical text, ‘<code class=property>right</code>’ aligns to
- the edge of the line box that would be the end edge for left-to-right
- text.
+ <dd>The inline contents are aligned to the right edge of the line box. (In
+ vertical writing modes, ‘<code class=property>right</code>’
+ aligns to the edge of the line box that would be the end edge for
+ left-to-right text.)
<dt><dfn id=center title="text-align:center">‘<code
class=css>center</code>’</dfn>
@@ -1930,9 +1918,10 @@
href="http://www.w3.org/TR/CSS21/syndata.html#value-def-string"><span
class=value-inst-string><string></span></a></span></code>’</dfn>
- <dd>The string must be a single character; otherwise the declaration must
- be <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.
- When applied to a table cell, specifies the <dfn
+ <dd>The string must be a single <a href="#character"><i>character</i></a>;
+ otherwise the declaration must be <a
+ href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>. When
+ applied to a table cell, specifies the <dfn
id=alignment-character>alignment character</dfn> around which the cell's
contents will align. See <a href="#character-alignment">below</a> for
further details and how this value combines with keywords.
@@ -1952,11 +1941,11 @@
<dt><dfn id=start-end title="text-align:start end">‘<code
class=css>start end</code>’</dfn>
- <dd>Specifies ‘<code class=css>start</code>’‘<code
- class=css> alignment of the first line and any line immediately after a
- forced line break; and </code>’‘<code
- class=property>end</code>’‘<code class=css> alignment of any
- remaining lines not affected by </code>’text-align-last'.
+ <dd>Specifies ‘<code class=css>start</code>’ alignment of the
+ first line and any line immediately after a forced line break; and
+ ‘<code class=css>end</code>’ alignment of any remaining lines
+ not affected by ‘<a href="#text-align-last0"><code
+ class=property>text-align-last</code></a>’.
</dl>
<p>A block of text is a stack of <a
@@ -1988,14 +1977,15 @@
href="http://dev.w3.org/csswg/css3-text/#white-space-rules">white space
processing rules</a>.
- <h4 id=character-alignment><span class=secno>7.1.1. </span>Details on
- Character-based Alignment in a Table Column</h4>
+ <h4 id=character-alignment><span class=secno>7.1.1. </span>Character-based
+ Alignment in a Table Column</h4>
- <p>When multiple cells in a column have an alignment character specified,
- the alignment character of each such cell in the column is centered along
- a single column-parallel axis and the rest of the text in the column
- shifted accordingly. (Note that the strings do not have to be the same for
- each cell, although they usually are.)
+ <p>When multiple cells in a column have an <a
+ href="#alignment-character"><i>alignment character</i></a> specified, the
+ alignment character of each such cell in the column is centered along a
+ single column-parallel axis and the rest of the text in the column shifted
+ accordingly. (Note that the strings do not have to be the same for each
+ cell, although they usually are.)
<p>If the alignment character appears more than once in the text, the first
instance is used for alignment. If the alignment character does not appear
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-text/Overview.src.html,v
retrieving revision 1.300
retrieving revision 1.301
diff -u -d -r1.300 -r1.301
--- Overview.src.html 10 Jan 2012 01:27:22 -0000 1.300
+++ Overview.src.html 12 Jan 2012 01:48:25 -0000 1.301
@@ -336,12 +336,6 @@
<pre>abbr:lang(ja) { text-transform: full-width; }</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?</p>
-
<p class="issue">CSS may introduce the ability to create custom mapping
tables for less common text transforms, such as by an ''@text-transform''
rule similar to ''@counter-style'' from [[CSS3LIST]], and this mechanism
@@ -385,11 +379,7 @@
<p>Control characters (Unicode class Cc) other than tab (U+0009), line feed
(U+000A), space (U+0020), and the bidi formatting characters (U+202<var>x</var>)
- should be rendered as invisible zero-width characters. UAs may instead treat
- them as visible characters. (Note, however, that this will usually result in
- them being rendered as missing glyphs.)
- <span class="issue">What's the line-breaking behavior? Effects on joining?
- Can we just copy the behavior of some zero-width Unicode character?</span>
+ are ignored for the purpose of rendering.
<h3 id="white-space-collapsing">
White Space Collapsing: the 'text-space-collapse' property</h3>
@@ -769,28 +759,26 @@
For breaking opportunities defined by the boundary between two characters,
the properties on the element containing the boundary control breaking.
<!-- http://lists.w3.org/Archives/Public/www-style/2008Dec/0043.html -->
- <span class="issue">What about Zs outside of U+0020?</span>
For break opportunities given by the first or last character of a
box, the break occurs immediately before/after the box rather than
breaking the box.
- <p class="note">Further information on line breaking conventions can be
- found in
+ <div class="note">
+ <p>Further information on line breaking conventions can be found in
[[JLREQ]] and [[JIS4051]] for Japanese,
[[ZHMARK]] for Chinese, and
in [[!UAX14]] for all scripts in Unicode.
<!-- The CSS Working Group notes that although UAX 14 contains a wealth of
information about line breaking conventions, a literal implementation
- of its algorithm has been found to be inadequate in multiple situations. --></p>
-
- <p class="issue">Any guidance for appropriate references here would be
- much appreciated.</p>
+ of its algorithm has been found to be inadequate in multiple situations. -->
- <p class="issue">It is not clear whether this section handles Southeast Asian
- scripts well. Additionally, some guidance should be provided on how to
- break or not break Southeast Asian in the absence of a dictionary.
- (See e.g. <a href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">notes on Thai</a>.)</p>
+ <p class="issue">Any guidance for appropriate references here would be
+ much appreciated.
+ <!-- Additionally, some guidance could be provided on how
+ to break or not break Southeast Asian in the absence of a dictionary.
+ (See e.g. <a href="http://lists.w3.org/Archives/Public/www-style/2011Feb/0126.html">notes on Thai</a>.) -->
+ </div>
<p>Floated and absolutely-positioned elements do not introduce a line
breaking opportunity. The line breaking behavior of a replaced element
@@ -978,24 +966,24 @@
<div class="example">
<p>Here's a mixed-script sample text:
- <pre>这是一些汉字, and some Latin text,<!--
+ <pre>这是一些汉字, and some Latin,<!--
--> و کمی نوشتنن عربی, <!--
-->and some complex LTR.</pre>
<p>The break-points are determined as follows (indicated by ‘·’):
<dl>
<dt>''word-break: normal''</dt>
<dd>
- <pre>这·是·一·些·汉·字,·and·some·Latin·text,<!--
+ <pre>这·是·一·些·汉·字,·and·some·Latin,<!--
-->·و·کمی·نوشتنن·عربی·<!--
-->and·some·complex·LTR.</pre>
<dt>''word-break: break-all''</dt>
<dd>
- <pre>这·是·一·些·汉·字·a·n·d·s·o·m·e·L·a·t·i·n·t·e·x·t,<!--
+ <pre>这·是·一·些·汉·字·a·n·d·s·o·m·e·L·a·t·i·n,<!--
-->·و·ﮐ·ﻤ·ﻰ·ﻧ·ﻮ·ﺷ·ﺘ·ﻦ·ﻋ·ﺮ·ﺑ·ﻰ,·<!--
-->a·n·d·s·o·m·e·c·o·m·p·l·e·x·L·T·R.</pre>
<dt>''word-break: keep-all''</dt>
<dd>
- <pre>这是一些汉字,·and·some·Latin·text,<!--
+ <pre>这是一些汉字,·and·some·Latin,<!--
-->·و·کمی·نوشتنن·عربی,·<!--
-->and·some·complex·LTR.</pre>
</dl>
@@ -1271,8 +1259,7 @@
there are no otherwise-acceptable break points in the line.
Shaping characters are still shaped as if the word were not
broken, and grapheme clusters must together stay as one unit.
- If specified together with ''hyphenate'', valid hyphenation
- takes precedence over ''break-word'' breaking.</dd>
+ No hyphenation character is inserted at the break point.
</dl>
<p>Break opportunities not part of ''overflow-wrap: normal'' line breaking
@@ -1328,9 +1315,9 @@
</tbody>
</table>
- <p>This property describes how inline contents of a block are horizontally aligned
- if the contents do not completely fill the line box. Values have the following
- meanings:</p>
+ <p>This property describes how inline contents of a block are aligned along
+ the inline axis if the contents do not completely fill the line box.
+ Values have the following meanings:</p>
<dl>
<dt><dfn title="text-align:start">''start''</dfn></dt>
@@ -1339,12 +1326,12 @@
<dd>The inline contents are aligned to the end edge of the line box.
<dt><dfn title="text-align:left">''left''</dfn></dt>
<dd>The inline contents are aligned to the left edge of the line box.
- In vertical text, 'left' aligns to the edge of the line box that
- would be the start edge for left-to-right text.</dd>
+ (In vertical writing modes, 'left' aligns to the edge of the line box
+ that would be the start edge for left-to-right text.)</dd>
<dt><dfn title="text-align:right">''right''</dfn></dt>
<dd>The inline contents are aligned to the right edge of the line box.
- In vertical text, 'right' aligns to the edge of the line box that
- would be the end edge for left-to-right text.</dd>
+ (In vertical writing modes, 'right' aligns to the edge of the line box
+ that would be the end edge for left-to-right text.)</dd>
<dt><dfn title="text-align:center">''center''</dfn></dt>
<dd>The inline contents are centered within the line box.
<dt><dfn title="text-align:justify">''justify''</dfn></dt>
@@ -1353,8 +1340,8 @@
<dt><dfn title="text-align:<string>">''<span title="<string>"><a
class="noxref" href="http://www.w3.org/TR/CSS21/syndata.html#value-def-string"
><span class="value-inst-string"><string></span></a></span>''</dfn></dt>
- <dd>The string must be a single character; otherwise the declaration must
- be <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.
+ <dd>The string must be a single <i>character</i>; otherwise the declaration
+ must be <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.
When applied to a table cell, specifies the <dfn>alignment character</dfn>
around which the cell's contents will align. See
<a href="#character-alignment">below</a> for further details and
@@ -1365,7 +1352,7 @@
'start' or 'end' keyword is calculated against its parent's 'direction'
value and results in a computed value of either 'left' or 'right'.
<dt><dfn title="text-align:start end">''start end''</dfn>
- <dd>Specifies ''start''' alignment of the first line and any line
+ <dd>Specifies ''start'' alignment of the first line and any line
immediately after a forced line break; and ''end'' alignment of
any remaining lines not affected by 'text-align-last'.
</dl>
@@ -1391,9 +1378,9 @@
<a href="http://dev.w3.org/csswg/css3-text/#white-space-rules">white
space processing rules</a>.
- <h4 id="character-alignment">Details on Character-based Alignment in a Table Column</h4>
+ <h4 id="character-alignment">Character-based Alignment in a Table Column</h4>
- <p>When multiple cells in a column have an alignment character specified,
+ <p>When multiple cells in a column have an <i>alignment character</i> specified,
the alignment character of each such cell in the column is centered along
a single column-parallel axis and the rest of the text in the column
shifted accordingly. (Note that the strings do not have to be the same
Received on Thursday, 12 January 2012 01:48:34 UTC