preparing for new wd

Author: howcom

css3-gcpm/Overview.src.html

@@ -33,9 +33,7 @@
 table.border table td { border: thin dotted black; padding: 0.2em; margin: 0.2em  }
 table.border .comment { margin-top: 0; white-space: normal; font-style: italic }
 
-div.out { background: #F55; padding: 0.2em 0.5em }
-div.out div.example { background: #FED }
-h1, h2, h3, h4, h5, h6 { background: transparent }
+
 </style>
 
 
@@ -45,7 +43,20 @@
 
 <!--logo-->
 
-<h1>CSS3 module: Generated Content for Paged Media</h1>
+<!--
+
+align lines: what did michael suggest?
+
+Another approach would be to extend the height of the block to be a 
+multiple of the grid height, but then people would probably want to 
+control where the extra space gets added.
+
+kerning?
+
+
+-->
+
+<h1>CSS Generated Content for Paged Media Module</h1>
 
 <h2 class="no-num no-toc" id="w3c-working">[LONGSTATUS] [DATE]</h2>
 
@@ -92,9 +103,6 @@ <h2 class="no-num no-toc" id=abstract>Abstract</h2>
 <h2 class="no-num no-toc">Status of this document</h2>
 
 <!--begin-status-->
-<p>[If you keep the &lt;!--comment-->, the status boilerplate will be
-included here automatically.]</p>
-<!--end-status-->
 
 <p>This WD describes functionality at various levels of maturity. Some
 features have been part of other WDs in the past and have already been
@@ -103,6 +111,9 @@ <h2 class="no-num no-toc">Status of this document</h2>
 features presented earlier in this draft are more mature that those
 presented later in the draft.
 
+<!--end-status-->
+
+
 
 <h2 class="no-num no-toc"><a name="contents">Table of contents</a></h2>
 
@@ -111,6 +122,7 @@ <h2 class="no-num no-toc"><a name="contents">Table of contents</a></h2>
 included here automatically.]</p>
 <!--end-toc-->
 
+<!--
 <h2 id=dependencies>Dependencies on other modules</h2>
 
 <p>This CSS3 module has normative references to the following other CSS3
@@ -129,7 +141,7 @@ <h2 id=dependencies>Dependencies on other modules</h2>
   <li>[[CSS3PAGE]]</li>
   <li>[[CSS3MULTICOL]]</li>
 </ul>
-
+-->
 
 <h2>Introduction</h2>
 
@@ -378,7 +390,6 @@ <h4>Using named strings</h4>
 assigned a value, the empty string is used.
 
 
-<div class=out>
 <h3>Running elements</h3>
 
 <p>Named strings, as described above, can only hold textual content; any
@@ -483,7 +494,7 @@ <h3>Running elements</h3>
 used on subsequent pages.
 </div>
 
-</div>
+
 
 <h2>Leaders</h2>
 
@@ -766,6 +777,7 @@ <h3>The ''target-text'' value</h3>
 </div>
 
 
+
 <h2>Footnotes</h2>
 
 <p>A footnote is a note typically placed at the bottom of a page that
@@ -1624,7 +1636,6 @@ <h3>The 'border-parts' properties</h3>
 -->
 
 
-<div class=out>
 
 <h2>Pulling elements: the ''target-pull()'' value</h2>
 
@@ -1662,7 +1673,6 @@ <h2>Pulling elements: the ''target-pull()'' value</h2>
 
 
 
-
 <h2>Pushing elements: named flows</h2>
 
 <p>Footnotes and running elements are print-specific conventions that
@@ -1791,7 +1801,6 @@ <h2>Pushing elements: named flows</h2>
 
 </div>
 
-</div>
 
 <h2>Hyphenation</h2>
 
@@ -2088,7 +2097,7 @@ <h3>Hyphenate properties</h3>
 <p class=issue>XSL uses a different list of <a href="http://www.w3.org/TR/2006/CR-xsl11-20060220/#common-hyphenation-properties">properties</a>. Reuse of these properties has been considered.
 -->
 
-<!--
+
 <h2>New counter styles</h2>
 
 <h3>The ''super-decimal'' list-style-type</h3>
@@ -2113,8 +2122,6 @@ <h3>The ''super-decimal'' list-style-type</h3>
 <p>Using super-script glyphs is optional; UAs may also scale and position
 other glyphs for use in footnote calls.
 
-<p class=issue>There are three things this could mean: (a) this implies the use of a font feature if the font has that feature (b) this implies that the counter is translated into the unicode characters (c) the issue of accessing font features should be 
--->
 
 
 <h3>Named counter styles</h3>
@@ -2307,8 +2314,6 @@ <h3>The ''pages'' counter</h3>
 
 -->
 
-<div class=out>
-
 <h2>Character substitution</h2>
 
 <p>It is sometimes convenient to replace one character with another
@@ -2317,12 +2322,7 @@ <h2>Character substitution</h2>
 better to replace it with a quotation character. The 'text-replace'
 property offers a way to perform the replacement in the style sheet.
 
-<p>This property only applies to batch processors.
-
-<!--
 <p class='issue'>It this something CSS should do? Some think it's OK to use CSS for non-stylistic purposes, some think this <em>is</em> is a stylistic purpose, and some think this is not stylistic and should therefore be kept outside of CSS.
--->
-
 
 <h3>The 'text-replace' property</h3>
 
@@ -2443,52 +2443,15 @@ <h3>The 'text-replace' property</h3>
 <p>This property is evaluated after the 'content' property, and before
 'text-transform'.
 
-<p>This property is applied after the 'white-space' property. 
-
-<div class="example">
-<p>Consider this CSS code:
-<pre>
-p { text-replace: "Soviet Union" "Russia"; }
-</pre>
-
-
-<p>Text replacements would occur in both these paragraphs:
-
-<pre>
-&lt;p>Hello Soviet Union!&lt;/p>
-&lt;p>Hello Soviet
-Union!&lt;/p>
-</pre>
-</div>
-
-
-<div class="example">
-<p>Consider this CSS code:
-<pre>
-p { 
-  text-replace: "Soviet Union" "Russia"; 
-  white-space: pre;
-}
-</pre>
-
-<p>Due to the preservation of white space, a text replacement would
-only occur in the first of these paragraphs:
-
-<pre>
-&lt;p>Hello Soviet Union!&lt;/p>
-&lt;p>Hello Soviet
-Union!&lt;/p>
-</pre>
-</div>
-
 <p class="note">This property is very powerful and must be used with
 great care. The purpose of this property is to beautify the
 presentation of text when changing the source document is
 impractical.
 
-
 <div class=issue>
 
+<p>This property has raised some discussions. Some people think it's much powerful, other thinks it's too weak. Some think it doesn't belong in CSS at all.
+
 <p>One weakness is that it is not able to perform a the commonly requested task of replacing pairs of double quotes with proper quote marks. One way of addressing this would be to add support for regular expressions. For example:
 
 <div class="example">
@@ -2521,9 +2484,6 @@ <h3>The 'text-replace' property</h3>
 </div>
 
 
-</div>
-
-
 
 <h2>Image resolution</h2>
 
@@ -2532,8 +2492,9 @@ <h2>Image resolution</h2>
 can record information about the resolution of images. This
 information can be helpful when determining the actual size of the
 image in the formatting process. However, the information can also be
-wrong, in which case it should be ignored. The 'image-resolution'
-property is introduced to determine the correct resolution of images.
+wrong, in which case it should be ignored. The 'image-resolution' and
+'background-image-resolution' properties are introduced to determine
+the correct resolution of images.
 
 <table class=propdef>
     <tr>
@@ -2547,7 +2508,7 @@ <h2>Image resolution</h2>
       <td>normal
     <tr>
       <td><em>Applies to:</em>
-      <td>replaced elements and background images
+      <td>replaced elements <span class=issue>and background images?</span>
     <tr>
       <td><em>Inherited:</em>
       <td>yes
@@ -2559,7 +2520,7 @@ <h2>Image resolution</h2>
       <td>visual
     <tr>
       <td><em>Computed&nbsp;value:</em>
-      <td>a &lt;dpi> value
+      <td>as specified value <span class=issue>(or, should it be only one value?)</span>
 </table>
 
 <p>This property accepts either a single value, or a comma-separated
@@ -2568,7 +2529,7 @@ <h2>Image resolution</h2>
 <dl>
 <dt>normal
 
-<dd>The resolution of the image is unknown, and UAs must not use the
+<dd>The resolution of the image is unknown, and UAs should not use the
 resolution found in the image. Instead, the image resolution will be
 found by making image pixels equivalent to CSS pixels.
 
@@ -2685,7 +2646,7 @@ <h2>Image resolution</h2>
 -->
 
 
-<!--
+
 
 <div class="issue">
 <p>Should there be a way of setting width, height, resolution on images that are referenced by a URL in the style sheet? E.g., 
@@ -2697,7 +2658,6 @@ <h2>Image resolution</h2>
 </div>
 
 
-
 <table class=propdef>
     <tr>
       <td><em>Name:</em>
@@ -2729,7 +2689,6 @@ <h2>Image resolution</h2>
 
 <p>As 'image-resolution', except that it describes the resolution of the element's background image. 
 
--->
 
 <h2>Page marks and bleed area</h2>
 
@@ -2781,7 +2740,7 @@ <h2>Page marks and bleed area</h2>
 <table class=propdef>
     <tr>
       <td><em>Name:</em>
-      <td><dfn>bleed</dfn>
+      <td><dfn>page-bleed</dfn>
     <tr>
       <td><em>Value:</em>
     <td>&lt;length&gt;
@@ -2981,8 +2940,6 @@ <h2>Bookmarks</h2>
 
 <h2>CMYK colors</h2>
 
-<p class=issue>PDF can hold two types of CMYK values: device-specific and color-profile-specific. In the latter case, we may need to point to a color profile.
-
 <p>Printers do not use RGB colors, they (often) use CMYK: cyan,
 magenta, yellow and black. A new functional value allows style sheets
 to express CMYK colors.
@@ -2996,10 +2953,6 @@ <h2>CMYK colors</h2>
 <p>The values representing the colors are between ''0'' and ''1''. 
 Values outside this range are clipped. 
 
-<p>Unless a color profile is specified, the cmyk() value refers to
-device-specific colors. A future version of this specifiction will
-describe how to link to color profiles.
-
 <p>It is not expected that screen-centric user agents support CMYK
 colors and it is therefore important that existing CSS color values can
 be combined with CMYK colors.
@@ -3018,6 +2971,8 @@ <h2>CMYK colors</h2>
 
 <h2>Creating paged presentations</h2>
 
+<p class=issue>This part is still at the brainstorming stage.
+
 <p>Printed publications are paged, while screen-based presentations of
 web pages are most often presented in a continous manner with a
 scrollbar on the side. There are reasons to believe that screen-based
@@ -3331,7 +3286,6 @@ <h2>Page floats</h2>
 width calculations are vice versa.
 
 
-
 <h2>Advanced multi-column layout</h2>
 
 <p>In paged media, it is common for figures, captions, images, and
@@ -4083,7 +4037,6 @@ <h3>The 'page' property</h3>
 </div>
 
 
-<div class=out>
 
 <h2>Continuation markers</h2>
 
@@ -4626,8 +4579,6 @@ <h3>A more complex example</h3>
 </pre>
 </div>
 
-</div>
-
 
 <h2>Conformance</h2>
 
@@ -4664,7 +4615,6 @@ <h2>Appendix A: Default style sheet</h2>
 </pre>
 
 
-
 <h2 class=no-num id=acknowledgments>Acknowledgments</h2>
 
 <p>This document has been improved by Bert Bos, Michael Day, Melinda