 <?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 Aliasing: Managing Expectations</title>
	<atom:link href="http://www.broken-links.com/2007/07/20/font-aliasing-managing-expectations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.broken-links.com/2007/07/20/font-aliasing-managing-expectations/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=font-aliasing-managing-expectations</link>
	<description>Thoughts on web development and technologies by Peter Gasston</description>
	<lastBuildDate>Tue, 07 Sep 2010 21:24:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Peter</title>
		<link>http://www.broken-links.com/2007/07/20/font-aliasing-managing-expectations/#comment-5413</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sun, 09 Dec 2007 12:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/07/20/font-aliasing-managing-expectations/#comment-5413</guid>
		<description>We showed them screenshot after screenshot of how the fonts would appear in other browsers, and explained that they were viewing in the worst possible way - IE6, no cleartype, on laptop screens - but in the end we had to change the serif fonts to sans-serif &amp; reduce the sizes; although, only for IE6. We used conditional comments, so other browsers saw the original designs.</description>
		<content:encoded><![CDATA[<p>We showed them screenshot after screenshot of how the fonts would appear in other browsers, and explained that they were viewing in the worst possible way — IE6, no cleartype, on laptop screens — but in the end we had to change the serif fonts to sans-serif &amp; reduce the sizes; although, only for IE6. We used conditional comments, so other browsers saw the original designs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gil Bates</title>
		<link>http://www.broken-links.com/2007/07/20/font-aliasing-managing-expectations/#comment-5411</link>
		<dc:creator>Gil Bates</dc:creator>
		<pubDate>Sun, 09 Dec 2007 11:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/07/20/font-aliasing-managing-expectations/#comment-5411</guid>
		<description>&quot;we had to take our nice, approved design and go back to make changes&quot;

I&#039;m curious...Exactly what changes did you make? Did you buy them all macs? ha ha.

I don&#039;t know how many times I&#039;ve given clients a 3 choice option (because any more will confuse their precious little brains), and I sneak in one option that is the original (for fun) and they choose the original! It just proves that people like what is comfortable and expected, and don&#039;t really like change unless it&#039;s forced upon them.

But I am curious how you managed to fix this &quot;problem&quot;.</description>
		<content:encoded><![CDATA[<p>“we had to take our nice, approved design and go back to make changes”</p>
<p>I’m curious…Exactly what changes did you make? Did you buy them all macs? ha ha.</p>
<p>I don’t know how many times I’ve given clients a 3 choice option (because any more will confuse their precious little brains), and I sneak in one option that is the original (for fun) and they choose the original! It just proves that people like what is comfortable and expected, and don’t really like change unless it’s forced upon them.</p>
<p>But I am curious how you managed to fix this “problem”.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
