<?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: ClearType rendering forthcoming for Safari on Windows?</title>
	<atom:link href="http://www.css3.info/cleartype-added-to-webkit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.css3.info/cleartype-added-to-webkit/</link>
	<description>All you ever needed to know about CSS3</description>
	<lastBuildDate>Fri, 30 Jul 2010 16:05:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: xavix</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-257255</link>
		<dc:creator>xavix</dc:creator>
		<pubDate>Fri, 20 Nov 2009 05:58:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-257255</guid>
		<description>There´s a way to use quartz rendering in Safari 4 for windows? </description>
		<content:encoded><![CDATA[<p>There´s a way to use quartz rendering in Safari 4 for windows? </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-251745</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sun, 09 Aug 2009 03:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-251745</guid>
		<description>Cleartype gives me a headache.</description>
		<content:encoded><![CDATA[<p>Cleartype gives me a headache.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KKT</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-230313</link>
		<dc:creator>KKT</dc:creator>
		<pubDate>Tue, 24 Feb 2009 19:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-230313</guid>
		<description>We did quite a bit of testing around this, and found one of the biggest issues with the WebKit rendering on the PC was the gamma settings.  The Mac assumes certain gamma settings that just aren&#039;t the same on the windows side. This heavily influences the mid-toned pixels, making them appear heavier under windows than on the Mac.</description>
		<content:encoded><![CDATA[<p>We did quite a bit of testing around this, and found one of the biggest issues with the WebKit rendering on the PC was the gamma settings.  The Mac assumes certain gamma settings that just aren&#8217;t the same on the windows side. This heavily influences the mid-toned pixels, making them appear heavier under windows than on the Mac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-200630</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 16 Sep 2008 14:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-200630</guid>
		<description>&quot;Cleartype which is intelligent enough to switch off anti aliasing below a certain size.&quot;

Cleartype still attempts to AA very small (like, 3 pixel high) fonts, add it&#039;s hinting in and you end up with a pixelated, black mess.</description>
		<content:encoded><![CDATA[<p>&#8220;Cleartype which is intelligent enough to switch off anti aliasing below a certain size.&#8221;</p>
<p>Cleartype still attempts to AA very small (like, 3 pixel high) fonts, add it&#8217;s hinting in and you end up with a pixelated, black mess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-200537</link>
		<dc:creator>Dean</dc:creator>
		<pubDate>Mon, 15 Sep 2008 18:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-200537</guid>
		<description>This either does not work or was already included in the latest 2 builds of Safari.

Either way Safari&#039;s text rendering is terrible!  I couldn&#039;t even read this page in Safari because it is so blurry.</description>
		<content:encoded><![CDATA[<p>This either does not work or was already included in the latest 2 builds of Safari.</p>
<p>Either way Safari&#8217;s text rendering is terrible!  I couldn&#8217;t even read this page in Safari because it is so blurry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Axel</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-123346</link>
		<dc:creator>Axel</dc:creator>
		<pubDate>Sun, 23 Mar 2008 02:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-123346</guid>
		<description>&gt;its text rendering is head-and-shoulders above anything else on Windows - it just looks so damn good

On Windows *2000*, maybe. But W2K is an 8-years old OS and does not have ClearType to begin with. On XP the story would be different, and yet again with Vista and WPF.</description>
		<content:encoded><![CDATA[<p>&gt;its text rendering is head-and-shoulders above anything else on Windows &#8211; it just looks so damn good</p>
<p>On Windows *2000*, maybe. But W2K is an 8-years old OS and does not have ClearType to begin with. On XP the story would be different, and yet again with Vista and WPF.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaurbrekt</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-102655</link>
		<dc:creator>Gaurbrekt</dc:creator>
		<pubDate>Tue, 05 Feb 2008 17:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-102655</guid>
		<description>While I agree that larger text sizes look much nicer with the CoreGraphics renderer I have had a lot of trouble with it when it comes  really small text sizes (xx-small), especially on coloured backgrounds. Yes, you DO need them sometimes! 

Here Safari is incapable of matching the readability of Cleartype which is intelligent enough to switch off anti aliasing below a certain size. Sure, it means text bodies look slightly different than the font designer intended and that it doesn&#039;t match what it would look like on paper but surely readibility is more important than either of these concerns. Besides: 

A webpage is not a printed document 
A webpage is not a printed document 
A webpage is not a printed document 
A webpage is not a printed document 
A webpage is not a printed document 
A webpage is not a printed document 

(repeat until it sticks)</description>
		<content:encoded><![CDATA[<p>While I agree that larger text sizes look much nicer with the CoreGraphics renderer I have had a lot of trouble with it when it comes  really small text sizes (xx-small), especially on coloured backgrounds. Yes, you DO need them sometimes! </p>
<p>Here Safari is incapable of matching the readability of Cleartype which is intelligent enough to switch off anti aliasing below a certain size. Sure, it means text bodies look slightly different than the font designer intended and that it doesn&#8217;t match what it would look like on paper but surely readibility is more important than either of these concerns. Besides: </p>
<p>A webpage is not a printed document<br />
A webpage is not a printed document<br />
A webpage is not a printed document<br />
A webpage is not a printed document<br />
A webpage is not a printed document<br />
A webpage is not a printed document </p>
<p>(repeat until it sticks)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Cobbledick</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-91530</link>
		<dc:creator>Dan Cobbledick</dc:creator>
		<pubDate>Thu, 10 Jan 2008 19:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-91530</guid>
		<description>I&#039;m using Windows Safari 3.0.3 (3.0.4 doesn&#039;t work on Win2k for me) despite the fact it&#039;s not a particularly great browser compared to Opera (for one) for the simple reason that its text rendering is head-and-shoulders above anything else on Windows - it just looks so damn good!</description>
		<content:encoded><![CDATA[<p>I&#8217;m using Windows Safari 3.0.3 (3.0.4 doesn&#8217;t work on Win2k for me) despite the fact it&#8217;s not a particularly great browser compared to Opera (for one) for the simple reason that its text rendering is head-and-shoulders above anything else on Windows &#8211; it just looks so damn good!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Darlow</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-91319</link>
		<dc:creator>Ben Darlow</dc:creator>
		<pubDate>Thu, 10 Jan 2008 11:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-91319</guid>
		<description>@Paul Walker: I understand that the horizontal resolution is tripled in the same width, but the way MS&#039; algorithm approaches this has undesirable effects. Compare the outline of the O letterform, and see how many horizontal steps there are compared to vertical. Now zoom into a similar sized piece of text with WebKit doing the rendering (or Gecko under OS X). Notice the difference? Under OS X the anti-aliasing still occupies more than one screen element. In Cleartype, the algorithm tries to squeeze all that information into a single screen element and consequently the horizontal resolution looks a lot lower than the vertical. Again, compare non-cleartype Windows anti-aliasing to cleartype and you&#039;ll see that cleartype looks less anti-aliased than its older sibling (yes, even on TFT displays).

Ultimately though, I don&#039;t see this decision to add cleartype rendering to Safari/Win as a technical decision, but a psychological one. Anti-aliasing on Windows and OS X have been very different for a long time, and so naturally those who&#039;ve been using Windows all this time will be more familiar with the Windows method.</description>
		<content:encoded><![CDATA[<p>@Paul Walker: I understand that the horizontal resolution is tripled in the same width, but the way MS&#8217; algorithm approaches this has undesirable effects. Compare the outline of the O letterform, and see how many horizontal steps there are compared to vertical. Now zoom into a similar sized piece of text with WebKit doing the rendering (or Gecko under OS X). Notice the difference? Under OS X the anti-aliasing still occupies more than one screen element. In Cleartype, the algorithm tries to squeeze all that information into a single screen element and consequently the horizontal resolution looks a lot lower than the vertical. Again, compare non-cleartype Windows anti-aliasing to cleartype and you&#8217;ll see that cleartype looks less anti-aliased than its older sibling (yes, even on TFT displays).</p>
<p>Ultimately though, I don&#8217;t see this decision to add cleartype rendering to Safari/Win as a technical decision, but a psychological one. Anti-aliasing on Windows and OS X have been very different for a long time, and so naturally those who&#8217;ve been using Windows all this time will be more familiar with the Windows method.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walker</title>
		<link>http://www.css3.info/cleartype-added-to-webkit/comment-page-1/#comment-91152</link>
		<dc:creator>Paul Walker</dc:creator>
		<pubDate>Thu, 10 Jan 2008 01:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/cleartype-added-to-webkit/#comment-91152</guid>
		<description>@Ben Darlow - That webpage extremely underestimates the effect of sub-pixel smoothing, and also, you seem to have gotten it&#039;s effect backwards. Subpixel smoothing, used in Cleartype and in OS X - TRIPES the horizontal resolution of type. Unfortunaely, it also makes it look terrible when scaled.
His complaints stem from a misunderstanding of how sub-pixel smoothing works. That 1 yellow pixel actually is three subpixel elements - red, green, and blue. On his screen the pixels are in the order RGB - so the blue is darkest (as it&#039;s nearer to the edge of the letter) the green is in between, and the red is lightest. This happens to make yellow when you blow it up. The number of steps between black and white are the same. They&#039;re just in a smaller area</description>
		<content:encoded><![CDATA[<p>@Ben Darlow &#8211; That webpage extremely underestimates the effect of sub-pixel smoothing, and also, you seem to have gotten it&#8217;s effect backwards. Subpixel smoothing, used in Cleartype and in OS X &#8211; TRIPES the horizontal resolution of type. Unfortunaely, it also makes it look terrible when scaled.<br />
His complaints stem from a misunderstanding of how sub-pixel smoothing works. That 1 yellow pixel actually is three subpixel elements &#8211; red, green, and blue. On his screen the pixels are in the order RGB &#8211; so the blue is darkest (as it&#8217;s nearer to the edge of the letter) the green is in between, and the red is lightest. This happens to make yellow when you blow it up. The number of steps between black and white are the same. They&#8217;re just in a smaller area</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!--
This site's performance optimized by W3 Total Cache:

W3 Total Cache improves the user experience of your blog by caching
frequent operations, reducing the weight of various files and providing
transparent content delivery network integration.

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/


Served from: css3.info @ 2010-07-30 19:24:17 -->