View Single Post
Old 11-12-2010, 05:28 PM   #1087
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
@Dusty Star: Yep, that's it, you can remove the attachment if you're concerned about what might lurk in those logs .

EDIT: Okay, found out both why it suddenly works, and why the browser is broken.

I seem to have slightly messed up the FT override codepath, and that ends up always using the autohint FT override when it shouldn't use *any* override.

Just to make sure: You didn't create the blank 'autohint' and/or 'bci' files, did you? (Most likely not, sounds like a bug on my end, but let's be sure about this ^^).

And then, indeed, when using an FT override (at least autohint, haven't tried anything else yet), that breaks font rendering in the K3 browser.

So, first things first, fix my broken override checks.

And then try to see if I can get it to work in the browser (I wouldn't hold my breath on that one, but, hey, who knows?! ).

Last edited by NiLuJe; 11-12-2010 at 05:41 PM.
NiLuJe is offline   Reply With Quote