[Fontconfig] Problem when <alias> is followed by more than one <family>

Raimund Steger rs at mytum.de
Tue Feb 28 01:25:34 PST 2012


Petr Gajdos wrote:
> 0. Forget. It can't work this way.

Well at the moment it's just unsupported syntax.

I understand that some of fontconfig's default configuration files used 
to have some minor glitches here which have been fixed recently.

fontconfig's implementation of <alias> parsing could probably be changed 
with some effort, but what's wrong with just using a bunch of <alias> 
elements? These aren't going to change so often anyway.


More information about the Fontconfig mailing list