http://qs321.pair.com?node_id=193200


in reply to formatting web pages for a printer

Style sheets and media types are your friend. Make use of the PRINT media type such that the format and styles used for the web pages are printer friendly when the person goes to print the page.

Big advantage - you only have to set this up once for all pages on the site.

What's that? Your browser does not support these standards? Then upgrade the browser to one that does support CSS-2.

Replies are listed 'Best First'.
Re: Re: formatting web pages for a printer
by jk2addict (Chaplain) on Aug 27, 2002 at 19:03 UTC

    Here Here!

    Along that line, you could also use something like AxKit on the backend. It's based on the same premise, xml/xsl/xslt transformations; even mix that backend with client side css on the front end. This is a win win if you want to repurpose output for more than just html for browsers from your site. It even has an AxPoint plugin, so you could translate the same xml doc into a .pdf output by doing something like ?media=pdf with little extra work.

    Regardless how what you choose, anything is better and two seperate pages just for two seperate looks on the same content.

    Yes, I'm a HUGE fan of AxKit.

      Hmm. I wasn't implying that markjugg create two different pages, but two different HTML::Templates, one for browser output and one tweaked especially for HTMLdoc.

      That said, Axkit is on my short list of systems to spend more time figuring out, along with Bricolage.

      -Any sufficiently advanced technology is
      indistinguishable from doubletalk.

        My apologies. I didn't mean to imply that was what you were suggesting, only that the 2-seperate-page (not templates) solution in general wasn't the way to go.

        -=Chris