Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: not2easy
Is there a way for modern browsers to force a font download
There's an example at
and it only really works in safari/chrome, most recent versions of Firefox and Opera still get it wrong.
I think you should do it the other way around and use regular fonts in the flash as well as not expect identical fonts that are going to be used by the browsers anyway.
but be ready to see major differences between browsers (as usual IE is by far the most deviant -also in IE8-)
This is flat-out misinformation. In IE, if a font is converted to an EOT file (or an EOTL file - EOT without any DRM root-string stuff), the font will render exactly as it does when it's installed in the operating system. Exactly.
The browser makes no distinctions.
Using TTF or OTF files, the same goes for FF 3.5, Safari, Opera 10, and Chrome launched with web fonts enabled.
The font will be treated the same as if it was locally installed.
There are, however, differences in the CSS syntax that have to be juggled a bit. But that's got nothing to do with the rendering quality.
I don't know what the problems are with the sample page you cite but there are plenty of examples now with web fonts working in every latest browser. And more being created every day.
search: web fonts panorama
This is flat-out misinformationI was referring to the lack of support of IE for truetype and opentype , both of which are supported by the underlying windows OS. There's no reason why IE should not support it and demand that horrible .eot format only (a format no other browser will touch AFAIK).
If you read the CSS3 spec [w3.org] as it stands today, there is AFAIK no "a UA might just choose to only support one of the font encodings" provision. There are platform limitations etc. that allow font-face to be ignored, but none of them lets a browser dictate "one format only", when the platform supports the provided fonts.
As a matter of fact, as it stands today, IE will not work with *any* of the examples in the standard ...
It's the usual tactic of MSFT when faced with standards, nothing new, they did the same with all of CSS for many years, and still do the same with SVG, CSS3, etc.