I'll try to create this style sheet in a few days.

I tested this print style sheet with Firefox, Opera, Safari and IE7, it's only for b2evo_ru skin.

Open _html_header.inc.php and add the following code

<link rel="stylesheet" href="print.css" type="text/css" media="print" />

Then create print.css file with this content and put it in skin folder

body { background:none; background-color: #FFFFFF; padding: 0; margin: 0; color: #000; font: 90% Arial, Helvetica, sans-serif }

a { text-decoration:underline; color: #0066CC }
a:visited { color: #CC3366; }
a:hover { color: #0066FF; }

/* Hide blocks */
div#pageHeader,
.bSideBar,
div#pageFooter,
form.bComment,
.bSmallPrint { display:none; border:none; background:none }

/* Hide border and background */
.block_item_wrap,
.block_item,
.browse_side_item,
.fieldset_title,
.fieldset_title div,
div.PostContent { border:none; background:none; margin:0 }

.bText { color:#000000; font-size:14px }

It's great, thank you!

No problem, do you have a chance to test it on IE6?

Not yet, just IE7 and FF2. I can test it on IE6 tomorrow when I'm at work.

It's not working in some cases. Take a look at this sample from FF 2:

http://www.comiclist.com/printsample.pdf

Yea I know about it, this only happens in FF when the post is longer than the print page.
I have now idea why FF does it and how to fix it.

Ok, done. Change the following

.bText { color:#000000; font-size:14px; overflow:visible }

and also add div#evo_toolbar to the HIDE list, so you won't print your toolbar.

In the /* Hide blocks */ section you probably want to add div#evo_toolbar to hide the toolbar from printing. Dunno if it'll solve your problem though.

Actually I have this funny feeling if you fix a bunch of your xhtml validation errors you might just fix your printing problem in the process. For example there is a table that never has a corresponding /table, and a table without a td in it. A couple of divs without a /div to snuggle up to really messes with the universe too. Not sure how many of these go to the printing issue, but yeah start with making your page valid code.

http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.comiclist.com%2Findex.php%2Fnews%2Fdiamond-aamp-radical-publishing-announce

BTW as a general rule if it breaks in Firefox it's probably not Firefox's fault ;)

Thank you Ed, when I get a chance, I'll try to decipher all those errors and find the missing endings.

And thank you Sam for the css!