View Single Post
Old 03-15-2015, 06:32 PM   #10
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
Not quite sure the complex font-shaping thing is theoretically handled properly at all and/or fixed by the Fonts hack on the K4, since its fontconfig (and thus KF8) handling is rather hackish and crude there, but Doitsu probably remembers that better than I .

It's handled as a rather dirty hack in the FW 5.x fonts hack (related to how the fallback font is handled), and I never could manage to make it behave properly 'on demand' for a specific family (without making it globally pass as the fallback font, which is the current workaround), which explains why embedding doesn't help on a vanilla device. Thanks for the tests on FW 5.6 though, since that was going to be my next question, as that release saw some significant changes to the font rendering stack .

Last edited by NiLuJe; 03-15-2015 at 06:39 PM.
NiLuJe is offline   Reply With Quote