<?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: Reconsidering Arial</title>
	<atom:link href="http://f6design.com/journal/2009/09/30/reconsidering-arial/feed/" rel="self" type="application/rss+xml" />
	<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/</link>
	<description>Adventures in web and graphic design</description>
	<lastBuildDate>Sun, 25 Jul 2010 23:46:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-111558</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 03 Nov 2009 00:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-111558</guid>
		<description>I&#039;m surprised to not see your article referenced in the following just publishing piece on anti-aliasing: http://www.smashingmagazine.com/2009/11/02/the-ails-of-typographic-anti-aliasing/</description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised to not see your article referenced in the following just publishing piece on anti-aliasing: <a href="http://www.smashingmagazine.com/2009/11/02/the-ails-of-typographic-anti-aliasing/" rel="nofollow">http://www.smashingmagazine.com/2009/11/02/the-ails-of-typographic-anti-aliasing/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-110175</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 08 Oct 2009 06:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-110175</guid>
		<description>Helvetica Māori - I like it! I must have dodged that bullet by &lt;strike&gt;escaping&lt;/strike&gt; leaving New Zealand right at the beginning of my design career.</description>
		<content:encoded><![CDATA[<p>Helvetica Māori &#8211; I like it! I must have dodged that bullet by <strike>escaping</strike> leaving New Zealand right at the beginning of my design career.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-110172</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 08 Oct 2009 05:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-110172</guid>
		<description>Although aesthetically spot on in your preference for Helvetica Neue, you may not be aware Jonathan that chocolate chip Helvetica was a conscious reworking by Linotype in 1983 of the vanilla favourite to standardise its heights and widths, and also includes improved legibility, heavier punctuation marks, and increased spacing in the numbers (thanks Wikipedia).

And on a Mac, I&#039;ve yet to ever have a system problem caused by Helvetica Neue, but I&#039;ve had plenty by corrupted versions of its grumpy older brother—most notoriously the hacked for macrons “Helvetica M&#x0101;ori”, which is perpetually doing the rounds in NZ design studios.</description>
		<content:encoded><![CDATA[<p>Although aesthetically spot on in your preference for Helvetica Neue, you may not be aware Jonathan that chocolate chip Helvetica was a conscious reworking by Linotype in 1983 of the vanilla favourite to standardise its heights and widths, and also includes improved legibility, heavier punctuation marks, and increased spacing in the numbers (thanks Wikipedia).</p>
<p>And on a Mac, I&#8217;ve yet to ever have a system problem caused by Helvetica Neue, but I&#8217;ve had plenty by corrupted versions of its grumpy older brother—most notoriously the hacked for macrons “Helvetica M&#x0101;ori”, which is perpetually doing the rounds in NZ design studios.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-110171</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 08 Oct 2009 05:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-110171</guid>
		<description>@Ivan - I think it&#039;s generally safe to place Helvetica first in your font stack, because Helvetica is not a system font on PC, so most people wouldn&#039;t have it installed. But as you suggest I err on the side of caution and put Arial first!

Like (I suspect) most designers I use a version of Helvetica named &#039;HelveticaNeue LT Std&#039; rather than plain old Helvetica, but the few times I&#039;ve had vanilla Helvetica activated I notice right away how fugly every second webpage looks.</description>
		<content:encoded><![CDATA[<p>@Ivan &#8211; I think it&#8217;s generally safe to place Helvetica first in your font stack, because Helvetica is not a system font on PC, so most people wouldn&#8217;t have it installed. But as you suggest I err on the side of caution and put Arial first!</p>
<p>Like (I suspect) most designers I use a version of Helvetica named &#8216;HelveticaNeue LT Std&#8217; rather than plain old Helvetica, but the few times I&#8217;ve had vanilla Helvetica activated I notice right away how fugly every second webpage looks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-110170</link>
		<dc:creator>Ivan</dc:creator>
		<pubDate>Thu, 08 Oct 2009 04:43:34 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-110170</guid>
		<description>This really makes me rethink my typical font stack I&#039;ve been using by habit.  I&#039;m thinking it should now be Arial,Helvetica for body and then Helvetica,Arial for headings.

My rule of thumb is I don&#039;t use anything less then 11px for the web, so the smaller sizes don&#039;t bother me too much.  But seeing my workhorse 11px looking so poor is pretty eye-opening. 

My other rule of thumb regarding Helvetica is to see what Khoi Vinh - who loves himself some Helvetica  - is doing on subtraction.com.  I promise I checked this after coming up with the above rule, but he uses Arial,Helvetica for body text and  Helvetica,Arial for headings. Nice!</description>
		<content:encoded><![CDATA[<p>This really makes me rethink my typical font stack I&#8217;ve been using by habit.  I&#8217;m thinking it should now be Arial,Helvetica for body and then Helvetica,Arial for headings.</p>
<p>My rule of thumb is I don&#8217;t use anything less then 11px for the web, so the smaller sizes don&#8217;t bother me too much.  But seeing my workhorse 11px looking so poor is pretty eye-opening. </p>
<p>My other rule of thumb regarding Helvetica is to see what Khoi Vinh &#8211; who loves himself some Helvetica  &#8211; is doing on subtraction.com.  I promise I checked this after coming up with the above rule, but he uses Arial,Helvetica for body text and  Helvetica,Arial for headings. Nice!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-109948</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 01 Oct 2009 21:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-109948</guid>
		<description>@Og2t - I upgraded my Safari install in the process of researching this post, and made the same discovery. I can understand why Apple made this decision, because they received a lot of flack for trying to crowbar the look/feel of the Mac OS into the Windows environment, but I think it&#039;s a shame because it was a real point of difference in Safari. The power user will know that this is a user configurable preference, but the average user will be none the wiser.</description>
		<content:encoded><![CDATA[<p>@Og2t &#8211; I upgraded my Safari install in the process of researching this post, and made the same discovery. I can understand why Apple made this decision, because they received a lot of flack for trying to crowbar the look/feel of the Mac OS into the Windows environment, but I think it&#8217;s a shame because it was a real point of difference in Safari. The power user will know that this is a user configurable preference, but the average user will be none the wiser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Og2t</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-109931</link>
		<dc:creator>Og2t</dc:creator>
		<pubDate>Thu, 01 Oct 2009 10:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-109931</guid>
		<description>I am not sure but I think the recent Safari 4 reverted back to use ClearType by default... :-(</description>
		<content:encoded><![CDATA[<p>I am not sure but I think the recent Safari 4 reverted back to use ClearType by default&#8230; <img src='http://f6design.com/journal/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-109914</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 01 Oct 2009 05:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-109914</guid>
		<description>@John - Thanks for the link. I hadn&#039;t read Joel&#039;s article before, but I am familiar with the debate about which rendering engine is &quot;better&quot;. I am one of those Windows users who, upon first firing up Win/SF3, had an &quot;ewwww, the fonts look blurry&quot; moment. But of course it&#039;s all a matter of what seems most familiar. I admit that Apple&#039;s approach has grown on me - blurry or not, it&#039;s nice to see fonts rendered the way the type designer intended.</description>
		<content:encoded><![CDATA[<p>@John &#8211; Thanks for the link. I hadn&#8217;t read Joel&#8217;s article before, but I am familiar with the debate about which rendering engine is &#8220;better&#8221;. I am one of those Windows users who, upon first firing up Win/SF3, had an &#8220;ewwww, the fonts look blurry&#8221; moment. But of course it&#8217;s all a matter of what seems most familiar. I admit that Apple&#8217;s approach has grown on me &#8211; blurry or not, it&#8217;s nice to see fonts rendered the way the type designer intended.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://f6design.com/journal/2009/09/30/reconsidering-arial/comment-page-1/#comment-109910</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 01 Oct 2009 04:41:31 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/?p=464#comment-109910</guid>
		<description>Nice post Jonathan. Found an interesting article by Jole Sposky on the differences between the Microsoft and Apple font rendering engines, which he attributes to being mainly a difference in philosophy, namely “form” vs “function”: http://www.joelonsoftware.com/items/2007/06/12.html</description>
		<content:encoded><![CDATA[<p>Nice post Jonathan. Found an interesting article by Jole Sposky on the differences between the Microsoft and Apple font rendering engines, which he attributes to being mainly a difference in philosophy, namely “form” vs “function”: <a href="http://www.joelonsoftware.com/items/2007/06/12.html" rel="nofollow">http://www.joelonsoftware.com/items/2007/06/12.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
