Re: Lucida Sans/Grande/Unicode matching confusion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 1, 2012 at 10:04 AM, S Page <skierpage@xxxxxxxxx> 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 :
https://bugs.freedesktop.org/show_bug.cgi?id=13416
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
experienced.

> 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...

-- 
Akira TAGOH
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig


[Index of Archives]     [Fedora Fonts]     [Fedora Users]     [Fedora Cloud]     [Kernel]     [Fedora Packaging]     [Fedora Desktop]     [PAM]     [Gimp Graphics Editor]     [Yosemite News]

  Powered by Linux