<?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: On anti-aliasing</title>
	<atom:link href="http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/feed/" rel="self" type="application/rss+xml" />
	<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/</link>
	<description>All hail the mushroom cloud</description>
	<lastBuildDate>Sat, 24 Apr 2010 08:56:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Tomas</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-113</link>
		<dc:creator>Tomas</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-113</guid>
		<description>Like you said, results vary on CRT monitors. Sometimes you get better readability and sometimes you get worse.

In your pictured example (not the zoomed-in one), I think the italicized text is easier to read in the Clear Type enabled version, while the rest of the text is hard to read in both, wether Clear Type is enabled or not; too pixely in the first case, too fuzzy in the other.

I have a professional line Trinitron monitor at home, and while that is a CRT screen just like the &quot;regular&quot; CRT at my office, I get better Clear Type results on the one at home.</description>
		<content:encoded><![CDATA[<p>Like you said, results vary on <span class="caps">CRT </span>monitors. Sometimes you get better readability and sometimes you get worse.</p>
<p>In your pictured example (not the zoomed-in one), I think the italicized text is easier to read in the Clear Type enabled version, while the rest of the text is hard to read in both, wether Clear Type is enabled or not; too pixely in the first case, too fuzzy in the other.</p>
<p>I have a professional line Trinitron monitor at home, and while that is a <span class="caps">CRT </span>screen just like the &#8220;regular&#8221; CRT at my office, I get better Clear Type results on the one at home.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pythagore Anonymous</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-114</link>
		<dc:creator>Pythagore Anonymous</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-114</guid>
		<description>The worst about the nice, anti-aliased fonts in Jaguar is when you do webdesign in it, and later get to see what your page looks like in Windows.</description>
		<content:encoded><![CDATA[<p>The worst about the nice, anti-aliased fonts in Jaguar is when you do webdesign in it, and later get to see what your page looks like in Windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-115</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-115</guid>
		<description>ClearType is smooth and nice. OS X&#039;s antialiasing is all blurred up. I can hardly read the smaller font sizes with OS X&#039;s antialiasing.</description>
		<content:encoded><![CDATA[<p>ClearType is smooth and nice. OS X&#8217;s antialiasing is all blurred up. I can hardly read the smaller font sizes with OS X&#8217;s antialiasing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emre</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-116</link>
		<dc:creator>Emre</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-116</guid>
		<description>The Trinitron CRT is arranged in RGB columns, whereas the normal CRT is RGB colors are not in a column, they are shifted each row. This may be why trinitron has much better results with cleartype than regular CRT.

Cleartype looks best on a digital LCD running at native resolution, where each pixel corresponds to a single RGB component, but on CRT (even trinitron and analog LCD), one pixel can occupy more than one RGB component.</description>
		<content:encoded><![CDATA[<p>The Trinitron <span class="caps">CRT </span>is arranged in <span class="caps">RGB </span>columns, whereas the normal <span class="caps">CRT </span>is <span class="caps">RGB </span>colors are not in a column, they are shifted each row. This may be why trinitron has much better results with cleartype than regular <span class="caps">CRT.</span></p>
<p>Cleartype looks best on a digital <span class="caps">LCD </span>running at native resolution, where each pixel corresponds to a single <span class="caps">RGB </span>component, but on <span class="caps">CRT </span>(even trinitron and analog <span class="caps">LCD</span>), one pixel can occupy more than one <span class="caps">RGB </span>component.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-117</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-117</guid>
		<description>Just to clarify that ClearType is only available in Windows XP, not in 2K.</description>
		<content:encoded><![CDATA[<p>Just to clarify that ClearType is only available in Windows <span class="caps">XP, </span>not in 2K.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ged</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-118</link>
		<dc:creator>Ged</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-118</guid>
		<description>What if not ClearType is the &quot;Smooth edge of fonts&quot; facility available then in Windows 2000 ? 
Is this anti-aliasing but at pixel, not sub-pixel level ?</description>
		<content:encoded><![CDATA[<p>What if not ClearType is the &#8220;Smooth edge of fonts&#8221; facility available then in Windows 2000 ? <br />
Is this anti-aliasing but at pixel, not sub-pixel level ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ged</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-119</link>
		<dc:creator>Ged</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-119</guid>
		<description>Does anybody know about imaging anti-aliasing scanned facsimile documents, and the optimisation thereof for LCD screens ?</description>
		<content:encoded><![CDATA[<p>Does anybody know about imaging anti-aliasing scanned facsimile documents, and the optimisation thereof for <span class="caps">LCD </span>screens ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-120</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-120</guid>
		<description>Windows XP has non-Cleartype anti-aliasing available for people who use CRT monitors. It is an improved version of &quot;Smooth edges of screen fonts&quot; in previous versions of Windows, like one commenter pointed out is in 2000. If you want this to be an accurate article, it wouldn&#039;t hurt to look into that.</description>
		<content:encoded><![CDATA[<p>Windows XP has non-Cleartype anti-aliasing available for people who use <span class="caps">CRT </span>monitors. It is an improved version of &#8220;Smooth edges of screen fonts&#8221; in previous versions of Windows, like one commenter pointed out is in 2000. If you want this to be an accurate article, it wouldn&#8217;t hurt to look into that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-121</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-121</guid>
		<description>The only problem I see with anti-aliasing is that for small fonts it only serves to make them harder to read. On my monitor, the first, non anti-aliased example is much easier to read IMHO.

So, to keep the fonts from giving readers headaches, you just make them larger, so that a 12pt anti-aliased font appears larger on screen than a 12pt aliased font, which is what KDE and other Linux GUIs do. Except that, of course, this is a waste of screen space.</description>
		<content:encoded><![CDATA[<p>The only problem I see with anti-aliasing is that for small fonts it only serves to make them harder to read. On my monitor, the first, non anti-aliased example is much easier to read <span class="caps">IMHO.</span></p>
<p>So, to keep the fonts from giving readers headaches, you just make them larger, so that a 12pt anti-aliased font appears larger on screen than a 12pt aliased font, which is what <span class="caps">KDE </span>and other Linux <span class="caps">GUI</span>s do. Except that, of course, this is a waste of screen space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Center ov Pestilence</title>
		<link>http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/comment-page-1/#comment-122</link>
		<dc:creator>A Center ov Pestilence</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://atomicplayboy.net/blog/2003/06/26/on-anti-aliasing/#comment-122</guid>
		<description>&lt;strong&gt;Usability...&lt;/strong&gt;
...is not a word I would use to describe A Center ov Pestilence. Not only is the page cluttered with stuff (in the bad way, compared to some people I know off), but I&#039;ve started to loath the popup-windows for
</description>
		<content:encoded><![CDATA[<p><strong>Usability&#8230;</strong><br />
&#8230;is not a word I would use to describe A Center ov Pestilence. Not only is the page cluttered with stuff (in the bad way, compared to some people I know off), but I&#8217;ve started to loath the popup-windows for</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: atomicplayboy.net @ 2012-05-22 12:30:21 -->
