W3C home > Mailing lists > Public > www-style@w3.org > October 2009

Re: font features in CSS

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 31 Oct 2009 09:40:49 +1300
Message-ID: <11e306600910301340r26b68839j845b8aa0b7cccd13@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: Thomas Phinney <tphinney@cal.berkeley.edu>, Bert Bos <bert@w3.org>, www-font@w3.org, www-style@w3.org
On Sat, Oct 31, 2009 at 9:25 AM, fantasai <fantasai.lists@inkedblade.net>wrote:

> Thomas Phinney wrote:
>
>>
>> Yes, the appropriateness is font-specific, but with @font-face we are
>> soon going to be fairly sure about what font we are getting, much of
>> the time (and with the font fallback stack we can be sure to specify
>> as fallback something that is unlikely to trigger an undesired result
>> for selecting alternate ampersand #27).
>>
>
> I think you're much too optimistic about this. Maybe on desktops in
> the broadband world there will be enough consistency that you can
> ignore the few percent of anomalies, but in other environments font
> downloads are just as likely to be either not available for the
> device/OS or turned off due to limited download speeds or memory.
>

In a @font-face rule where you specify alternates, you could use a single
'src' value and be sure that if the file is not loaded, the alternates will
not be applied, and do your fallback in font-family rules in the content.

If that turns out to be too cumbersome, we could extend @font-face so that
you can associate font options with particular sources.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
Received on Friday, 30 October 2009 20:41:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:21 GMT