<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Browser anti-aliasing: do you design your comps using bitmapped text?</title>
	<atom:link href="http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/</link>
	<description>26 year old from Massachusetts</description>
	<lastBuildDate>Wed, 08 Sep 2010 07:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Forrest Frazier</title>
		<link>http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/comment-page-1/#comment-1677</link>
		<dc:creator>Forrest Frazier</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.combustingboy.com/?p=96#comment-1677</guid>
		<description>The crux of your argument lies at &quot;those two type-faces do not look good at small sizes&quot; and I couldn&#039;t agree more.  That is why I am trying to get away from using small type on sites.  I know I&#039;m bucking the trend but it&#039;s time for everyone to be able to easily read content regardless of the font chosen (assuming its a readable font in the first place).</description>
		<content:encoded><![CDATA[<p>The crux of your argument lies at &#8220;those two type-faces do not look good at small sizes&#8221; and I couldn&#8217;t agree more.  That is why I am trying to get away from using small type on sites.  I know I&#8217;m bucking the trend but it&#8217;s time for everyone to be able to easily read content regardless of the font chosen (assuming its a readable font in the first place).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/comment-page-1/#comment-1676</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.combustingboy.com/?p=96#comment-1676</guid>
		<description>I design comps with anti-aliased fonts as well. I&#039;m a bit of a &#039;screw old habits/methods/technology&#039; guy, which bites me in the butt sometimes, but this is one I stick with.</description>
		<content:encoded><![CDATA[<p>I design comps with anti-aliased fonts as well. I&#8217;m a bit of a &#8216;screw old habits/methods/technology&#8217; guy, which bites me in the butt sometimes, but this is one I stick with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/comment-page-1/#comment-1675</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:16:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.combustingboy.com/?p=96#comment-1675</guid>
		<description>I *always* smooth my fonts. The same way others believe that you no longer have to support IE6, it&#039;s time to move forward.

My goal is to show your design in the best way possible. If you&#039;re going to hold back your machine with pixelated fonts, things will still render and be readable (especially due to my love of large fonts), but everything will probably look — well — chunky.</description>
		<content:encoded><![CDATA[<p>I *always* smooth my fonts. The same way others believe that you no longer have to support IE6, it&#8217;s time to move forward.</p>
<p>My goal is to show your design in the best way possible. If you&#8217;re going to hold back your machine with pixelated fonts, things will still render and be readable (especially due to my love of large fonts), but everything will probably look — well — chunky.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcel</title>
		<link>http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/comment-page-1/#comment-1674</link>
		<dc:creator>Marcel</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:15:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.combustingboy.com/?p=96#comment-1674</guid>
		<description>We haven&#039;t discussed it yet, but I think we&#039;ll go anti-aliased. It looks better and more people will ultimately be going that route.</description>
		<content:encoded><![CDATA[<p>We haven&#8217;t discussed it yet, but I think we&#8217;ll go anti-aliased. It looks better and more people will ultimately be going that route.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Peters</title>
		<link>http://www.combustingboy.com/2009/04/26/browser-anti-aliasing-do-you-design-your-comps-using-bitmapped-text/comment-page-1/#comment-1673</link>
		<dc:creator>Dan Peters</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.combustingboy.com/?p=96#comment-1673</guid>
		<description>Great article Marcel, we&#039;ve also had similar discussions around which to include in design  comps. Where did you guys end up?</description>
		<content:encoded><![CDATA[<p>Great article Marcel, we&#8217;ve also had similar discussions around which to include in design  comps. Where did you guys end up?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
