Re: Problem with narrow vs condensed fonts

[Stefan Monnier]

>>> > But, as you changed the numeric value of of `normal' weight
>>> > from 100 to 101, ftfont_list doesn't include regular weight
>>> > font (most of ttf has regular weight).

>>> Why does it only accept an exact-match?

>> Because that's the spec I desided for that API of (struct
>> font_driver *)->list.  I wanted to distinguish required
>> (i.e. mandatory) font-spec and preferred font-spec.  `list'
>> returns fonts matching with a required spec, and
>> font-selection routine find a font besting matching with
>> preferred spec from them.

>> So, we should not give FONT-SPEC containing just preferred
>> specs to `list'.

> Right: the defaulting to "normal" should be done when the value is later
> used as a preferred spec, but a wildcard should be used instead if the
> value is later used as an exact spec.

Or rather the defaulting to "normal" should be done elsewhere: when
choosing the preferred font for a SPEC which doesn't specify any weight.


        Stefan