View Single Post
Old 11-21-2019, 01:18 PM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
You can force fontconfig's searchpath via env vars to work around the config mismatches somewhat, without having to do anything crazier.

IIRC, FONTCONFIG_FILE points to the "master" fonts.conf (i.e., what's usually /etc/fonts/fonts.conf). This can point to a bogus path if you just need to discard everything (which was my own use-case, but that was a pretty edge-casey one ;p).

There may be finer-grained approaches, check fontconfig's docs .

Last edited by NiLuJe; 11-21-2019 at 01:20 PM.
NiLuJe is offline   Reply With Quote