- From: Erik Aronesty <earonesty@montgomery.com>
- Date: Mon, 2 Jun 1997 09:49:50 -0700
- To: "'wlkngowl@unix.asb.com'" <wlkngowl@unix.asb.com>, "'Sarr Blumson'" <sarr@umich.edu>
- Cc: "'www-html@w3.org'" <www-html@w3.org>
Still, there's basically no way to produce attractive, printable reports on the Web. Any document worth reading on a browser is worth printing. The only serious problem with the printablility of reports is the concept of paging. With pages, there is no need to know about paper size/margins or fonts...because it then becomes possible for a browser to intelligently attempt to "fit each page". Secondary problems are paper size, headers and footers. >-----Original Message----- >From: Rob [SMTP:wlkngowl@unix.asb.com] >Sent: Monday, June 02, 1997 12:41 PM >To: Sarr Blumson >Cc: Erik Aronesty; www-html@w3.org >Subject: Re: pages > >"Sarr Blumson" <sarr@umich.edu> wrote: >[..] >> If your suggesting that browsers should be configurable to force a "page >>break" >> on a level one header I would agree completely. I could even deal with a > >I disagree. I (and many others) use H1 on top as a title for the >main-document or group of documents name and H2 for the main >sections. A forced page-break would leave a blank page on top, which >would confuse and turn off a lot of web-surfers. > >> "force new page" tag although I suspect it will end up being grossly >>misused. > >It *will* be misused. > >Better off leavng the use of page breaks along with the handling of >widows and orphans to style-sheets. > >Rob > >--- >Robert Rothenburg Walking-Owl (wlkngowl@unix.asb.com) >Se habla PGP. >http://www.asb.com/usr/wlkngowl
Received on Monday, 2 June 1997 12:59:57 UTC