Having multiple values in <test> isn't supported and may not

[greatquux]

be supported
-
a new warning that was added to fontconfig in May (http://cgit.freedesktop.org/fontconfig/ ... 18d48f4652) and is causing a lot of warnings when starting programs on Ubuntu 12.10 (which incorporates this version of fontconfig): https://bugs.launchpad.net/ubuntu/+sour ... ug/1034928

It's not just infinality that uses these and the Ubuntu developers are considering reverting the warning anyway, I just figured you might want to be aware of this.

[infinality]

Thanks... Yes I'm aware of the issue and working on adjusting the rules to do things the "right" (and really inconvenient) way. I may be able to get the fontconfig people to adjust the warning a bit.... More later.

[pablox]

I got the same issue too, but on Arch Linux that recently updated fontconfig to 2.10. I'm also getting a lot of errors.
There's some way to workaround this meanwhile we got a patch?

[bwat47]

I got the same issue too, but on Arch Linux that recently updated fontconfig to 2.10. I'm also getting a lot of errors.
There's some way to workaround this meanwhile we got a patch?

The only workaround would probably be to not use fontconfig-infinality, since those warnings are due to the way infinality's fontconfig is setup.

The warnings are harmless anyway, I wouldn't worry.

[bohoomil]

The only workaround would probably be to not use fontconfig-infinality, since those warnings are due to the way infinality's fontconfig is setup.

Not really: you have to modify Infinality fontconfig rules so that one test set applies to each font separately, more or less like this:

Code: Select all

cat 60-group-tt-fonts.conf

<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
. . .
<match target="font">
  <test name="force_autohint">
   <bool>false</bool>
  </test>
  <test name="family">
   <string>Aller Light</string>
  </test>
  <edit name="font_type" mode="assign">
   <string>TT Instructed Font</string>
 </edit>
</match>
. . .
</fontconfig>


[infinality]

A tentative fix for this is in the git repo now... may be subject to change though, so wait for the next release if you are a packager.

https://github.com/Infinality/fontconfig-infinality