- From: H?kon Wium Lie via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 21 Sep 2011 13:24:03 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-gcpm
In directory hutz:/tmp/cvs-serv3706
Modified Files:
Overview.html
Log Message:
x
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-gcpm/Overview.html,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -d -r1.109 -r1.110
--- Overview.html 1 Nov 2010 11:21:07 -0000 1.109
+++ Overview.html 21 Sep 2011 13:24:01 -0000 1.110
@@ -60,11 +60,11 @@
RATIONALE: Removes unused combinations and unnecessary comma
- RESOLVED: Replace image-resolution: auto; with image-resolution: from-image;
- RATIONALE: ‘<code class=property>auto</code>’ vs. ‘<code class=property>normal</code>’ is hard to understand. (‘<code class=property>normal</code>’ is 1 pixel == 1px)
+ RATIONALE: 'auto' vs. 'normal' is hard to understand. ('normal' is 1 pixel == 1px)
- - Discussed removing ‘<code class=property>background-image-resolution</code>’ in favor of various options.
- So far idea is that ‘<code class=property>image-resolution</code>’ applies to all images and we will
+ - Discussed removing 'background-image-resolution' in favor of various options.
+ So far idea is that 'image-resolution' applies to all images and we will
introduce functional notation in the future to allow setting resolution on a
per-image basis.
@@ -99,13 +99,13 @@
<h1>CSS Generated Content for Paged Media Module</h1>
- <h2 class="no-num no-toc" id=w3c-working>Editor's Draft 1 November 2010</h2>
+ <h2 class="no-num no-toc" id=w3c-working>Editor's Draft 21 September 2011</h2>
<dl>
<dt>This version:
<dd><a
- href="http://www.w3.org/TR/2010/ED-css3-gcpm-20101101">http://www.w3.org/TR/2010/ED-css3-gcpm-20101101</a>
+ href="http://www.w3.org/TR/2011/ED-css3-gcpm-20110921/">http://www.w3.org/TR/2011/ED-css3-gcpm-20110921</a>
<dt>Latest version:
@@ -124,7 +124,7 @@
<!--begin-copyright-->
<p class=copyright><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
- rel=license>Copyright</a> © 2010 <a
+ rel=license>Copyright</a> © 2011 <a
href="http://www.w3.org/"><acronym title="World Wide Web
Consortium">W3C</acronym></a><sup>®</sup> (<a
href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute
@@ -328,14 +328,14 @@
<li><a href="#the-float-offset-property"><span class=secno>15.1.
</span>The ‘<code class=property>float-offset</code>’
property</a>
-
- <li><a href="#aligning-baselines"><span class=secno>15.2.
- </span>Aligning baselines</a>
</ul>
- <li><a href="#conformance"><span class=secno>16. </span>Conformance</a>
+ <li><a href="#aligning-baselines-in-multi-column-layou"><span
+ class=secno>16. </span>Aligning baselines in multi-column layouts</a>
- <li><a href="#appendix-a-default-style-sheet"><span class=secno>17.
+ <li><a href="#conformance"><span class=secno>17. </span>Conformance</a>
+
+ <li><a href="#appendix-a-default-style-sheet"><span class=secno>18.
</span>Appendix A: Default style sheet</a>
<li class=no-num><a href="#acknowledgments">Acknowledgments</a>
@@ -1357,7 +1357,7 @@
<p class="note">In published books, it is customary for the footnote
area to be limited to less than half the height of the page area. Long
footnotes may need more space, and the customary solution is for
-footnotes to span several pages. To achieve this, the ‘<code class=property>max-height</code>’
+footnotes to span several pages. To achieve this, the 'max-height'
property should be used. However, footnotes spanning several pages is
an advanced feature which is not a conformance requirement for this
specification.
@@ -1381,9 +1381,7 @@
due to the ‘<code class=property>border-clip</code>’
property, which is defined in <a
href="http://dev.w3.org/csswg/css4-background/">CSS Backgrounds and
- Borders Module Level 4</a>.
- <!--<a href="#CSS4BACKGROUND" rel="biblioentry">[CSS4BACKGROUND]<!--{{!CSS4BACKGROUND}}-->-->.
-
+ Borders Module Level 4</a>. <!--[[!CSS4BACKGROUND]]-->.
</div>
<!--
<p class="issue">Footnotes in tables and floats may be problematic. In
@@ -1453,8 +1451,8 @@
<p class=issue>Should one also be able to manually increment the "footnote"
counter? <!--
-<p>The ‘<code class=property>counter-increment</code>’ property can be set in the @footnote rule.
-Each time an element with ‘<code class=css>float: footnote</code>’ is found, the corresponding
+<p>The 'counter-increment' property can be set in the @footnote rule.
+Each time an element with 'float: footnote' is found, the corresponding
counter is incremented.
<div class="example">
@@ -2228,11 +2226,11 @@
bottom of a page.
<p>This specifiction describes two counters that can be used to
-indicate page numbers: ‘<code class=css>page</code>’ and ‘<code class=css>pages</code>’.
+indicate page numbers: ''page'' and ''pages''.
-<h3>The ‘<code class=css>page</code>’ counter</h3>
+<h3>The ''page'' counter</h3>
-<p>The ‘<code class=css>page</code>’ counter is predefined to start with a value of zero,
+<p>The ''page'' counter is predefined to start with a value of zero,
and to be automatically incremented by one before every page. That is,
UAs must behave as if this code fragment is part of the default style
sheet:
@@ -2243,7 +2241,7 @@
}
</pre>
-<p>The ‘<code class=css>page</code>’ counter can be reset and incremented in style sheets
+<p>The ''page'' counter can be reset and incremented in style sheets
just like other counters. On pages where the counter is incremented by
the style sheet in the page context, the automatic incrementation does
not take place.
@@ -2268,9 +2266,9 @@
</div>
-<h3>The ‘<code class=css>pages</code>’ counter</h3>
+<h3>The ''pages'' counter</h3>
-<p>The ‘<code class=css>pages</code>’ counter is predefined to have the total number of
+<p>The ''pages'' counter is predefined to have the total number of
pages in the document. In order to find the value of this counter, the
UA will have to paginate the document. This counter is a constant and
it cannot be set or incremented by a style sheet.
@@ -2290,8 +2288,8 @@
<div class=example>
-<p>This code has no effect on the ‘<code class=css>pages</code>’ counter which cannot be
-changed by the style sheet. However, the the ‘<code class=css>page</code>’ counter reset normally.
+<p>This code has no effect on the ''pages'' counter which cannot be
+changed by the style sheet. However, the the ''page'' counter reset normally.
<pre>
@page :right {
@@ -2456,12 +2454,12 @@
<dt><dpi>
-<dd>The value consists of a number with a ‘<code class=property>dpi</code>’ unit identifier. The
+<dd>The value consists of a number with a 'dpi' unit identifier. The
UA should use the specified resolution.
</dl>
-<p>If, after evaluating the specified values, no image resolution has been determined, the UA should behave as if ‘<code class=css>normal</code>’ had been specified.
+<p>If, after evaluating the specified values, no image resolution has been determined, the UA should behave as if ''normal'' had been specified.
<div class="example">
<p>This rule specifies that the UA should use the image resolution found in the image itself.
@@ -2527,7 +2525,7 @@
<p class=issue>Introducing one new property in all places where an image can be loaded may not be a scalable solution. Therefore this property is at risk.
-<p>As ‘<code class=property>image-resolution</code>’, except that it describes the resolution of the element's background image.
+<p>As 'image-resolution', except that it describes the resolution of the element's background image.
-->
@@ -2537,6 +2535,10 @@
<p>The ‘<a href="#marks"><code
class=property>marks</code></a>’ property from <a href="#CSS2"
rel=biblioentry>[CSS2]<!--{{CSS2}}--></a> is part of this specification.
+ <!--
+http://www.w3.org/TR/2008/REC-CSS2-20080411/page.html#propdef-marks
+-->
+
<table class=propdef>
<tbody>
@@ -3043,7 +3045,7 @@
class=property>float</code>’</span> property is extended with
several new values: <!--
-<p>Further, the ‘<code class=property>float</code>’ property is extended to accept a
+<p>Further, the 'float' property is extended to accept a
comma-separated list of sets of keywords. If the first set of keywords
cannot be honored with the element remaining on the current page, the
second set of keywords will determine how the element is floated.
@@ -3077,12 +3079,12 @@
<dt>page
- <dd>Indicates that the page area is the flow root for the element.
+ <dd>Indicates that the page area is the float-root for the element.
<dt>multicol
- <dd>Indicates that the multicol element is the flow root for the element.
-
+ <dd>Indicates that the multicol element is the float-root for the
+ element.
<dt>intrude
@@ -3289,7 +3291,7 @@
<div class=example>
<pre class=css>
-img { float: left; width: 120% }
+img { float: left intrude; width: 120%; }
</pre>
<p>In this example, the image is wider than the column and will therefore
@@ -3349,7 +3351,7 @@
<div class=example>
<pre class=css>
-img { float: right; width: 120% }
+img { float: right intrude; width: 120% }
</pre>
<p>In this example, the image naturally appears in the last column. Due
@@ -3536,8 +3538,8 @@
class=property>float-offset</code></a>’ is a good concept for
moving a float into the right position. For completeness it should apply
to absolute positioning as well. We should reuse existing naming
- conventions already in place for abspos elements (e.g., 'offset-left,
- ‘<code class=property>right</code>’, or call it ‘<code
+ conventions already in place for abspos elements (e.g., ‘<code
+ class=css>offset-left, </code>’right', or call it ‘<code
class=css>shift left, </code>’shift right' etc.).
<div class=example>
@@ -3994,8 +3996,8 @@
</div>
- <h3 id=aligning-baselines><span class=secno>15.2. </span>Aligning
- baselines</h3>
+ <h2 id=aligning-baselines-in-multi-column-layou><span class=secno>16.
+ </span>Aligning baselines in multi-column layouts</h2>
<p>In multi-column layouts, baselines are typically aligned between
adjacent columns. This gives the presentation a visual rythm, and text in
@@ -4039,10 +4041,10 @@
class=property>line-stacking-strategy</code>’ property is <a
href="http://www.w3.org/TR/xsl/#line-stacking-strategy">used in XSL</a>.
- <h2 id=conformance><span class=secno>16. </span>Conformance</h2>
+ <h2 id=conformance><span class=secno>17. </span>Conformance</h2>
<!--User agents that support hyphenation and support this specification must a-->
- <h2 id=appendix-a-default-style-sheet><span class=secno>17.
+ <h2 id=appendix-a-default-style-sheet><span class=secno>18.
</span>Appendix A: Default style sheet</h2>
<p class=issue>
@@ -4095,21 +4097,11 @@
<dt id=CSS3LIST>[CSS3LIST]
- <dd>Ian Hickson; Tantek Çelik. <a
- href="http://www.w3.org/TR/2002/WD-css3-lists-20021107"><cite>CSS3
- module: Lists.</cite></a> 7 November 2002. W3C Working Draft. (Work in
- progress.) URL: <a
- href="http://www.w3.org/TR/2002/WD-css3-lists-20021107">http://www.w3.org/TR/2002/WD-css3-lists-20021107</a>
- </dd>
- <!---->
-
- <dt id=CSS4BACKGROUND>[CSS4BACKGROUND]
-
- <dd>Elika J. Etemad; Håkon Wium Lie. <a
- href="http://dev.w3.org/csswg/css4-background/"><cite>CSS Backgrounds
- and Borders Module Level 4.</cite></a> Proposal for a CSS module.
- (Retrieved 2 June 2010) URL: <a
- href="http://dev.w3.org/csswg/css4-background/">http://dev.w3.org/csswg/css4-background/</a>
+ <dd>Tab Atkins Jr. <a
+ href="http://www.w3.org/TR/2011/WD-css3-lists-20110524"><cite>CSS Lists
+ and Counters Module Level 3.</cite></a> 24 May 2011. W3C Working Draft.
+ (Work in progress.) URL: <a
+ href="http://www.w3.org/TR/2011/WD-css3-lists-20110524">http://www.w3.org/TR/2011/WD-css3-lists-20110524</a>
</dd>
<!---->
</dl>
@@ -4133,16 +4125,16 @@
<dt id=CSS3COL>[CSS3COL]
<dd>Håkon Wium Lie. <a
- href="http://www.w3.org/TR/2009/CR-css3-multicol-20091217"><cite>CSS
- Multi-column Layout Module.</cite></a> 17 December 2009. W3C Candidate
+ href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412"><cite>CSS
+ Multi-column Layout Module.</cite></a> 12 April 2011. W3C Candidate
Recommendation. (Work in progress.) URL: <a
- href="http://www.w3.org/TR/2009/CR-css3-multicol-20091217">http://www.w3.org/TR/2009/CR-css3-multicol-20091217</a>
+ href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412">http://www.w3.org/TR/2011/CR-css3-multicol-20110412</a>
</dd>
<!---->
<dt id=CSS3PAGE>[CSS3PAGE]
- <dd>Melinda Grant; Håkon Wium Lie. <a
+ <dd>Håkon Wium Lie; Melinda Grant. <a
href="http://www.w3.org/TR/2006/WD-css3-page-20061010"><cite>CSS3
Module: Paged Media.</cite></a> 10 October 2006. W3C Working Draft.
(Work in progress.) URL: <a
@@ -4226,8 +4218,8 @@
<th>Media
<tbody>
- <tr valign=baseline>
- <td><a class=property href="#bleed">bleed</a>
+ <tr>
+ <th><a class=property href="#bleed">bleed</a>
<td><length>
@@ -4241,8 +4233,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#bookmark-label">bookmark-label</a>
+ <tr>
+ <th><a class=property href="#bookmark-label">bookmark-label</a>
<td>content() | attr() | <string>
@@ -4256,8 +4248,8 @@
<td>all
- <tr valign=baseline>
- <td><a class=property href="#bookmark-level">bookmark-level</a>
+ <tr>
+ <th><a class=property href="#bookmark-level">bookmark-level</a>
<td>none | <integer>
@@ -4271,8 +4263,8 @@
<td>all
- <tr valign=baseline>
- <td><a class=property href="#bookmark-state">bookmark-state</a>
+ <tr>
+ <th><a class=property href="#bookmark-state">bookmark-state</a>
<td>open | closed
@@ -4286,8 +4278,8 @@
<td>all
- <tr valign=baseline>
- <td><a class=property href="#bookmark-target">bookmark-target</a>
+ <tr>
+ <th><a class=property href="#bookmark-target">bookmark-target</a>
<td>none | <uri> | <attr>
@@ -4301,8 +4293,8 @@
<td>all
- <tr valign=baseline>
- <td><a class=property href="#float-offset">float-offset</a>
+ <tr>
+ <th><a class=property href="#float-offset">float-offset</a>
<td><length> <length> ?
@@ -4316,8 +4308,8 @@
<td>visual, paged
- <tr valign=baseline>
- <td><a class=property href="#hyphenate-after">hyphenate-after</a>
+ <tr>
+ <th><a class=property href="#hyphenate-after">hyphenate-after</a>
<td><integer> | auto
@@ -4331,8 +4323,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#hyphenate-before">hyphenate-before</a>
+ <tr>
+ <th><a class=property href="#hyphenate-before">hyphenate-before</a>
<td><integer> | auto
@@ -4346,8 +4338,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property
+ <tr>
+ <th><a class=property
href="#hyphenate-character">hyphenate-character</a>
<td>auto | <string>
@@ -4362,8 +4354,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property
+ <tr>
+ <th><a class=property
href="#hyphenate-last-line-avoid">hyphenate-last-line-avoid</a>
<td>auto | always | column | page | spread
@@ -4378,8 +4370,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#hyphenate-lines">hyphenate-lines</a>
+ <tr>
+ <th><a class=property href="#hyphenate-lines">hyphenate-lines</a>
<td>no-limit | <integer>
@@ -4393,8 +4385,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#hyphenate-resource">hyphenate-resource</a>
+ <tr>
+ <th><a class=property href="#hyphenate-resource">hyphenate-resource</a>
<td>none | <uri> [, <uri> ]*
@@ -4408,8 +4400,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#hyphens">hyphens</a>
+ <tr>
+ <th><a class=property href="#hyphens">hyphens</a>
<td>none | manual | auto | all
@@ -4423,8 +4415,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#image-resolution0">image-resolution</a>
+ <tr>
+ <th><a class=property href="#image-resolution0">image-resolution</a>
<td>normal | [ from-image || <dpi> ]
@@ -4438,8 +4430,8 @@
<td>visual
- <tr valign=baseline>
- <td><a class=property href="#marks">marks</a>
+ <tr>
+ <th><a class=property href="#marks">marks</a>
<td>[ crop || cross ] | none
@@ -4453,8 +4445,8 @@
<td>visual, paged
- <tr valign=baseline>
- <td><a class=property href="#string-set">string-set</a>
+ <tr>
+ <th><a class=property href="#string-set">string-set</a>
<td>[[ <identifier> <content-list>] [, <identifier>
<content-list>]* ] | none
Received on Wednesday, 21 September 2011 13:24:09 UTC