@font-face Generator Expectations
Hint: Keep Them Low
We are all very excited to finally see browsers support some form of font embedding. Hurray you get to use any font you want now. While we were all celebrating that fact, the elephant in the room started trumpeting...
That elephant is named Windows. Here’s the short of it: Windows browsers do not render type well unless you have a perfectly hinted TrueType font. OpenType (OTF) fonts don't rendered well, unhinted TrueType don't render well, and even "auto-hinted" TrueType don't render well. Update: I changed my mind. The Font-Face Generator does a pretty good job of auto-hinting. Try it out and see.
Many Font Squirrel users have become frustrated that their OTF files that are being run through the Generator come out looking like a pixelated mess. Particularly bad are fonts that are light and thin.
So what should you do about it? My recommendation is to:
- Stick with the standard font stack for body copy until Microsoft can deliver a better rasterizer to most of your users.
- Use custom @font-face fonts for headlines and other "big" type. The bigger the type, the less noticeable the rendering.
- Always start with a TrueType font if you can help it.
You will be disappointed by most of the converted @font-face fonts you see in Internet Explorer and Firefox for Windows. And we don't think it is our fault. Just look at how nice a Mac renders! Again, I changed my mind. The type coming out of our Generator is looking pretty good now!
Comments
November 7, 2009 at 06:00 PM
@Charles - I agree. DirectWrite seems to be the last domino that needs to fall to get all this going. I'm actively working to get better rendered fonts out of the Generator, but haven't gotten there yet.
November 7, 2009 at 09:48 PM
http://www.basschouten.com/blog1.php/2009/10/27/font-rendering-gdi-versus-directwrite
What is *particularly* interesting is this quote: "I've been working for Mozilla on implementing DirectWrite as a Cairo and gfxFont backend."
Sweet!
November 10, 2009 at 02:53 AM
http://blog.mozilla.com/nattokirai/2009/10/22/better-postscript-cff-font-rendering-with-directwrite/
DirectWrite rendered Calluna looks *gorgeous*.
November 10, 2009 at 03:06 AM
November 18, 2009 at 02:14 PM
November 19, 2009 at 09:50 AM
i'm very excited about embedded fonts and i'll drop a mail to a few of my friends. unfortunately most people i know don't know about sifr. this could be a long road :)
btw, chrome is rendering the fonts nicely for me on windows. even ie6 is looking okayish. but ff3.6 isn't antialiasing.
November 27, 2009 at 06:42 AM
November 27, 2009 at 06:45 AM
December 1, 2009 at 01:51 PM
December 8, 2009 at 03:49 AM
December 11, 2009 at 04:04 AM
January 6, 2010 at 02:58 PM
I'm running FireFox 3.5.6 on XP and the site loads @font-face fine. Not sure what might be the issue for you...
January 6, 2010 at 03:01 PM
January 8, 2010 at 05:21 PM
Just one thing, anybody knows why Netscape has no support for font-face? Does it require a special type of font? (I heard something about support for "PFR" format..) If anyone knows anything about Netscape, any links, PLEASE let me know!! I'll link to your website from mine (and to Squirrel too!)
January 17, 2010 at 07:17 AM
"I am noticing that none of the kits work in firefox 3.5 on my pc. Even the font used on this site and the examples of the kits. I was wondering if this is unique to me or if anyone else is experiencing this? BTW this is firefox 3.5/IE6 on windows XP."
and
@ Ethan Dunham
"I'm running FireFox 3.5.6 on XP and the site loads @font-face fine. Not sure what might be the issue for you..."
First, I am the absolute zero in font embedding but have had an interest in the subject for years.
Today I sumbled on fontsquirrel and experienced the same problem as mentioned. On one PC it worked fine both with Netscape and IE. On another one it was fine with IE but not Netscape. On the third one the same as the second one. Trying the base64 encoding made it work fine with Firefox on all three but crippled IE on all three.
Found that, without base64, it only works with a Firefox version higher than 3.5.0. I don't know about versions lower that 3.5.8, apart from what Ethan says about 5.3.6, but I found that as from 5.3.8 on it is OK. This leaves us with a problem: if people don't update Firefox ...
Would it (for the time being) be a solution to include a browser detector and for earlier Firefox versions point to the base64 css? How to do that? No idea. I am also an absolute javascript zero - alas.
March 9, 2010 at 11:59 AM
March 10, 2010 at 08:59 AM
However, it struck me afterward that there is two unintended consequences of creating webkits in this manner:
1- as the webkit is retained in the browser cache, if I later wanted to use the full font, the full downlable version will be ignored and the local version used instead with unintended consequences to the page
2 - is someone else saves the font from the download, they probably will not realized that it a crippled version of the original. This can, in time, lead to a pollution of the web will all manner of crippled fonts without anyone realizing it.
To avoid these potential problems, is it possible to modified the generator to create a webkit containing the .ttf, .eot,. woff and .svg with a new font name such as 'dutch_initials_normal_LTD.ttf' (LTD => limited) or 'dutch_initials_normal-TRUNC.ttf' (trunc => truncated)?
April 19, 2010 at 09:57 AM
April 24, 2010 at 09:52 AM
Thanks for a good tool for designer specially.
i m facing i problem while using the font kit generated is while looking the site in windows 7 and linux the generated font doesn't work.
please give me an ideal if u have to fix this problem
Thanks
May 5, 2010 at 08:05 AM
The type on our site - http://www.m360ltd.co.uk/ - works well in Chrome, Firefox(3.6), Safari and IE8... first gen iPhone Safari no luck but better than no display at all through Flash!
Tom
June 3, 2010 at 12:02 PM
I have noticed a couple of problems though. I tried converting a font with greek letters (the unicode range for html entities ω τ etc) and even though i don't use subsetting (and the glyphs are there after converting, i checked with fontforge), they don't show up with woff and eot fonts.
It seems that only the latin and latin-1 supplement planes are there (working correctly) and i can't access the glyphs in latin extended.
June 20, 2010 at 12:02 PM
July 19, 2010 at 10:14 AM
August 9, 2010 at 07:40 PM
August 9, 2010 at 09:22 PM
August 19, 2010 at 02:03 AM
August 26, 2010 at 04:59 PM
August 26, 2010 at 05:01 PM
Now i stumbled over a strange issue - IE9 Beta does not show it. All the fonts on your page are correctly "replaced" but if i download a fontpack from here it does not work on my server.
Please help
September 23, 2010 at 12:35 PM
I've played with @font-face using .ttf, up 'til now, only Firefox users have had the benefit of my "genius" !
Now, with your kits, I'll have cross browser support.
Brilliant !
October 29, 2010 at 06:14 AM
So far only cleartype in IE 7/8 can be turned off (via some CSS). I cannot figure out how to do this in firefox or chrome or safari.
As much as I'd love to use @font-face, I can't until a work around is found because the results in Windows Vista/7 look attrocious.
October 30, 2010 at 09:55 AM
I thank you Fontsquirrel, I like the font-generator feature and the prepackaged font-face.
This is the greatest font site I ever visited. Thanks again.
November 11, 2010 at 11:26 AM
If I use only the TTF format it's just ok (Win 7, Chrome/FF/IE), I only have this issue when converting the TTF font into the other ones through this generator.
Is there a way you could look into this problem?
Thanks in advance!
November 30, 2010 at 10:50 AM
When I use Persian fonts, It converts them to Tahoma. Is there anyone can help me?
I think it has problem :)
Please notify me by mail for any reply ;)
ali @ namnam . ir
November 20, 2011 at 04:22 PM
Submit a Comment
Comments are closed.
Font Squirrel relies on advertising in order to keep
bringing you great new free fonts and to keep making improvements to the web font generator.
If you are seeing this message, you probably have an ad blocker turned on. Please consider
disabling it to see content from our partners.
Alternatively, you can support Font
Squirrel by purchasing a paid license from our sister site,
Fontspring.
Unfortunately I encountered a problem with at least one of the fonts. The eot-file is missing and I also couldn't generate it by uploading the ttf-file and using your generator. Is there anything I can do? Except installing WEFT on my PC - :-(( ?
November 7, 2009 at 03:44 AM