<?xml version="1.0"  encoding="UTF-8"?>
	<rss version="2.0">
		<channel>
			<title>Comments to Web Graphics: Why Are We So Limited?</title>
			<link>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/</link>
			<description>User submitted comments to Practical Ecommerce's article entitled Web Graphics: Why Are We So Limited?</description>
			<language>en-us</language>
			<copyright>Copyright 2007 Confluence Publishing</copyright>
			<lastBuildDate>Thu, 20 Sep 2007 14:40:13 -0600</lastBuildDate>
			<docs>http://www.practicalecommerce.com/rss/</docs>
			<generator>Practical Ecommerce v2.0.1</generator>
			<category>Ecommerce</category>
			<managingEditor>kmurdock@practicalecommerce.com</managingEditor>
			<webMaster>bgetting@practicalecommerce.com</webMaster>
			<ttl>60</ttl>
			<item>
			<title>Misha</title>
			<link>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/#comment3704</link>
			<description>This is not correct (Brian and Ryan). It&#039;s a little confusing (and this is a common misconception). A particular monitor&#039;s DPI is based on the monitor size and the resolution of the monitor: A 19&quot; monitor with 1024x768 pixel resolution would have a DPI greater than a 19&quot; monitor with a 800x600 pixel resolution.

However, in effect, there is no difference between a 72dpi image that is 500px wide and a 300dpi image that is 500px wide ON A WEB PAGE. In fact, each image will be the same filesize. However, if you were to print out a 500px wide image at 72dpi, it would be much larger than the printed version of the image at 300dpi. On paper, a 500px wide image, at 72dpi is 7 inches wide. On paper, a 500px wide image at 300dpi is nearly 3 inches wide.

Part of the filesize misinformation is that, if you were to want an image to print out at 7 inches wide (at 300dpi) you would have to have a 2100px wide image, and thus a larger filesize.

I had held the &quot;72 dpi misinformation&quot; until I...</description>
			<pubDate>Thu, 20 Sep 2007 14:40:13 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/#comment3704</guid>
			</item>
			
				<item>
			<title>Brian Getting</title>
			<link>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/#comment3319</link>
			<description>72 DPI is the resolution for all screens right now, and the default resolution for web graphics.  Period.  You can save your graphics at 300 DPI if you would like, but they will still display at 72 DPI on a computer screen, because there are only 72 pixels crammed into each linear inch of a computer screen.  Like it or not, pixels from the web world and &quot;dots&quot; (the mesh screen size) in the print world are analogous.</description>
			<pubDate>Sun, 15 Jul 2007 12:53:55 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/#comment3319</guid>
			</item>
			
				<item>
			<title>B. T. Clown</title>
			<link>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/#comment3317</link>
			<description>I take issue with your statement that browers will always display graphics at 72 DPI.  First of all, DPI is only relevant in print work and is absolutely irrelevant to the Web.  PPI is only marginally relevant, mostly as a *very* rough sizing guideline.  Browsers don&#039;t care about the pixel density of an image.  The only thing that matters on the Web is an image&#039;s dimensions measured in pixels.  If you design your web site to be 800px wide and want a photo to take up one quarter of the width, the photo should be 200px wide, simple as that.  If you think you can make a photo always appear 4&quot;x5&quot; on the viewer&#039;s screen then you&#039;re stuck in the print paradigm and don&#039;t understand how display graphics work.</description>
			<pubDate>Sun, 15 Jul 2007 11:31:13 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/70/Web-Graphics-Why-Are-We-So-Limited/#comment3317</guid>
			</item>
			
				
		</channel>
	</rss>