The *browser* knows the page size, or even if there is a screen at all
that can be paginated. Therefore, a make-page-breaks style attribute
would tell the browser to paginate the document to best fit on the screen
it has to work with.
> To use your book metaphor, the hardcover might be twice
> the size of the pages, so the book won't fit on the shelf, except sideways
> maybe. Or the cover might be half the size of the pages, and the pages
> would get frayed.
> You could choose an arbitrary page size, but that would be making many
> assumptions. At least be sure no graphic is wider than 470 pixels, because
> that is the standard imaging area width for Netscape and Mosaic browsers
> when used on screens 640 pixels wide. Anyone with a 512-pixel wide screen
> or smaller would get the wrong size, although they're probably used to it
> already. ;)
Or, the browser could scale down images to fit the page it has to work
with. This is probably a good idea regardless of whether you scroll or
page through the document. Inline images are described as non-essential
decoration, and the style guides I have read suggest using a link to a
full-size image if the graphics are really essential. Therefore I think
it's perfectly fine for the browser to down-size an image to fit the
screen. If I'm not mistaken, the HTML 3 <IMG> tag will let you give
attributes that define a size relative to the browser page, as well as
specifying a size in pixels.
It seems to me that resizing the page and paginating it is a natural
extension of this idea.
-- %%%%%% firstname.lastname@example.org %%%%%% http://www.clark.net/pub/mikebat/www/ %%%%%%