comment on

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.

In reply to Re: Re: formatting web pages for a printer by jk2addict
in thread formatting web pages for a printer by markjugg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks