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

Re: font features in CSS

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 30 Oct 2009 10:41:25 -0700
Message-ID: <4AEB2545.2@inkedblade.net>
To: Bert Bos <bert@w3.org>
CC: www-font@w3.org, www-style@w3.org
Bert Bos wrote:
> 
> Yes, we should choose names that match the style of the other keywords
> in CSS. No need to copy the naming style of OpenType or other font formats.
> 
> Moreover, I don't think it is a requirement that CSS supports all OT
> features. A handful of the more common ones is enough. If a designer
> wants a specific feature of a specific font, he can make a new font (or
> a virtual font) in which that feature is turned on. That's what we have
>  @font-face for.
> 
> We don't provide ways either to replace colors in a JPEG or change a
> circle to a square in an SVG. The designer just makes a new image with a
> new URL. That's a more flexible and modular solution.
> 
> I think we should provide keywords for small caps (already done) and
> oldstyle figures, and maybe one or two more. But if a font has half a
> dozen different ampersands and the designer really wants the fourth
> variant, he should make a font with that glyph. (Or maybe he actually
> meant to use an image?)

I agree with Bert's position here. For a lot of these less common features
(and by common, I mean common to fonts, not just commonly used), the values
and their appropriateness is very font-specific. That says to me that it
should be in the @font-face rule. Triggering alternate glyph set #2 when you
have no guarantee of what font ultimately gets used seems like a good way
to introduce cross-platform problems.

~fantasai
Received on Friday, 30 October 2009 19:15:30 GMT

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