[Fontconfig] Lucida Sans/Grande/Unicode matching confusion

Raimund Steger rs at mytum.de
Tue May 1 08:52:36 PDT 2012


Akira TAGOH wrote:
> Well, actually it's not alias specific but can see same behavior when
> having multiple strings in<test>.
> https://bugs.freedesktop.org/show_bug.cgi?id=33644#c12 and
> https://bugs.freedesktop.org/show_bug.cgi?id=33644#c17 may helps to
> understand what happened there.

I've read the comments now, and it sounds rather difficult to get it 
right. (I typically work around such situations by duplicating rules in 
the config, i. e. effectively appending/prepending my edits several 
times during config substitution.)

I think that most users, when they use multiple families in the upper 
part of <alias>, think of something like:

   "Now if I use <accept>, then append after the last occuring
    value out of the ones I just specified"


   "If I use <prefer>, then prepend before the first occuring
    value out of the ones I specified"

I. e. maybe something like having FcConfigMatchValueList() return first 
_and_ last match in the actual value list and use the latter for append 

But I don't really know. I'm fine with the current implementation and 
it's easy to avoid such configuration issues anyway.


More information about the Fontconfig mailing list