Hello, On Aug 21 07:54 Per Jessen wrote (shortened):
Brian K. White wrote:
But that very statement about flowing to fit any window makes me think that it should be no problem for a browser or plug-in to simply re-render the page in an imaginary window that has the same properties as a printed sheet
Exactly. In particular since CUPS exist, any application can get the whole PPD file for a particular print queue (even for remote print queues) from the cupsd and the PPD file contains all necessary information about the capabilities of the output device, in particular - imageable area (the media size is wrong and useless!) - color or monochrome - resolution And if the application likes to produce generic output (i.e. output which is not specific for a particular printer) it could use its own generic PPD file (also as fallback if no CUPS is available - e.g. on a system with LPRng).
... the browser shouldn't be getting all the blame.
Not all the blame but almost all the blame. In particular usual HTML text intermixed with usual images could be printed perfectly. I see only problems when there is dynamically changing stuff in the HTML, e.g. sequences of images ("movies"). In this case I think that the HTML must somehow contain information which one of the sequence of images is the right one which should appear on a "fixed" printout or provide an alternative fixed image for printout. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org