<?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: Text anti-aliasing: Windows&#8217; ClearType vs. Mac OS X&#8217;s Quartz Text Smoothing</title>
	<atom:link href="http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/</link>
	<description>Notes from an unfinished world…</description>
	<lastBuildDate>Thu, 15 Jul 2010 12:49:25 +0200</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Patrick Wynne</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1122</link>
		<dc:creator>Patrick Wynne</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1122</guid>
		<description>Just a note: The first link in the argument (&quot;ClearType technology is far superior&quot;) actually points to one of Zeldman&#039;s posts about his OS X troubles, not a Scoble blog entry.</description>
		<content:encoded><![CDATA[<p>Just a note: The first link in the argument (&#8220;ClearType technology is far superior&#8221;) actually points to one of Zeldman&#8217;s posts about his OS X troubles, not a Scoble blog entry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Wynne</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1123</link>
		<dc:creator>Patrick Wynne</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1123</guid>
		<description>Heh heh, or y&#039;know, I could actually *read* the Zeldman post to see that he does talk about anti-aliasing. Oops.</description>
		<content:encoded><![CDATA[<p>Heh heh, or y&#8217;know, I could actually *read* the Zeldman post to see that he does talk about anti-aliasing. Oops.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1125</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1125</guid>
		<description>Thanks for the correction. Scoble&#039;s blog design leaves a bit to be desired, shall we say.</description>
		<content:encoded><![CDATA[<p>Thanks for the correction. Scoble&#8217;s blog design leaves a bit to be desired, shall we say.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Scoble</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1131</link>
		<dc:creator>Robert Scoble</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1131</guid>
		<description>Actually, if you talk with the engineers at either Apple or Microsoft, anti-aliasing, or technologies like ClearType (which really isn&#039;t anti-aliasing, but rather a technology that uses the RGB display technology to increase resolution) are both ways to make fonts easier to read, not to make them more faithful to print.</description>
		<content:encoded><![CDATA[<p>Actually, if you talk with the engineers at either Apple or Microsoft, anti-aliasing, or technologies like ClearType (which really isn&#8217;t anti-aliasing, but rather a technology that uses the RGB display technology to increase resolution) are both ways to make fonts easier to read, not to make them more faithful to print.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1132</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1132</guid>
		<description>Robert: Thanks for your comment. As I said, I&#039;m not a specialist, and certainly do not have the inside scoop about MS or Apple technology. However, it strikes me as strange that matching print should not be the goal, since most fonts are designed specifically for print. (I know that MS in particular has developed some fonts especially for on-screen reading, but these are exceptions.) In any case, I think you will agree from the screen shot provided by Going Nowhere that Mac OS X anti-aliasing looks much closer to what the Times font looks like in print than the Windows XP anti-aliasing does. Whether that translates into the text being easier to read on-screen is obviously another matter, and a highly subjective one at that.  </description>
		<content:encoded><![CDATA[<p>Robert: Thanks for your comment. As I said, I&#8217;m not a specialist, and certainly do not have the inside scoop about MS or Apple technology. However, it strikes me as strange that matching print should not be the goal, since most fonts are designed specifically for print. (I know that MS in particular has developed some fonts especially for on-screen reading, but these are exceptions.) In any case, I think you will agree from the screen shot provided by Going Nowhere that Mac OS X anti-aliasing looks much closer to what the Times font looks like in print than the Windows XP anti-aliasing does. Whether that translates into the text being easier to read on-screen is obviously another matter, and a highly subjective one at that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Scoble</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1133</link>
		<dc:creator>Robert Scoble</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1133</guid>
		<description>Well, print is useful to study but now that we&#039;re creating type for on screen, we need to look at that as a separate thing than print. Learn from the old, but design for the new. Designing fonts for readability on screen (most screens are 72 DPI to 96 DPI, while print is usually 600 DPI or higher) is different than for print. Go and listen to the Bill Hill videos over on Channel9 &lt;a href=&quot;http://channel9.msdn.com&quot; title=&quot;http://channel9.msdn.com&quot;&gt;http://channel9.msdn.com&lt;/a&gt; (click on videos and look for Bill Hill, he&#039;s the head of typography here).</description>
		<content:encoded><![CDATA[<p>Well, print is useful to study but now that we&#8217;re creating type for on screen, we need to look at that as a separate thing than print. Learn from the old, but design for the new. Designing fonts for readability on screen (most screens are 72 DPI to 96 DPI, while print is usually 600 DPI or higher) is different than for print. Go and listen to the Bill Hill videos over on Channel9 <a href="http://channel9.msdn.com" title="http://channel9.msdn.com">http://channel9.msdn.com</a> (click on videos and look for Bill Hill, he&#8217;s the head of typography here).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1134</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1134</guid>
		<description>Robert, I agree with that old maxim about &quot;learn from the old, design for the new&quot; but I think that Pierre&#039;s point here is not about designing new fonts. Clearly some beautiful work has been done on computer typefaces.

The point is about whether we can easily read text displayed on computer screens. Right? But we all learn to read on print, and that human dependence on print is not likely to change anytime soon, so then it makes sense to ask to what degree what we see on the screen is like what we see in print.</description>
		<content:encoded><![CDATA[<p>Robert, I agree with that old maxim about &#8220;learn from the old, design for the new&#8221; but I think that Pierre&#8217;s point here is not about designing new fonts. Clearly some beautiful work has been done on computer typefaces.</p>
<p>The point is about whether we can easily read text displayed on computer screens. Right? But we all learn to read on print, and that human dependence on print is not likely to change anytime soon, so then it makes sense to ask to what degree what we see on the screen is like what we see in print.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Kheit</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1135</link>
		<dc:creator>John Kheit</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1135</guid>
		<description>I did an article on this a while back that may be of interest to the debate.  To me it&#039;s it boils down to this.  At small font sizes you need to tune down the amount of &quot;halo&quot; effect use in the antialiasing.  ClearType does that.  At medium to larger sizes, having more &quot;halo&quot; effect smooths things nicely.  I proposed a &quot;MultipleMasters&quot; type of approach to antialiasing as a more optimal solution.  Namely the display layer should crank down the &quot;halo&quot; effect as you get down to smaller font sizes (say 14pt and smaller) and crank it up at higher points.

Anyway, here&#039;s the link:

&lt;a href=&quot;http://www.macobserver.com/columns/devilsadvocate/2003/20030523.shtml&quot; title=&quot;http://www.macobserver.com/columns/devilsadvocate/2003/20030523.shtml&quot;&gt;http://www.macobserver.com/columns/devilsadvocate/2003/20030523.shtml&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I did an article on this a while back that may be of interest to the debate.  To me it&#8217;s it boils down to this.  At small font sizes you need to tune down the amount of &#8220;halo&#8221; effect use in the antialiasing.  ClearType does that.  At medium to larger sizes, having more &#8220;halo&#8221; effect smooths things nicely.  I proposed a &#8220;MultipleMasters&#8221; type of approach to antialiasing as a more optimal solution.  Namely the display layer should crank down the &#8220;halo&#8221; effect as you get down to smaller font sizes (say 14pt and smaller) and crank it up at higher points.</p>
<p>Anyway, here&#8217;s the link:</p>
<p><a href="http://www.macobserver.com/columns/devilsadvocate/2003/20030523.shtml" title="http://www.macobserver.com/columns/devilsadvocate/2003/20030523.shtml">http://www.macobserver.com/columns/devilsadvocate/2003/20030523.shtml</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Sampson</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1163</link>
		<dc:creator>Adam Sampson</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1163</guid>
		<description>Having played around with antialiased rendering for a while, I&#039;ve found that display gamma makes a considerable different to how good it looks. If I recall correctly, Mac and Windows systems have different default gamma settings — so isn&#039;t it quite likely that the Mac rendering model will look good on a Mac, and the Windows model good on a Windows machine?

The other thing I&#039;ve discovered is that almost everybody has different preferences for how their text is rendered, so it&#039;s always going to be difficult to argue that one method is superior to all others.</description>
		<content:encoded><![CDATA[<p>Having played around with antialiased rendering for a while, I&#8217;ve found that display gamma makes a considerable different to how good it looks. If I recall correctly, Mac and Windows systems have different default gamma settings — so isn&#8217;t it quite likely that the Mac rendering model will look good on a Mac, and the Windows model good on a Windows machine?</p>
<p>The other thing I&#8217;ve discovered is that almost everybody has different preferences for how their text is rendered, so it&#8217;s always going to be difficult to argue that one method is superior to all others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2004/04/28/text-anti-aliasing-windows-cleartype-vs-mac-os-xs-quartz-text-smoothing/comment-page-1/#comment-1166</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1026#comment-1166</guid>
		<description>I agree that gamma settings probably have some impact. However, the screen shot provided by Going Nowhere can be viewed on both PCs and Macs, with their respective gamma settings. I&#039;ve tried fooling around with the gamma setting on my monitor while viewing GN&#039;s screen shot, and I don&#039;t really see major variations. </description>
		<content:encoded><![CDATA[<p>I agree that gamma settings probably have some impact. However, the screen shot provided by Going Nowhere can be viewed on both PCs and Macs, with their respective gamma settings. I&#8217;ve tried fooling around with the gamma setting on my monitor while viewing GN&#8217;s screen shot, and I don&#8217;t really see major variations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
