<?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: Font rendering comparison</title>
	<atom:link href="http://frozr.com/design/font-rendering-comparison/feed/" rel="self" type="application/rss+xml" />
	<link>http://frozr.com/design/font-rendering-comparison/</link>
	<description>Wordpress themes &#38; Tutorials</description>
	<lastBuildDate>Sat, 22 May 2010 23:25:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kev</title>
		<link>http://frozr.com/design/font-rendering-comparison/comment-page-1/#comment-23752</link>
		<dc:creator>Kev</dc:creator>
		<pubDate>Fri, 24 Apr 2009 09:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://frozr.com/?p=189#comment-23752</guid>
		<description>I&#039;m a firefox fan and I love it&#039;s features, safari and the iphone lack browser settings, but I have to say that I think things do look better in safari. I don&#039;t use safari except for testing and so may not know when it looks worse.

As for cleartype, from the documentation, it should? only be neccessary as a fix for flat screens, it shouldn&#039;t be needed for crts and therefore SHOULD? only effect the display and not the capture. 

If you think it looks better on a crt with cleartype then smoothing has improved the font which lacks resolution but then the font may have lost definition, however smoothing can help keep the filesize of fonts down. I had to treble the size of one of my intricate images to cater for internet explorer and it still looked worse than safari did originally. 

I guess theres a balance that all browsers should adhere to, but then maybe we need to wait for screen technology to level out first (in the end crts matched their colors to each other and to printers). I feel more smoothing could be a good thing as so many web images have to be small and smoothing beforehand requires more bandwidth(scarce) rather than cpu(abundant).

In fact you have to be careful testing fonts on flat screens as anyone who has watched the credits of a DVD on a HD tv would see, whereas a far higher resolution crt can display consistently at any resolution it supports (except lower resolution than the source imagery). 

This is because a flat screen is digital and therefore lacks the levels of brightness (on or off only) per pixel of an analog crt, meaning only native resolutions (resolution the flat screen was designed for) look half decent, especially for text.

Comparisons should therefore be made on crts and also tested on flat screens, otherwise you would have to know the hardware.

If wish the flat crt had made it out of development, but then would it have limitations anyway?</description>
		<content:encoded><![CDATA[<p>I&#8217;m a firefox fan and I love it&#8217;s features, safari and the iphone lack browser settings, but I have to say that I think things do look better in safari. I don&#8217;t use safari except for testing and so may not know when it looks worse.</p>
<p>As for cleartype, from the documentation, it should? only be neccessary as a fix for flat screens, it shouldn&#8217;t be needed for crts and therefore SHOULD? only effect the display and not the capture. </p>
<p>If you think it looks better on a crt with cleartype then smoothing has improved the font which lacks resolution but then the font may have lost definition, however smoothing can help keep the filesize of fonts down. I had to treble the size of one of my intricate images to cater for internet explorer and it still looked worse than safari did originally. </p>
<p>I guess theres a balance that all browsers should adhere to, but then maybe we need to wait for screen technology to level out first (in the end crts matched their colors to each other and to printers). I feel more smoothing could be a good thing as so many web images have to be small and smoothing beforehand requires more bandwidth(scarce) rather than cpu(abundant).</p>
<p>In fact you have to be careful testing fonts on flat screens as anyone who has watched the credits of a DVD on a HD tv would see, whereas a far higher resolution crt can display consistently at any resolution it supports (except lower resolution than the source imagery). </p>
<p>This is because a flat screen is digital and therefore lacks the levels of brightness (on or off only) per pixel of an analog crt, meaning only native resolutions (resolution the flat screen was designed for) look half decent, especially for text.</p>
<p>Comparisons should therefore be made on crts and also tested on flat screens, otherwise you would have to know the hardware.</p>
<p>If wish the flat crt had made it out of development, but then would it have limitations anyway?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bat</title>
		<link>http://frozr.com/design/font-rendering-comparison/comment-page-1/#comment-253</link>
		<dc:creator>Bat</dc:creator>
		<pubDate>Wed, 02 Jul 2008 16:02:12 +0000</pubDate>
		<guid isPermaLink="false">http://frozr.com/?p=189#comment-253</guid>
		<description>I love the font rendering in Safari. Sometimes I prefer to use Safari(windows version) than FireFox because of the advance CSS rendering in Safari(Safari use WebKit Engine).

Pay a visit to http://jeffcroft.com in both browsers, you will get it. =)</description>
		<content:encoded><![CDATA[<p>I love the font rendering in Safari. Sometimes I prefer to use Safari(windows version) than FireFox because of the advance CSS rendering in Safari(Safari use WebKit Engine).</p>
<p>Pay a visit to <a href="http://jeffcroft.com" rel="nofollow">http://jeffcroft.com</a> in both browsers, you will get it. =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xero</title>
		<link>http://frozr.com/design/font-rendering-comparison/comment-page-1/#comment-252</link>
		<dc:creator>xero</dc:creator>
		<pubDate>Wed, 02 Jul 2008 07:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://frozr.com/?p=189#comment-252</guid>
		<description>damn... i guess u not use the clear type smooth edge effect on ur windows.. bcoz... my ff3 doesnt look bad like that.. thats screenie looks like on ie 4/5 years ago.. huhuhu..

but still.. safari have a good text rendering.. but somtime i dont like it.. huhu.. blurry..</description>
		<content:encoded><![CDATA[<p>damn&#8230; i guess u not use the clear type smooth edge effect on ur windows.. bcoz&#8230; my ff3 doesnt look bad like that.. thats screenie looks like on ie 4/5 years ago.. huhuhu..</p>
<p>but still.. safari have a good text rendering.. but somtime i dont like it.. huhu.. blurry..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: flisterz</title>
		<link>http://frozr.com/design/font-rendering-comparison/comment-page-1/#comment-249</link>
		<dc:creator>flisterz</dc:creator>
		<pubDate>Sat, 28 Jun 2008 01:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://frozr.com/?p=189#comment-249</guid>
		<description>actually a lot of people hate the text rendering in Safari.
but IMO, it does look good sometimes, not all the time.
there&#039;s a tip to fix the safari rendering &quot;problem&quot; though.</description>
		<content:encoded><![CDATA[<p>actually a lot of people hate the text rendering in Safari.<br />
but IMO, it does look good sometimes, not all the time.<br />
there&#8217;s a tip to fix the safari rendering &#8220;problem&#8221; though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
