W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [css3-fonts] "font-feature-settings: none" shorthand?

From: Glenn Adams <glenn@skynav.com>
Date: Thu, 30 May 2013 10:57:18 -0600
Message-ID: <CACQ=j+eW6=RwUt0sm=V6ATONDFH2kP_g=HW22sZApaadDiL39g@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: W3C Style <www-style@w3.org>
On Wed, May 29, 2013 at 11:35 AM, fantasai <fantasai.lists@inkedblade.net>wrote:

> On 05/29/2013 01:03 PM, Tab Atkins Jr. wrote:
>
>> On Wed, May 29, 2013 at 9:11 AM, Glenn Adams <glenn@skynav.com> wrote:
>>
>>> It would be useful to have a shorthand on font-feature-settings that is
>>> the
>>> same as enumerating all features and specifying 'off' for each feature.
>>>
>>
>> Agreed.  As a general principle, any list-valued property should accept
>> "none".
>>
>
> Um, this makes no sense at all. There's a 'normal' keyword, which does the
> appropriate thing and undoes what font-feature-settings does. There's
> absolutely no reason to have a feature that turns all OpenType features
> unilaterally off.


I respectfully disagree. In discussing an early implementation of this
property in the Apache FOP project (as an extension for XSL-FO), a user has
asked for the ability to turn off all font features unilaterally. For their
use cases, they offer that for experimentation with font features (in
general), they want to experiment with behavioral results, and want to turn
off all features without having to specify all features individually or
have to know which features are supported and specifying them as off as a
subset of all features.

These users are not in the position of creating a custom font.


> Even if there was a reason, it'd be the 0.000000000000001%
> use case, at which point, just make a custom font without any features.
>
> ~fantasai
>
>
Received on Thursday, 30 May 2013 16:58:09 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 30 May 2013 16:58:09 UTC