Hands in the air, anyone actually using @font-face in a commercial project

Frode Bo Helland's picture

There are two major drawbacks with @font-face at the current state, IMO: The subscription model (exception for Typotheque) and the unreliable browser rendering. Both makes me uneasy about using web fonts for anything but playing around.

Have any of you actually relied on @font-face in real life projects?

ralf h.'s picture

FF Meta for Firefox: http://www.mozilla.com/en/firefox/3.6/whatsnew/

The Typekit blog also lists featured sites with webfonts: http://blog.typekit.com/

aluminum's picture

There's beginning to be a nice collection of very usable open source and/or freely licensed stuff out there that makes the subscription issue less of an issue.

However, the lack of proper anti-aliasing (at least in Firefox) really turns me off still.

I wasn't aware that WOFF has come to FF, though. Good news!

Don McCahill's picture

Can I put my hand down now?

Garrick Van Buren's picture

Kernest displays thumbnails of the sites it's serving fonts to.

Just a reminder: @font-face use doesn't require a third party service, so the only way to know - is to check the site's CSS. Honestly I've been pleasantly surprised by the font stacks I've been seeing lately.

nina's picture

I'm currently trying out a couple of weights of Fedra Sans Alt on my own site, as sort of a test. It seems that rendering quality on Windows is a real issue? I must admit I'm not really up to date with all the background; to be on the safe [but still somewhat progressive :-) ] side, I think I'll limit it to titling at the moment, and only in situations of course where fallback fonts are also OK, so that the @font-face becomes sort of a «bonus» for those people who can see it.

Thomas Phinney's picture

"However, the lack of proper anti-aliasing (at least in Firefox) really turns me off still."

This is the OS, has very little to do with Firefox per se.

T

Syndicate content Syndicate content