- From: Glenn Adams <glenn@skynav.com>
- Date: Thu, 30 May 2013 10:59:16 -0600
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: W3C Style <www-style@w3.org>
- Message-ID: <CACQ=j+eG0NCKNh-m5HG2UhmN=kOKBH695Wh4si5nmS6AXNkm5A@mail.gmail.com>
On Thu, May 30, 2013 at 10:57 AM, Glenn Adams <glenn@skynav.com> wrote: > > > 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. > I guess I should add that I plan to support a generic 'none' value no matter whether [css-fonts] adds it to the spec. > > >> 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 17:00:07 UTC