Comments on: @font-face Coming to a browser near you

By: Idle Hacking » More on @font-face

Idle Hacking » More on @font-face — Thu, 20 Aug 2009 15:58:38 +0000

[...] in December 2008, I put together an example of using @font-face and described some of the deficiencies of using the Microsoft font format eot. It turns out that I was wrong and corrected on the quality [...]

By: mohammod

mohammod — Fri, 14 Aug 2009 14:00:00 +0000

That was not a fair test. I presume you obtained the IE6 results on a Windows platform (WinXP?) and others on Mac/Linux platfrom, am I right?

The reason of the font being “jagged looking” is not down to the browser itself, however, it’s because of the OS. If you have got the right settings at Control Panel (turning on the ClearType feature), you will see that the problem is solved. IE6 is actually able to display text in antialias manner in fact.

You are not the first one I have seen mistakenly blaming the problem on IE, but I just want to emphasize this is Windows’ default setting, not because of the handicapped IE6.

By: Andrew

Andrew — Sun, 08 Feb 2009 07:39:11 +0000

I use a custom font on my blog, and I have some more findings that you may be interested in. Chrome does not support @font-face at all - I am not sure why since it is using the same layout engine as Safari. Safari tends to render fonts with a lot more weight than Firefox - a lot of custom fonts tend to look skinny and unattractive in Firefox. Professionally designed fonts with proper hinting look fine in both. EOT is a pox on mankind - the sooner Microsoft stops trying to peddle that idiotic format the better. The good news is that in a few months the majority of browsers (Safari, Opera and Firefox) will all have mainstream @font-face support. Andrews last blog post..A Better Handwriting Font with YourFonts.com