Hey everyone, I was just wondering how compliant using font-face in CSS3 is, to render a custom font on a user's browser.
What's the browser support like?
What versions do not support this?
Thanks,
Mike
I was slow to adopt this, but
I was slow to adopt this, but I've just jumped on the bandwagon, and it works surprisingly well. As long as you have some extra code (and the EOT file format) for IE, I even got it working in stupid IE6. It was good in Firefox Win and Mac, Safari Win and Mac, too. So I'd say it's pretty well supported.
The main reason I was slow in
The main reason I was slow in adopting this technique was the poor quality of the fonts that aren't already on people's computers.
Very poor anti-aliasing causing jagged edges. You really have to experiment with them before you'll find one that is acceptable to use. It's really a big surprise because they look fantastic on a Mac and then you look on a Windows box and it looks like an old Atari 2600 font made out of huge blocks. 8-bit, woot!
That's very true... even if
That's very true... even if it works, you must have non-sucking font files. I've found that various versions of the same font may differ considerably. If in doubt, you simply avoid free fonts, pay for a nice one, and pass the cost along to the client.
And having good taste in font selection wouldn't hurt. In the site where I just implemented this, the file is good quality, nice and smooth, but as it happens, I don't like it. But as long as the client does, hey, whatever.
So as font-face becomes very widespread maybe bad fonts will become the "blink tags" of our era. 
flamenco wrote:... If in
... If in doubt, you simply avoid free fonts, pay for a nice one ...
Well, that's no guarantee either. I have a rather nice looking font that I purchased for a client to use with sIFR. It seems to work well in that context but using it via embedding makes it just looks like garbage. That's rather disappointing.
I'd show an example but it's on my broken down Mac. 
