W3C home > Mailing lists > Public > www-style@w3.org > August 2015

Re: Proposal: add a "small-caps" value to "font-synthesis"

From: Alan Stearns <stearns@adobe.com>
Date: Wed, 12 Aug 2015 13:26:19 +0000
To: John Daggett <jdaggett@mozilla.com>, "Myles C. Maxfield" <mmaxfield@apple.com>
CC: www-style list <www-style@w3.org>, Ted O'Connor <eoconnor@apple.com>
Message-ID: <D1F091B3.2BF83%stearns@adobe.com>
On 8/11/15, 10:25 PM, "John Daggett" <jdaggett@mozilla.com> wrote:

>
>> Are there any other opinions on this issue?
>
>Thinking about this a little more, I don't think we should add
>'small-caps' to the 'font-synthesis' property. The CSS Fonts spec
>defines *required* fallback behavior when 'font-variant' is set to
>'small-caps' and the font lacks small caps glyphs. This is different
>from the way font selection works for the synthetic bold and italic
>cases, those are basically *optional* features added by the user agent.

While it’s true that the specification uses different RFC 2119 terms
(should versus may), I’m not sure it should have. Bold and italic
synthesis are technically optional but in practice ubiquitous, to the
point that font-synthesis is required to be able to opt out.

I don’t see a big distinction between the cases presented. Bold and italic
synthesis *may* (but usually does) happen, and font-synthesis allows you
to block it. Small cap synthesis *should* happen, and we should not have a
way of blocking it? Why shouldn’t I be able to express “Use small caps
glyphs only if they’re available”?

Thanks,

Alan

Received on Wednesday, 12 August 2015 13:29:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 August 2015 13:29:41 UTC