Will somebody please make a drag-and-drop ttf/otf -> .eot app? Then we can all get on with our lives. For the better part of a decade, Microsoft has held us back from doing good type on the ‘web. There’s a command-line solution in linux, what about something that Mac and Windows people can get into?

Good old CamelCase. Nice catch, Stephen. I updated the post.

@Rebecca,

Professional _developers_ will be able to assess if a beta product is worth using in their _professional_ sites.

sIFR3 has been rock solid for years, though admittedly not straightforward to implement for someone without a minimal JavaScript knowledge.

Websites from high profile companies and high profile developers have been using it just fine.

@Veen, I don’t know if you already have, but should contact Mark Wubben. He knows this stuff. Has been debugging it for years.

sIFR 3 is still technically beta. Developers will not risk putting beta scripts on professional sites.

Hmm, this looks like an excellent opportunity to shamelessly promote my font subsetting code! It’s not really a usable tool by itself, but it could be used in one – it aims to handle high quality fonts (preserving ligatures etc), and it seems to work fine in practice, and if there are any problems I could probably be motivated to fix bugs and missing features 🙂

But what will determine the success of this project is the cross-browsebility. I, as many, project my sites, and first test in the latest versions of the browsers, but make it work in older versions, mainly in internet explorer 6 and 7, unhapply is still needed. We can’t just say to the clients of our clients that they have to atualise their browsers or they wont be able to see our site. Mostly, we can’t tell our clients that their clients has to do it. So, this is a fundamental part, becase we can’t just do two versions of the site, using image in one. So we prefer use images in both.

Other thing, It has to load fast. You must know an aplicative called ienpgfix. This is a little script that allow ie6 users to see tranparent png in the sites. But it make even in broadband the site a little, very little, but still considerable slow to load. And it kills this script.

The iniciative is really GREAT! Hope to use it as soon as possible!

I’m also curious about what implementation methods turn out to be the most popular. I hope this information is released at some point, as it gives the rest of us a specialized look at how modern sites are built. While I would ideally retain direct CSS control, this might not be the case for everyone, and awareness of that would help guide future decisions.

Very good point Matt. I am also curious, as direct font linking implies a different model than I’d been lead to believe (JS-based licensing/DRM). Server-side makes more sense to me than a JS authentication key, but all of this is still very much in the air as far as public information goes.

Regardless, sensible automation of EOT vs OTF/TTF is a valuable feature in its own right. Anyone who’s attempted a combo @font-face/EOT solution in the past will greatly welcome a service that does it for them, even if it’s only serving freely licensed fonts.