W3C home > Mailing lists > Public > public-css-commits@w3.org > March 2012

csswg/css3-page-template Overview.html,1.1,1.2 Overview.src.html,1.5,1.6

From: Alan Stearns via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 03 Mar 2012 16:59:49 +0000
To: public-css-commits@w3.org
Message-Id: <E1S3sJB-0006hU-W4@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-page-template
In directory hutz:/tmp/cvs-serv25742/css3-page-template

Modified Files:
	Overview.html Overview.src.html 
Log Message:
fixed typos and added www-style para

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-page-template/Overview.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Overview.html	3 Mar 2012 02:24:49 -0000	1.1
+++ Overview.html	3 Mar 2012 16:59:47 -0000	1.2
@@ -223,8 +223,7 @@
               margin-right:0.8em;
               text-transform:uppercase;      
           }
-              .separate-pre {
-      --margin: 5%;
+    .separate-pre {
       background-color: rgba(0, 0, 0, 0.08);
     }
   </style>
@@ -305,10 +304,39 @@
    until all of the content is displayed.
 
   <h2 class="no-num no-toc" id=status>Status of this document</h2>
+  <!--begin-status-->
 
-  <p><strong>This document is only an Editor's Draft. It has not yet been
-   adopted by the Working Group, and should not be considered to be part of
-   CSS.</strong>
+  <p>This is a public copy of the editors' draft. It is provided for
+   discussion only and may change at any moment. Its publication here does
+   not imply endorsement of its contents by W3C. Don't cite this document
+   other than as work in progress.
+
+  <p>The (<a
+   href="http://lists.w3.org/Archives/Public/www-style/">archived</a>) public
+   mailing list <a
+   href="mailto:www-style@w3.org?Subject=%5Bcss3-page-template%5D%20PUT%20SUBJECT%20HERE">
+   www-style@w3.org</a> (see <a
+   href="http://www.w3.org/Mail/Request">instructions</a>) is preferred for
+   discussion of this specification. When sending e-mail, please put the text
+   &#8220;css3-page-template&#8221; in the subject, preferably like this:
+   &#8220;[<!---->css3-page-template<!---->] <em>&hellip;summary of
+   comment&hellip;</em>&#8221;
+
+  <p>This document was produced by the <a href="/Style/CSS/members">CSS
+   Working Group</a> (part of the <a href="/Style/">Style Activity</a>).
+
+  <p>This document was produced by a group operating under the <a
+   href="/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent
+   Policy</a>. W3C maintains a <a href="/2004/01/pp-impl/32061/status"
+   rel=disclosure>public list of any patent disclosures</a> made in
+   connection with the deliverables of the group; that page also includes
+   instructions for disclosing a patent. An individual who has actual
+   knowledge of a patent which the individual believes contains <a
+   href="/Consortium/Patent-Policy-20040205/#def-essential">Essential
+   Claim(s)</a> must disclose the information in accordance with <a
+   href="/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the
+   W3C Patent Policy</a>.</p>
+  <!--end-status-->
 
   <p>The following features are at risk: none
 
@@ -408,7 +436,8 @@
    href="#CSS3-REGIONS"
    rel=biblioentry>[CSS3-REGIONS]<!--{{CSS3-REGIONS}}--></a>.
 
-  <p>This module uses the overflow-style property from [[CSS3-GCPM]].
+  <p>This module uses the overflow-style property from <a href="#CSS3GCPM"
+   rel=biblioentry>[CSS3GCPM]<!--{{CSS3GCPM}}--></a>.
 
   <p>Some examples use positioning from <a href="#CSS3GRID"
    rel=biblioentry>[CSS3GRID]<!--{{CSS3GRID}}--></a>.
@@ -421,8 +450,8 @@
    pagination templates if its &lsquo;<code
    class=property>overflow-style</code>&rsquo; property is set to any of the
    paged-* values defined in css3-gcpm. If a document defines no pagination
-   templates, then there is an implicit paginated template with a single slot
-   containing the paginated element's contents.
+   templates, then there is an implicit pagination template with a single
+   slot containing the paginated element's contents.
 
   <div class=issue-marker>
    <div class=issue-details>Do pagination templates get their size (and other
@@ -431,13 +460,13 @@
     100%/100% size based on the element's box?</div>
   </div>
 
-  <p>A slot is an anonymous box in a paginated template where content can be
+  <p>A slot is an anonymous box in a pagination template where content can be
    placed. In an @template rule @slot rules create slots. The order of @slot
-   rules determines the order of the boxes in the paginated template. Each
+   rules determines the order of the boxes in the pagination template. Each
    @slot rule can take an optional name.
 
   <p>Slots default to displaying the content of the paginated element. Slots
-   can instead contain generated content assigned from the content property.
+   can instead contain generated content assigned with the content property.
    Slots can also be assigned content from named flows.
 
   <div class=example>
@@ -472,12 +501,12 @@
 
   <div class=example>
    <p>The simplest example takes all of the content in the document and flows
-    it into a single paginated template with a single slot. This template
+    it into a single pagination template with a single slot. This template
     will display a viewport's worth of content at a time, and will create a
     new slot on a new page each time content overflows.
 
    <p>The three examples below are equivalent, but merely illustrate how
-    content from the element can be assigned to paginated template slots.
+    content from the element can be assigned to pagination template slots.
     Actual use of templates would either define more slots or assign content
     differently than the default.
 
@@ -520,14 +549,14 @@
   </div>
 
   <div class=example>
-   <p>A paginated template could contain two side-by-side slots that paginate
-    two separate articles. Side-by-side translations are often laid out this
-    way. This example fills the left side of the paged view with content from
-    an English article and the right side with content from a French article.
-    New pages and slots are created until the content from both articles is
-    exhausted. If one article is longer than the other then in this simple
-    example template the longer article will continue taking up just its half
-    of the page.
+   <p>A pagination template could contain two side-by-side slots that
+    paginate two separate articles. Side-by-side translations are often laid
+    out this way. This example fills the left side of the paged view with
+    content from an English article and the right side with content from a
+    French article. New pages and slots are created until the content from
+    both articles is exhausted. If one article is longer than the other then
+    in this simple example template the longer article will continue taking
+    up just its half of the page.
 
    <p> <img alt="side-by-side flows on a page"
     src="images/side-by-side-1.png" width=120> <span
@@ -645,7 +674,7 @@
    </div>
 
    <div class=issue-marker>
-    <div class=issue-details>One way of promoting re-use of paginated
+    <div class=issue-details>One way of promoting re-use of pagination
      templates would be to parameterize the named flow idents. Instead of
      using named flow idents directly, @slot rules could use a parameter and
      a paginated element using the template would pass in the particular
@@ -660,9 +689,9 @@
    a separate template for pages that match the selector.
 
   <div class=issue-marker>
-   <div class=issue-details>Should we use :left and :right and allow viewing
-    more than one page at a time in a viewport? Should we have :nth(x)
-    selectors?</div>
+   <div class=issue-details>Should :left and :right be allowed with a way of
+    displaying more than one page at a time in a viewport? Should :nth(x)
+    selectors be allowed?</div>
   </div>
 
   <div class=issue-marker>
@@ -922,6 +951,16 @@
     </dd>
    <!---->
 
+   <dt id=CSS3GCPM>[CSS3GCPM]
+
+   <dd>H&#229;kon Wium Lie. <a
+    href="http://www.w3.org/TR/2010/WD-css3-gcpm-20100608"><cite>CSS
+    Generated Content for Paged Media Module.</cite></a> 8 June 2010. W3C
+    Working Draft. (Work in progress.) URL: <a
+    href="http://www.w3.org/TR/2010/WD-css3-gcpm-20100608">http://www.w3.org/TR/2010/WD-css3-gcpm-20100608</a>
+    </dd>
+   <!---->
+
    <dt id=CSS3GRID>[CSS3GRID]
 
    <dd>Alex Mogilevsky; Markus Mielke. <a

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-page-template/Overview.src.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- Overview.src.html	3 Mar 2012 02:24:49 -0000	1.5
+++ Overview.src.html	3 Mar 2012 16:59:47 -0000	1.6
@@ -223,8 +223,7 @@
               margin-right:0.8em;
               text-transform:uppercase;      
           }
-              .separate-pre {
-      --margin: 5%;
+    .separate-pre {
       background-color: rgba(0, 0, 0, 0.08);
     }
   </style>
@@ -275,9 +274,12 @@
 
 <h2 class="no-num no-toc" id="status">Status of this document</h2>
 
-<p><strong>This document is only an Editor's Draft. It has not yet been adopted by the Working Group, and should not be considered to be part of CSS.</strong></p>
+<!--begin-status-->       
+  <p><strong>This document is only an Editor's Draft. It is provided for discussion only and may change at any moment. It has not yet been adopted by the Working Group, and should not be considered to be part of CSS.</strong>
 
-<p>The following features are at risk: none
+  <p>The archived public mailing list www-style@w3.org is preferred for discussion of this specification. When sending e-mail, please put the text "css3-page-template" in the subject, preferably like this: "[css3-page-template] …summary of comment…"
+<!--end-status-->
+  <p>The following features are at risk: none
 
 <h2 class="no-num no-toc" id="contents">Table of contents</h2>
 
@@ -302,19 +304,19 @@
 Module Interactions</h3>
 
   <p>This module uses named flows and region chains defined in [[CSS3-REGIONS]].
-  <p>This module uses the overflow-style property from [[CSS3-GCPM]].
+  <p>This module uses the overflow-style property from [[CSS3GCPM]].
   <p>Some examples use positioning from [[CSS3GRID]].
 
 <h2 id="templates-and-slots">
 Pagination Templates and Slots</h2>
 
-  <p>An @template rule defines a pagination template. Pagination templates contain one or more slots to display content. An element can use pagination templates if its 'overflow-style' property is set to any of the paged-* values defined in css3-gcpm. If a document defines no pagination templates, then there is an implicit paginated template with a single slot containing the paginated element's contents.
+  <p>An @template rule defines a pagination template. Pagination templates contain one or more slots to display content. An element can use pagination templates if its 'overflow-style' property is set to any of the paged-* values defined in css3-gcpm. If a document defines no pagination templates, then there is an implicit pagination template with a single slot containing the paginated element's contents.
 
   <div class="issue-marker"><div class="issue-details">Do pagination templates get their size (and other characteristics) from the element with the overflow-style property, or does this have be set in the @template rule? Can templates use a default 100%/100% size based on the element's box?</div></div>
 
-  <p>A slot is an anonymous box in a paginated template where content can be placed. In an @template rule @slot rules create slots. The order of @slot rules determines the order of the boxes in the paginated template. Each @slot rule can take an optional name.
+  <p>A slot is an anonymous box in a pagination template where content can be placed. In an @template rule @slot rules create slots. The order of @slot rules determines the order of the boxes in the pagination template. Each @slot rule can take an optional name.
 
-  <p>Slots default to displaying the content of the paginated element. Slots can instead contain generated content assigned from the content property. Slots can also be assigned content from named flows.
+  <p>Slots default to displaying the content of the paginated element. Slots can instead contain generated content assigned with the content property. Slots can also be assigned content from named flows.
 
   <div class='example'>
     <p>An @template rule that creates header and footer slots around the paginated element's content
@@ -332,9 +334,9 @@
   <div class="issue-marker"><div class="issue-details">If there is more than one slot with no 'content' or 'flow-from' assignment, does the element's content use all of these slots like a region chain, or is only the last unassigned slot used for content?</div></div>
 
   <div class='example'>
-    <p>The simplest example takes all of the content in the document and flows it into a single paginated template with a single slot. This template will display a viewport's worth of content at a time, and will create a new slot on a new page each time content overflows.
+    <p>The simplest example takes all of the content in the document and flows it into a single pagination template with a single slot. This template will display a viewport's worth of content at a time, and will create a new slot on a new page each time content overflows.
 
-    <p>The three examples below are equivalent, but merely illustrate how content from the element can be assigned to paginated template slots. Actual use of templates would either define more slots or assign content differently than the default.
+    <p>The three examples below are equivalent, but merely illustrate how content from the element can be assigned to pagination template slots. Actual use of templates would either define more slots or assign content differently than the default.
 
     <pre class='separate-pre'>
     body { overflow-style: paged-x; }</pre>
@@ -358,7 +360,7 @@
   <div class="issue-marker"><div class="issue-details">Is there a need to create more structure, nesting slots within slots? If so, then slots can also have layout method declarations?</div></div>
 
   <div class='example'>
-    <p>A paginated template could contain two side-by-side slots that paginate two separate articles. Side-by-side translations are often laid out this way. This example fills the left side of the paged view with content from an English article and the right side with content from a French article. New pages and slots are created until the content from both articles is exhausted. If one article is longer than the other then in this simple example template the longer article will continue taking up just its half of the page.
+    <p>A pagination template could contain two side-by-side slots that paginate two separate articles. Side-by-side translations are often laid out this way. This example fills the left side of the paged view with content from an English article and the right side with content from a French article. New pages and slots are created until the content from both articles is exhausted. If one article is longer than the other then in this simple example template the longer article will continue taking up just its half of the page.
     <p>
     <img src="images/side-by-side-1.png" width="120" alt="side-by-side flows on a page">
     <span style="font-size:50px">…</span>
@@ -450,7 +452,7 @@
 
   <div class="issue-marker wrapper">
   <div class="issue-marker"><div class="issue-details">Instead of specifying a template-set, should there be a way of scoping @template rules to an element? The reason to put them on the document is to re-use pagination templates with multiple elements.</div></div>
-  <div class="issue-marker"><div class="issue-details">One way of promoting re-use of paginated templates would be to parameterize the named flow idents. Instead of using named flow idents directly, @slot rules could use a parameter and a paginated element using the template would pass in the particular named flow ident meant for that parameter.</div></div>
+  <div class="issue-marker"><div class="issue-details">One way of promoting re-use of pagination templates would be to parameterize the named flow idents. Instead of using named flow idents directly, @slot rules could use a parameter and a paginated element using the template would pass in the particular named flow ident meant for that parameter.</div></div>
   </div>
   
 <h3 id='ordered-templates'>
@@ -458,7 +460,7 @@
 
   <p>Selectors such as :first can be used on a pagination template to define a separate template for pages that match the selector.
 
-  <div class="issue-marker"><div class="issue-details">Should we use :left and :right and allow viewing more than one page at a time in a viewport? Should we have :nth(x) selectors?</div></div>
+  <div class="issue-marker"><div class="issue-details">Should :left and :right be allowed with a way of displaying more than one page at a time in a viewport? Should :nth(x) selectors be allowed?</div></div>
 
   <div class="issue-marker"><div class="issue-details">Describe how @template rules with selectors cascade.</div></div>
 
Received on Saturday, 3 March 2012 16:59:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:26:13 UTC