Ling, Luke C wrote: > . . . Would working in a web standards compliant way, lead me > to the path of enlightenment when it comes to my end users being able > to print my pages, stripped of graphics? Or do I really only require > a simple print version for the CSS that will override all my web > rendering formatting?
A well-organized source-code is the best base, as reorganizing or repositioning for print isn't working all that well in the majority of today's browsers. What you (probably) want is a linear, more or less "text-only", version of a page, without all the screen-design stuff. Once the source-code is brought somewhat under control, the rest is dealt with through CSS only, following one of two possible paths. 1: create a stylesheet for _all_ media, and use it to design primarily for screens. 1b: create a separate stylesheet for print, and override screen styles until you have a print-output you're satisfied with. Article: <http://www.alistapart.com/stories/goingtoprint/> 2: create separate stylesheets or style-sets for each media, using either the media-attribute for stylesheet links, or @media wrappers, to keep them separate. This will basically give you a pretty print-friendly version even if you don't create a stylesheet or style-set for print, since nothing from your screen styles will affect print or other media. Example: <http://www.gunlaug.no/contents/wd_1_04.html> All other (cross-browser working) solutions are just variants of the shown methods. A bit more info: <http://www.w3.org/TR/css-print/> <http://www.w3.org/TR/CSS21/media.html> <http://www.ilovejackdaniels.com/css/printer-friendly-pages/> regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
