From: Spencer Phippen <spencer.phippen@gmail.com>
Date: Wed, 23 Nov 2016 18:17:59 +0000 (+0100)
Subject: Fixed 'missing glyph doesn't use fontconfig config substitutions' bug
X-Git-Url: https://git.xinqibao.xyz/st.git/commitdiff_plain/fa9a4599720703932d1c4f16b9aeee1f91f96263?hp=fa9a4599720703932d1c4f16b9aeee1f91f96263

Fixed 'missing glyph doesn't use fontconfig config substitutions' bug

XftFontMatch does display-specific font configuration (commit 528241a).
Nice. Unfortunately, when we switched from FcFontMatch, we also stopped
storing the post-Fc{Config,Default}Substitute FcPattern for future
lookups. The result is that if a glyph isn't found in the primary font,
secondary font lookups use the original FcPattern, not the configured
one. If you have custom fontconfig rules (like me), this can be
disappointing.

I basically just copied the guts out of XftFontMatch[1] and saved
the intermediate configured FcPattern. Could be related to the bug that
inspired commit 4242027.

[1]: https://cgit.freedesktop.org/xorg/lib/libXft/tree/src/xftfont.c
---