W3C home > Mailing lists > Public > www-style@w3.org > March 2010

Re: [css3-fonts] opentype font feature support

From: Thomas Phinney <tphinney@cal.berkeley.edu>
Date: Thu, 4 Mar 2010 15:30:46 -0800
Message-ID: <f49ae6ac1003041530s1eff9344t76ac6d73e980b56e@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, robert@ocallahan.org, Jonathan Kew <jonathan@jfkew.plus.com>, www-style list <www-style@w3.org>
On Thu, Mar 4, 2010 at 2:36 PM, Håkon Wium Lie <howcome@opera.com> wrote:
> Also sprach fantasai:
>
>  > >      > 6.1 font-kerning: normal | inherit | enabled | disabled
>  > >      >
>  > >      > There are few properties that use generic on/off state names like
>  > >     ‘enabled’ and ‘disabled’. I would prefer not to see more of them,
>  > >     but I do not know which pair of words would be better here, ‘kern’/?
>  > >     perhaps.
>  > >
>  > >     I'd be happy to hear alternative suggestions, although as the draft
>  > >     does not currently include font-kerning as one of the properties
>  > >     controllable via the font shorthand, I don't think the generic
>  > >     "enabled" and "disabled" are particularly problematic here.
>  > >
>  > > How about just naming them 'kerning' and 'no-kerning'? If 'font-kerning:
>  > > kerning' is too weird, perhaps rename 'font-kerning' to
>  > > 'font-glyph-spacing'?
>  >
>  > I'd go with font-kerning: normal | kern | no-kern
>
> We have:
>
>  hyphens: none | manual | auto
>
>  http://www.w3.org/TR/css3-gcpm/#hyphenate
>
> How about:
>
>  font-kerning: none | normal | auto

I don't much care for "auto" here. Surely "kern" could be used and
would be clear enough.

T

-- 
"The rat's perturbed; it must sense nanobots! Code grey! We have a
Helvetica scenario!" — http://xkcd.com/683/
Received on Thursday, 4 March 2010 23:31:21 GMT

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