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

Re: [css3-fonts] font descriptor default values

From: Adam Twardoch <list.adam@twardoch.com>
Date: Thu, 05 Mar 2009 01:19:08 +0100
Message-ID: <49AF1A7C.3080109@twardoch.com>
To: Brad Kemper <brad.kemper@gmail.com>
CC: John Daggett <jdaggett@mozilla.com>, Thomas Phinney <tphinney@cal.berkeley.edu>, www-style <www-style@w3.org>
Brad Kemper wrote:
> If the font file itself contains information about optical sizes to use,
> such as with multiple-master fonts, then ideally the UA would use the
> right optical size based on the used font-size, right?

Multiple Master fonts are a defunct format so it's not practical to
implement them, but optical sizes are supported in OpenType fonts (using
a special GSUB "size" OpenType Layout feature).

A.

> 
> 
> 
> On Mar 4, 2009, at 12:45 PM, John Daggett <jdaggett@mozilla.com> wrote:
>>>>> Or the lack of font properties to sufficiently delineate full font
>>>>> families?
>>>>
>>>> That's also a problem. The notion of properties only goes so far: in
>>>> the real world, some members of font families are distinguished by
>>>> arbitrary design variations that don't necessarily match the simple
>>>> weight/width/slope model. Optical size is the obvious and most
>>>> common one, and could be done as a property, but there are plenty of
>>>> simply arbitrary differences that are not amenable to a "property"
>>>> approach, and are best dealt with as an additional string.
>>>
>>> That being said, weight/width/slope handles maybe 95% of the fonts out
>>> there, and is a great advance over just bold and italic.
>>
>> Optical size as a separate axis of variation is interesting.  I know
>> Adobe ships with font families that include optical size variations but
>> is this commonly used by other font vendors?
>>
>>>> It would be helpful to hear solutions you think might solve this
>>>> "fundamentally broken" model.
>>>
>>> Two things need to be done:
>>>
>>> - clearly define what version of "family" name should be used
>>>
>>> - define appropriate means to disambiguate fonts which are not
>>> distinguished by weight/width/slope alone. Perhaps add a property for
>>> optical size, and the ability to specify an arbitrary string for part
>>> of the name.
>>
>> Interesting, so the arbitrary string would map to what exactly?  You're
>> thinking of something WPF-ish where you try and match this against some
>> part of the style name?  Style name localizations are a big headache
>> here.  If only there were named variation axes... ;)
>>
>> Regards,
>>
>> John
>>
> 
> 


-- 

Adam Twardoch
| Language Typography Unicode Fonts OpenType
| twardoch.com | silesian.com | fontlab.net

I hate to advocate drugs, alcohol, violence, or
insanity to anyone, but they've always worked for me.
(Hunter S. Thompson)
Received on Thursday, 5 March 2009 00:19:56 GMT

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