[Bug 1192175] Re: Use of mode="assign" in default configuration
BubuXP
1192175 at bugs.launchpad.net
Wed Jun 19 08:31:20 UTC 2013
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
Foundations Bugs, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1192175
Title:
Use of mode="assign" in default configuration
Status in “fontconfig” package in Ubuntu:
New
Bug description:
The additional .conf files that Ubuntu's patches create in conf.avail/ use mode="assign" to set preferences.
But in this upstream bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=17722
it's said that the default configurations should use mode="append", and the use of "assign" should be limited to user configuration. The original fontconfig .conf files in Ubuntu already use "append", as correction of this bug.
Ubuntu versions that present this bug: all.
fontconfig versions that present this bug: all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1192175/+subscriptions
More information about the foundations-bugs
mailing list