You would set up your font stack such as: h1{font-family: 'mycustomfont',
arial, helvetica, sans-serif;} the fallback being arial, etc which would
display if the custom-for whatever reason-didn't.
Sent from my iPhone
On Sep 25, 2011, at 2:44 PM, Elli Vizcaino <[email protected]> wrote:
>
>>> Wanted to know the level of support w embedding fonts and if it will
>>> require Javascript to enforce compliancy w all major browsers?
>>>
>>> Elli
>>
>> Support for @font-face is excellent including our friends IE 6/7/8/9. Not
>> supported in Camino at least at present. Nor in OperaMini [a mobile
>> browser]. However, with a decent fallback font you are still good to go. No
>> js required for open-source [free] webfonts from a repository such as
>> FontSquirrel.
>>
>> Best,
>> F. Goudy
>
>
>
> Thanks David! When you wrote "fallback font" - how should this be set up in
> the CSS? Can you elaborate?
>
> Elli Vizcaino
> Web Designer & Developer
> http://www.E7Flux.com
> The Best Compliment We Can Receive Is A Referral!
> ______________________________________________________________________
> css-discuss [[email protected]]
> http://www.css-discuss.org/mailman/listinfo/css-d
> List wiki/FAQ -- http://css-discuss.incutio.com/
> List policies -- http://css-discuss.org/policies.html
> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/