system — 2010-04-20T08:19:46-04:00 — #1
What solution is there to get @font-face to work for these browsers FireFox 2.0 & Mozilla 1.7.12 ? Is my only option @font-family ? Or is there a specific font type that these browsers can only read ?
ryanreese — 2010-04-20T12:19:32-04:00 — #2
Hi, IE only suppports .EOT type fonts, while others support .TTF type fonts, so you'd have to give regular browsers .TTF and feed IE a conditioanl comment .EOT font :).
I'd recommend staying away from it in general though.
system — 2010-04-20T12:22:37-04:00 — #3
I'm talking about FireFox 2.0 & Mozilla 1.7.12 not IE
ryanreese — 2010-04-20T12:25:48-04:00 — #4
I don't believe that font face is supported in browsers that old, I could be wrong though :).
logic_earth — 2010-04-20T12:44:41-04:00 — #5
There is no need for a conditional comment.
src: url( "AndaleMono.eot" );
src: local( "Andale Mono"),
url( "AndaleMono.woff" ) format( "woff" ),
url( "AndaleMono.ttf" ) format( "truetype" ),
url( "AndaleMono.svg#AndaleMono" ) format( "svg" );
paulob — 2010-04-20T12:48:39-04:00 — #6
The font-squirrel site show you which browsers are supported.
Older browsers should resort back to normal text which is the best you can do unless you want to do sifr (or similar) instead.
ryanreese — 2010-04-20T16:43:12-04:00 — #7
I did not know that, I assumed one format would override the other, tholugh thinking about it, it wouldn't because of the format types :).
I just went to sitepoints refernece on this and Mozilla isn't even listed, and FF 2 is on the unsuported list.
system — 2010-04-20T20:50:56-04:00 — #8
Basically for Mozilla and FireFox 2.0 I should just use @font-family ? I do have a TTF for Mozilla and FireFox 2.0 and there not rendering it. My only option is to include a sIRF font for those browsers?
cooper_semantics — 2010-04-20T20:54:44-04:00 — #9
alexdawson — 2010-04-21T01:38:15-04:00 — #10
Huskey, Paul was correct, @font-face is an element of CSS3! Basically it's only technically a recent "innovation" outside of Internet Explorer (who started the trend), so no... old versions of Mozilla won't support it, neither will old versions of Safari (etc). What you should always do when using font-face (no matter the browser) is have a fall-back mechanism in case someone cripples such functionality (never rely on bleeding edge stuff). This is where you use font-family and stacks. Honestly I don't know why your bothering with the old versions of gecko, very few people use them, almost everyone outside of IE upgrades their browser regularly. As for falling back onto using sFIR, why bother? not many people will see the effect and that will easily fail if they don't have scripting or flash enabled.
system — 2010-04-21T06:22:41-04:00 — #11
Basically I should have Font-Family rule in that style for fall back ? Well I'm only going to do that, I'm not even supporting IE6.
alexdawson — 2010-04-21T06:32:59-04:00 — #12
You have the custom font at the front, then you have fall-back fonts following it to ensure if the custom typeface is unavailable there is something for it to drop back onto as an alternative. Generally you want to aim for Custom Font, Font which looks closest, websafe fall-back, font style (like serif or sans-serif).
system — 2010-04-21T07:12:37-04:00 — #13
I understand, I'm just going to add a Font-family for those other browsers