The issue seems to have been fixed by that commit
https://cgit.freedesktop.org/fontconfig/commit/?id=4699406a
Closing since it's resolved with 1.13.1 in the current Ubuntu serie,
maybe it should be SRU to 18.10 but that's a non LTS serie and the issue
doesn't seem to get much user traction...
** Changed in: fontconfig (Ubuntu)
Importance: Undecided => Low
** Changed in: fontconfig (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1814342
Title:
fc-match does not return the correct font
Status in fontconfig package in Ubuntu:
Fix Released
Bug description:
On Ubuntu 18.10 the command `fc-match monospace:bold` returns
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
instead of
DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold"
This works correctly on Ubuntu 18.04.1 which is using fontconfig 2.12.6,
whereas 18.10 uses 2.13.0.
I compiled 2.13.1 from source and just installed libfontconfig.so.1.12.0.
This solves the problem.
While it does not sound much, this bug also causes Java 8 AWT/Swing
font rendering to be uglier than it has to be. Instead of "DejaVu Sans
Mono Bold" and emboldened version of "DejaVu Sans Mono" is used which
has a different size, which goes counter to the notion of a
"monospace" font.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1814342/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp