Support for print.css

Splendid idea!

The print.css allows page content to be printet without the blocks containing navigation. However, there is room for improvement (althoug I don't know if it is do'able using only a css).. Because, tabs, are still being printed. So is search field and comment links. Please see attached pdf's.

Wow. It looks like its possible to actually make printed webpages look, well, great!

I applied your modified css. Gone are printed tabs, and printed search field and search button. Good work!

Just to see how it would look, I deleted the "times roman 12 point" font override from print.css. What looks best is up to discussion, serif fonts (like times) are known to be more easily readable on print - but I wanted to see how close we could get to the original foliage theme....

Therefore, I also instructed IE to print the background colors. The results are looking very promising. Take a loot at the attachment. I have got two comments:

a) position of site name in the header is off - that might require edit of the page.tpl file??
b) the submit buttons (save changes, reset) are no good on print ;-)

Another thing: Firefox seems to print url's of links in readable form - is that an option somewhere?

Bjarne

I did some hacking on your print.css - below is what i learned, and a sample I'd like you to try out:

a) the false position of the sitename in the header was a result of the print.css hiding the entire table cell with the search form. hiding #search-theme-form instead, hides the seach form, but not the cell, and this positioning is again correct

b) buttons are .form-submit styled - I've hid them as well (could be optional, documented in readme)

c) RSS feed icon is .feed-icon styled - also hidden.

d) body text is again 12point serif font - I have left headers to their original styling, except:

e) text colors are all black - this speeds up printing a lot (at least on our multipass color printer)

f) header and footer looks ok without background image, but shines with background image enabled - I have tried this in IE7 and Firefox 2 in portrait and landscape mode (slows down printing of cause)

g) i have removed extra margins on content, browser adds margins on print as well..

/**
 * New print.css for foliage. v1.1a vjordan and netbjarne
 */

body {
   background: white;
   color: black;
}

p {
   font: 12pt times, serif;
   color: black;
}

h1 {
   color: black;
}

/* Do not print these sections of the page */
#sidebar-left, #sidebar-right, #menu, #search-theme-form {
   display: none;
}

/* Do not print parts styled like this */
/* You may also want to add other comment action links: .comment_delete, .comment_edit, .comment_reply */
.tabs, .comment_add, .form-submit, .feed-icon {
  display: none;
}

#header,#footer,#mission{
  width: 100%;
  margin: 0;
  border: 0;
}

#content {
   width: auto;
   margin: 0;
   padding: 0;
   border: 0;
   float: none !important;
   background: transparent none;
   color: black;
}

div#content {
   padding-top: 1em;
}

a:link, a:visited {
   background: transparent;
   text-decoration: underline;
   color: black;
}

Gotta go! - tell me what you think?

Just forgot: live working sample of hack: http://test.oldrup.dk/node/1

I like the changes.. I guess we could release it as it is...

However, I have experienced inconsistencies in how IE, Firefox and Opera renders the output. While thats not a big issue, it annoys me a lot. The page title seems gray instead of black in IE, and some browsers renders horizontal borders while others don't... That does not male print.css unusable, its a big improvement over no print.css, but it really annoys me - especially the part that after fiddling with the css for several hours, I didn't get the slightest bit closer to a solution. Like it or not, IE is still the most frequently used browser, and I think we should support it as best as we can.

So... Is this getting to a conclusion or?

I guess so. I say, unless vjordan have any idea to fix the inconsistencies we go ahead and release the print.css. Yes - it can still be improved, but its absolutely useful as it is..

I agree. The print.css addition to Foliage is good as it is, and there is no reason to be picky about minor inconsistencies between IE and Firefoxs rendering of the printer friendly pages, as long as print.css is a major improvement when it comes to printing in both browsers.

However, I'm leaving the Foliage development for the time being, and I'm not tempted by the hassle of installing/configuring/trying-to-understanding a CVS client at the moment, so I will not be able to provide a prober release (whats wrong with good ol' ftp ;-))

So – to take advantage of print.css, you'll have to add a few lines to page.tpl.php as described in this issues first post, and create the print.css file – i suggest you copy the code of comment #7. Its less than 5 minutes work and worth it.

To vjordan: Great work – and thank you for contributing to the Foliage theme...
- Bjarne

Thanks to Vjordan for contributing the print.css file!

The stylesheets for the new Drupal 6 version have been revised from ground up and I also included a print.css file into the new version. I hope that it works well.
There are no actual plans to revise the Drupal 5 version and so I think that this issue can be closed.

However I invite you to reopen it if you think that corrections for the Drupal 6 version are necessary.