11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
22<html lang="en">
3- <!-- $Id: print.src,v 1.8 1997-09-24 22:14:02 ian Exp $ -->
3+ <!-- $Id: print.src,v 1.9 1997-10-01 22:30:38 ian Exp $ -->
44<HEAD>
55<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
66<TITLE>Printing with style sheets</TITLE>
@@ -43,8 +43,8 @@ many forms of multimedia.
4343While they may contain both text, graphics, and images, they may not
4444contain video, animation, or sound.
4545
46- <P>The best web pages for screen display make the worst web pages for
47- print<i>. Therefore, the most active web pages must be converted to
46+ <P>The best Web pages for screen display make the worst Web pages for
47+ print<i>. Therefore, the most active Web pages must be converted to
4848static pages prior to printing.</i> If this is not done just right,
4949the intent of the author may be distorted and critical information may
5050be lost. If the information is not too significant, then perhaps this
@@ -65,48 +65,12 @@ features does not lend itself to a single, universal solution. Rather
6565a range of solutions is required to meet the various needs of many
6666types of Web publishers.
6767
68- <H2>The page model </H2>
68+ <H2><a name=" page-breaks">Page breaks</a> </H2>
6969
70- <P>In the previous section, we defined the term <span
71- class="index-inst" title="canvas">"canvas"</span> as a surface with a
72- fixed width but infinitely long. In order to cope with printing, we
73- introduce the notion of the <span class="index-def"
74- title="page"><em>page</em></span>, which is a rectangular surface
75- (i.e., fixed width and fixed height. The following sections describe
76- mechanisms that authors may use to tell user agents how to alter the
77- <a href="./flowobj.html">visual flow model</a> so that elements are
78- correctly positioned on individual pages.
79-
80- <P>Note that a "page" is an abstract rectangle that may or may not
81- correspond to the size of a physical "sheet" of paper. Once a page has
82- been formatted, it is the user agent's responsibility to transfer
83- pages to paper. The transfer may vary in complexity. Some transfer
84- possibilities include:
85-
86- <ul>
87- <li>One page to one sheet of paper.
88- <li>Two pages to one sheet of paper (double-sided printing).
89- <li>N (small) pages to one sheet of paper (called <span
90- class="index-def" title="n-up"><em>n-up</em></span>
91- printing).
92- <li>One (large) page to N x M sheets of paper (called "tiling").
93- <li>Signatures (a group of pages
94- printed on a sheet, which, when folded and trimmed like a book, appear in their
95- proper sequence).
96- <li>Printing to alternate paper trays.
97- <li>Printing to a file.
98- </ul>
99-
100- <P>The transfer mechanism from page to sheet lies beyond the scope of
101- this specification. However, the user agent does need to target
102- a certain size and orientation when printing, and this is known as the
103- <span class="index-def" title="print target"><EM>print
104- target</EM></span>. The user will typically set set the target size
105- and orientation in the <EM>Print</EM> dialogue box of the UA. There
106- will often, but not always, be a correlation between the target size
107- and the sheet size.
108-
109- <H2>Page breaks</H2>
70+ <P>The following sections describe mechanisms that authors may use to
71+ tell user agents how to alter the <a href="./flowobj.html">visual flow
72+ model</a> so that elements are correctly positioned on individual <a
73+ href="./convent.html#page">pages</a>.
11074
11175<P>Four properties indicate where the UA may or should break pages, and on
11276what page (left or right) the subsequent content should resume. These
0 commit comments