<?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"
	>
<channel>
	<title>Comments on: In&#8217;s and Out&#8217;s of Comping Text for Web Browsers</title>
	<atom:link href="http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/</link>
	<description>The company blog for Pint Inc.</description>
	<pubDate>Tue, 06 Jan 2009 23:20:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: dbutler</title>
		<link>http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-101</link>
		<dc:creator>dbutler</dc:creator>
		<pubDate>Thu, 23 Aug 2007 06:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-101</guid>
		<description>You guys are both right - when designing for small print or web graphics, SHARP will produce a "fudged" shape but it is still closer to a browser's rendition of that font (if over 18 pixels or that magic number).</description>
		<content:encoded><![CDATA[<p>You guys are both right - when designing for small print or web graphics, SHARP will produce a &#8220;fudged&#8221; shape but it is still closer to a browser&#8217;s rendition of that font (if over 18 pixels or that magic number).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy</title>
		<link>http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-28</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Mon, 16 Jul 2007 17:10:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-28</guid>
		<description>rus, we've found that Sharp seems to mimic best how browsers render text. I certainly wouldn't say that the way a browser renders text is the best way, but sharp does give an honest representation.</description>
		<content:encoded><![CDATA[<p>rus, we&#8217;ve found that Sharp seems to mimic best how browsers render text. I certainly wouldn&#8217;t say that the way a browser renders text is the best way, but sharp does give an honest representation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-21</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 14 Jul 2007 01:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-21</guid>
		<description>Sharp vs. Crisp.

Troy - care to respond with your thoughts?</description>
		<content:encoded><![CDATA[<p>Sharp vs. Crisp.</p>
<p>Troy - care to respond with your thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rus</title>
		<link>http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-18</link>
		<dc:creator>rus</dc:creator>
		<pubDate>Fri, 13 Jul 2007 21:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-18</guid>
		<description>setting your text to SHARP will produce bad results as that setting fudges the integrity of the character shape. use CRISP instead for best results.</description>
		<content:encoded><![CDATA[<p>setting your text to SHARP will produce bad results as that setting fudges the integrity of the character shape. use CRISP instead for best results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deFUNKT - design blog</title>
		<link>http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-17</link>
		<dc:creator>deFUNKT - design blog</dc:creator>
		<pubDate>Fri, 13 Jul 2007 09:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/11/ins-and-outs-of-comping-text-for-web-browsers/#comment-17</guid>
		<description>[...] Text in webdesign link  [...]</description>
		<content:encoded><![CDATA[<p>[...] Text in webdesign link  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
