Skip to content

Commit 61a6e21

Browse files
committed
[css2] Removed printing extensions section
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%40199
1 parent e326b8a commit 61a6e21

1 file changed

Lines changed: 1 addition & 73 deletions

File tree

css2/notes.src

Lines changed: 1 addition & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
22
<html lang="en">
3-
<!-- $Id: notes.src,v 1.8 1997-09-23 14:18:54 ian Exp $ -->
3+
<!-- $Id: notes.src,v 1.9 1997-10-02 16:06:21 ian Exp $ -->
44
<HEAD>
55
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
66
<TITLE>Appendix C: Implementation and performance notes</TITLE>
@@ -277,77 +277,5 @@ tell when a font is being dereferenced, because the URL is inside a
277277
font description. Thus, only the relevant Accept headers need be sent
278278
(not headers related to images, HTML, etc).
279279

280-
<h2>Printing</h2>
281-
282-
<H3>Future extensions</H3>
283-
<p>The following is a short list of where we expect to see additional
284-
work concerning printing.
285-
286-
<ul>
287-
288-
<li>Multi-column Properties.
289-
290-
<li>Additional Page Properties. Documents might contain multiple
291-
sections, each with a different page orientation, headers/footers,
292-
etc. How elements span pages should be better controlled with
293-
widow/orphan control and keep together type properties. Additional
294-
formatting properties such as vertical page alignment and font
295-
kerning.
296-
297-
<li>Media Dependent Elements. It would be much easier for many users
298-
if a separate style sheet did not have to be maintained for each
299-
possible output medium. This would also support inline styles. Can
300-
they be merged so that a media property is associated with each
301-
element or style sheet property? What about properties that apply to
302-
more than one element? How do the various media cascade?
303-
304-
<li>Collections of Pages. The author may define a set of pages that
305-
may be logically printed together, e.g., a catalog or a chapter of a
306-
book. How does a user discover that the author has provided this? Is
307-
there a uniform UI that is presented? Can collections contain other
308-
collections? To what level? Are page relationships defined from a
309-
table of contents type of page or on each page itself? What if a page
310-
belongs to more than one collection? How can print collections be
311-
reconciled with other planned site navigation tools? Do collections
312-
have other uses besides printing, e.g., off line reading?
313-
314-
315-
<li>Headers and Footers. How can those provided by the page author be
316-
reconciled with those desired by the user? What about site wide
317-
headers and footers, logos, and watermarks? Should all information be
318-
propagated even when redundant? Are headers a type of decoration or
319-
style? Is it proper to have headers and footers appear in style
320-
sheets? What if they have content in addition to format, e.g., a
321-
company confidential message as well as page number location? Is there
322-
a collection heading that has priority if the page is printed as part
323-
of an author defined set?
324-
325-
<li>Footnotes. How are footnotes specified within a page? Should we
326-
have a separate method for those at the end of a page as well as those
327-
at the end of a section? Can the user elect to have end of page
328-
footnotes printed at the end of the section anyway? How are footnotes
329-
presented on screen? As a pop-up? Can links to other HTML pages
330-
automatically be treated as footnotes?
331-
332-
<li>Environment Dependent Styles. Can the UA environment automatically
333-
pick an appropriate style? If a high resolution color screen is used,
334-
can it retrieve different images than a low resolution monochrome
335-
screen? Should high resolution printers retrieve a higher resolution
336-
image for printing? What if more than one printer is available? How
337-
does the UA describe the highest quality available for the various
338-
printers? Can certain display devices be paginated, thus presenting
339-
headers, footers, etc.
340-
341-
<li>Finishing Properties. These are the properties associated with a
342-
page to be printed that are required to meet the author's or user's
343-
printing requirements - rendering options, stapling or binding,
344-
impositions, delivery, accounting, media type or grade, form name,
345-
number of copies, etc. Especially useful in third party printing,
346-
shared printers, and intranet print shops. How are these attached to a
347-
document to be printed? Can portions be overridden? What about the
348-
security of the accounting information. Can they be divided into
349-
author and user fields, supplied at different points?
350-
</ul>
351-
352280
</BODY>
353281
</HTML>

0 commit comments

Comments
 (0)