A user informed me that some pages I've created with nested tables are
spewing out dozens of blank pages at the end of a print run. No one
noticed this for a long time, as printer-friendly files are available
elsewhere, and the .htm files are intended for online viewing.

But still, others will click 'print' in the browser window, so I'd
like to stop all that paper from being wasted.

The pages seem to validate okay. Any ideas? Is there an 'end of
file' marker I can add to the code?

Usenet User schrieb:[color=blue]
>
> A user informed me that some pages I've created with nested tables are
> spewing out dozens of blank pages at the end of a print run. No one
> noticed this for a long time, as printer-friendly files are available
> elsewhere, and the .htm files are intended for online viewing.
>
> The pages seem to validate okay. Any ideas? Is there an 'end of
> file' marker I can add to the code?[/color]

URL so we can take a look?


Matthias

"Usenet User" <usenet_user@yahoo.com> wrote in message
news:465f0d47.0310291218.687598ed@posting.google.c om...[color=blue]
> A user informed me that some pages I've created with nested tables are
> spewing out dozens of blank pages at the end of a print run. No one
> noticed this for a long time, as printer-friendly files are available
> elsewhere, and the .htm files are intended for online viewing.
>
> But still, others will click 'print' in the browser window, so I'd
> like to stop all that paper from being wasted.
>
> The pages seem to validate okay. Any ideas? Is there an 'end of
> file' marker I can add to the code?[/color]

My guess (and that's all this is), is that your page extends past the right
margin of the printed page, creating the additional pages. I bet if you
count, you probably have the same number of blank pages as pages with
content. It could be that you have some image or something that extends far
to the right, perhaps right to the edge of the margin, but because of
padding it may be exceeding that margin.

Hope this helps.
Peter Foti

Usenet User wrote:
[color=blue]
> A user informed me that some pages I've created with nested tables are
> spewing out dozens of blank pages at the end of a print run. No one
> noticed this for a long time, as printer-friendly files are available
> elsewhere, and the .htm files are intended for online viewing.
>[/color]

HTML files are actually intended for a multitude of purposes, printing
being one of them. With CSS, you can additionally tailor layout for
each of the media. Nested table-layout is opposing the idea of
separation of form and content, which results in such problems as above.

On Wed, 29 Oct 2003 15:29:55 -0500, "Peter Foti"
<peterf@systolicnetworks.com> wrote:
[color=blue]
>"Usenet User" <usenet_user@yahoo.com> wrote in message
>news:465f0d47.0310291218.687598ed@posting.google. com...[color=green]
>> A user informed me that some pages I've created with nested tables are
>> spewing out dozens of blank pages at the end of a print run. No one
>> noticed this for a long time, as printer-friendly files are available
>> elsewhere, and the .htm files are intended for online viewing.
>>
>> But still, others will click 'print' in the browser window, so I'd
>> like to stop all that paper from being wasted.
>>
>> The pages seem to validate okay. Any ideas? Is there an 'end of
>> file' marker I can add to the code?[/color]
>
>My guess (and that's all this is), is that your page extends past the right
>margin of the printed page, creating the additional pages. I bet if you
>count, you probably have the same number of blank pages as pages with
>content. It could be that you have some image or something that extends far
>to the right, perhaps right to the edge of the margin, but because of
>padding it may be exceeding that margin.[/color]

That sounds like a good guess (it's also possible to imagine situations
where the number of blank pages is exactly 2 or 3 times the number of
content pages - typo on the width of a spacer GIF, for example).

To which I'd add that with judicious use of flexible layout and CSS
print rules one can nearly always avoid the need for separate
printer-friendly pages, which makes things easier for everyone.

--
Stephen Poley

http://www.xs4all.nl/~sbpoley/webmatters/

Thanks for the feedback. I guess I'll have to get in there and squint
at the code; no quick fix on this one. I appreciate the time of
everyone who answered.

usenet_user@yahoo.com (Usenet User) wrote in message news:<465f0d47.0310291218.687598ed@posting.google. com>...[color=blue]
> A user informed me that some pages I've created with nested tables are
> spewing out dozens of blank pages at the end of a print run. No one
> noticed this for a long time, as printer-friendly files are available
> elsewhere, and the .htm files are intended for online viewing.
>
> But still, others will click 'print' in the browser window, so I'd
> like to stop all that paper from being wasted.
>
> The pages seem to validate okay. Any ideas? Is there an 'end of
> file' marker I can add to the code?[/color]