login/register

Snip!t from collection of Alan Dix

see all channels for Alan Dix

Snip
summary

In certain instances, not everyone views every portion o... online: eventually, someone is going to print parts of i... this is perfectly fine: if you have a print style sheet ...
It’s a simple problem of resolution. Images are always ...
Back in 200

Print-Friendly Images and Logos with CSS
http://www.cssnewbie.com/print-friendly-images/

Categories

/Channels/techie/css

[ go to category ]

/Channels/techie/web development

[ go to category ]

For Snip

loading snip actions ...

For Page

loading url actions ...

In certain instances, not everyone views every portion of your website online: eventually, someone is going to print parts of it. In many cases, this is perfectly fine: if you have a print style sheet that takes care of your worst sins, your website should look okay. But one area where it may still look lackluster is the images.

It’s a simple problem of resolution. Images are always displayed on the web at 72dpi (dots per inch). However, nearly all printers can handle resolutions far higher than this. What that means is the text of your printed web page will be printed at a high resolution – likely at least 300dpi. Your images, however, won’t have enough information to print out at 300dpi or higher. Instead, because the browser and printer know how much space (vertically and horizontally) the image is supposed to take up, they’ll up-sample the image, doubling and tripling the number of pixels in the image via crude pixel duplication algorithms until the image is the correct size. The result is a fuzzy image with jagged edges.

Back in 2005, an article by Ross Howard appeared on A List Apart describing a way around this problem. It solves a real problem with a viable solution, but the author doesn’t give a lot of practical information on how to implant the solution. So here’s my take on that technique.

HTML

<p>In certain instances, not everyone views every portion of your website online: eventually, someone is going to print parts of it. In many cases, this is perfectly fine: if you have a <a href="http://www.cssnewbie.com/7-tips-print-style-sheets/" title="7 Tips for Great Print Style Sheets">print style sheet that takes care of your worst sins,</a> your website should look okay. But one area where it may still look lackluster is the images.</p><p>It&#x2019;s a simple problem of resolution. Images are always displayed on the web at 72dpi (dots per inch). However, nearly all printers can handle resolutions far higher than this. What that means is the text of your printed web page will be printed at a high resolution &#x2013; likely at least 300dpi. Your images, however, won&#x2019;t have enough information to print out at 300dpi or higher. Instead, because the browser and printer know how much <em>space</em> (vertically and horizontally) the image is supposed to take up, they&#x2019;ll up-sample the image, doubling and tripling the number of pixels in the image via crude pixel duplication algorithms until the image is the correct size. The result is a fuzzy image with jagged edges.</p><p>Back in 2005, <a href="http://www.alistapart.com/articles/hiresprinting">an article by Ross Howard appeared on A List Apart</a> describing a way around this problem. It solves a real problem with a viable solution, but the author doesn&#x2019;t give a lot of practical information on how to implant the solution. So here&#x2019;s my take on that technique.</p>