View Single Post
Old 10-19-2014, 09:18 AM   #260
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
@mandy314: Keep in mind that I was talking about my own stuff. I don't remember how bulletproof the fontconfig KUAL extension is, so YMMV if you're using that. The appropriate FC_DEBUG value & fc-match help figure these things out on fontconfig's side, but that leaves the mysteries of how the KF8 renderer actually honors those...

As for your examples, the mixed Publisher fonts thing can be handled safely with the fonts hack. Usually, the fallback is serif, and overriding that is safe. As for sans, the fallback override usually takes care of it.

Last edited by NiLuJe; 10-19-2014 at 01:54 PM.
NiLuJe is offline   Reply With Quote