[Fontconfig] Lucida Sans/Grande/Unicode matching confusion

Akira TAGOH akira at tagoh.org
Tue May 1 01:11:16 PDT 2012

On Tue, May 1, 2012 at 10:04 AM, S Page <skierpage at gmail.com> wrote:
> The current behavior isn't "do the right thing" for a naive user. If I
> install a font that is obviously much closer to other font families
> than the O.S. default, it's strange that fontconfig doesn't pick it
> unless I write some configuration info.

I think it's a known and long standing issue :
it needs to be fixed/improved in the future.

> Is fontconfig even intended to know about font families that aren't
> installed so it can pick the closest matching font given a name?

It doesn't do more than comparing the names for family name so far,
unless having any particular rules for alternatives, as you

> That's been the PANOSE/OS2 sFamilyClass dream for decades; it seems
> from a few web documents using the abandoned CSS panose-1 property
> that Lucida and Lucida Sans share the same "2 11 6 2 3 5 4 2 2 4"
> panose-1 digits.

We have a RFE for that too I think...


More information about the Fontconfig mailing list