Correcting the above bug may introduce this issue:
https://bugs.freedesktop.org/show_bug.cgi?id=60748
that has been fixed by using target="pattern" instead of target="font".
For example, the 10-antialias.conf file at the moment is:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<!-- Use the Antialiasing -->
<match target="font">
<edit name="antialias" mode="assign"><bool>true</bool></edit>
</match>
</fontconfig>
it should become:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<!-- Use the Antialiasing -->
<match target="pattern">
<edit name="antialias" mode="append">
<bool>true</bool>
</edit>
</match>
</fontconfig>
** Bug watch added: freedesktop.org Bugzilla #60748
https://bugs.freedesktop.org/show_bug.cgi?id=60748
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192175
Title:
Use of mode="assign" in default configuration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1192175/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
