I believe this is what they mean by not supporting multiple weights for a font family of the same name.

So the workaround is to declare each bold (and italic) styles as a different font-family instead of assuming that `font-weight: bold` and `font-style: italic` will take care of that. For Internet Explorer.

But would calling multiple Google Webfonts URLs be enough? The generated CSS still calls the same font-family. I'd copy the CSS but change the font-family values for each font.

The present & future of web fonts is looking awfully bright. Quality and Quantity are increasing, though there are still a few fonts I have to pass over when designing for the web. While I don’t know if all of these are in the pipeline to become web fonts, I have to believe that all type foundries are moving in that direction so that their fonts remain useful. It’s important to note that this shouldn’t be read as a “what’s the holdup” post. Creating high quality web fonts is no simple task. The only thing worse than a font you can’t use on the web is one that can be used but renders poorly.

Case in point: I recently replaced Futura served by an unnamed service with the relatively new Futura PT from ParaType served via Typekit. There was a significant improvement in tracking as well as rendering. Here’s a short, non-comprehensive list of fonts I’d love to put on a webpage.

The “Fontspring @Font-Face Syntax”
This is the way the code should have been all along. Clean, clear and simple:

@font-face {
font-family: 'MyFontFamily';
src: url('myfont-webfont.eot#') format('embedded-opentype'),
url('myfont-webfont.woff') format('woff'),
url('myfont-webfont.ttf') format('truetype'),
url('myfont-webfont.svg#webfontFqDaNIX6') format('svg');
}
What? I don't get it.
The hack trick that makes this work is the '#' following the EOT filename. Seriously.

How it works
Internet Explorer <9 has a bug in the parser for the src attribute. If you include more than one font format in the src, IE fails to load it and reports a 404 error. The reason is that IE attempts to load as a file everything between the opening parenthesis all the way to the very last closing parenthesis. To deal with that wrong behavior, you merely declare the EOT first and append a single hash mark. The hash fools IE into thinking the rest of the string is a URL fragment and loads just the EOT file. The other browsers follow the spec and select the format they need based on the src cascade and the format hint.

Browser compatibility
I see no reason why any browser would fail with this syntax. Please report your findings though. Once we feel that there are no issues, we'll change the syntax for the Fontspring webfonts.

We've tested on:

Safari 5.03, IE 6-9, Firefox 3.6-4, Chrome 8, iOS 3.2-4.2, Android 2.2-2.3, Opera 11

Fontdeck is the professional webfonts solution. You only pay for the fonts you need, when you need them. Get up and running in under 60 seconds.