Public bug reported:
Binary package hint: fontconfig-config
If I enable the yes-bitmaps rule globally (i.e. fix the
/etc/fonts/conf.d/70-yes-bitmaps.conf link) then it's not possible to
disable any bitmap font with <rejectfont> elements in the user local
~/.fonts.conf.
It looks like this is due to the fact that <acceptfont> elements (which
is used by /etc/fonts/conf.avail/70-yes-bitmaps.conf) always override
<rejectfont> (according to fonts.conf(5)), and the user specific
settings is given no priority over the system settings.
Ideally user settings should always override system settings regardless
of the priority between elements, but a short-term fix seems to be to
always avoid <acceptfont> elements in the /etc/fonts/conf.d files. In
the case of the 70-yes-bitmaps.conf file, there is no need to specify an
<acceptfont> element at all since fonts are accepted by default.
** Affects: fontconfig (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
The yes-bitmaps rule makes it impossible to disable any bitmap font on a
per-user basis
https://bugs.launchpad.net/bugs/110392
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
