in reply to Re: formatting web pages for a printer
in thread formatting web pages for a printer

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.

  • Comment on Re: Re: formatting web pages for a printer

Replies are listed 'Best First'.
Re: Re: Re: formatting web pages for a printer
by Hero Zzyzzx (Curate) on Aug 27, 2002 at 20:33 UTC

    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