View Single Post
Old 06-20-2014, 03:59 PM   #8
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
Oookay. Weird twist: The Code2000 override that I recently added to the Fonts Hacks worksaround this bug (the font used to override Code200 is used instead of Helvetica).

Huh.

While new & relatively untested, it should be mostly safe, but it's obviously only applicable if you don't actually rely on a wide unicode coverage and/or complex script layout.

That said, I'm looking into 'fixing' this in a less intrusive (& relatively safe) way, now that I managed to reproduce a testcase (thanks, ShamanNS ;p).

EDIT: Nope, didn't manage to do it in a better way. So, yep, the Code2000 override does the trick without touching the UI (and thus *should* be mostly safe).

Last edited by NiLuJe; 06-20-2014 at 06:25 PM.
NiLuJe is offline   Reply With Quote