Comments on: Font-face Support Table http://mwhenry.com/blog/2009/12/font-face-support-table/ A blog by Matt Henry Sat, 24 Jul 2010 16:57:26 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Mike McElligott http://mwhenry.com/blog/2009/12/font-face-support-table/comment-page-1/#comment-45 Mike McElligott Tue, 16 Feb 2010 22:48:49 +0000 http://mwhenry.com/blog/?p=84#comment-45 Hey Matt, great entry. I've been killing myself over attempting to add Hebrew characters to AlphaCards, my flashcard app for WebOS. What's frustrating is that it looks like WebOS actually downloads the font (from the load time for given characters being displayed on-screen), but then doesn't use it. Hey Matt, great entry. I’ve been killing myself over attempting to add Hebrew characters to AlphaCards, my flashcard app for WebOS. What’s frustrating is that it looks like WebOS actually downloads the font (from the load time for given characters being displayed on-screen), but then doesn’t use it.

]]> By: Matt Henry http://mwhenry.com/blog/2009/12/font-face-support-table/comment-page-1/#comment-36 Matt Henry Wed, 09 Dec 2009 00:14:44 +0000 http://mwhenry.com/blog/?p=84#comment-36 It's anybody's guess really. Theoretically, we should be there soon given how the percentage of smartphones that use WebKit-based browsers. But as the table shows, being "Webkit-based" doesn't mean a whole heck of a lot, since Android and PalmOS use Webkit browsers but don't support @font-face at all. Mozilla's Fennec (at least the version that ships with Nokia's Maemo OS on the N900) is good but not great. It renders TTF okay, but renders OTF at a smaller size, and doesn't support SVG or WOFF, despite being based on Firefox 3.6. So, like a lot of things in mobile development, if you're willing to bet that most of your users are using iPhones, you can go ahead and use all of the cool new toys. Even if they aren't, as long as you're smart about picking your font stack in such a way that your layout doesn't blow up and things still look pretty okay if your custom font isn't supported, then you can still use @font-face. I need to do more poking at Maemo & Fennec, and when I do I'll update the table. It’s anybody’s guess really. Theoretically, we should be there soon given how the percentage of smartphones that use WebKit-based browsers. But as the table shows, being “Webkit-based” doesn’t mean a whole heck of a lot, since Android and PalmOS use Webkit browsers but don’t support @font-face at all.

Mozilla’s Fennec (at least the version that ships with Nokia’s Maemo OS on the N900) is good but not great. It renders TTF okay, but renders OTF at a smaller size, and doesn’t support SVG or WOFF, despite being based on Firefox 3.6.

So, like a lot of things in mobile development, if you’re willing to bet that most of your users are using iPhones, you can go ahead and use all of the cool new toys. Even if they aren’t, as long as you’re smart about picking your font stack in such a way that your layout doesn’t blow up and things still look pretty okay if your custom font isn’t supported, then you can still use @font-face.

I need to do more poking at Maemo & Fennec, and when I do I’ll update the table.

]]> By: Ian Homer http://mwhenry.com/blog/2009/12/font-face-support-table/comment-page-1/#comment-35 Ian Homer Tue, 08 Dec 2009 23:31:23 +0000 http://mwhenry.com/blog/?p=84#comment-35 Hi - great analysis on this topic, thx. Have you seen any clues as to when font-face support is coming to mobile? We're itching to get better font control on mobile. Hi — great analysis on this topic, thx. Have you seen any clues as to when font-face support is coming to mobile? We’re itching to get better font control on mobile.

]]>