MobileRead Forums - View Single Post

NiLuJe · 07-25-2014, 01:30 PM

@roger64: Yeah, cr3.ini is NOT shipped with KOReader, it's built at runtime the first time a CRe-handled document is opened.

But your detailed recap of what you did was perfect, and answered my question [you indeed got a 'new' cr3.ini, whith the changes I linked to in the KOReader thread]

.

So, without further ado: it's probably because you're used to the previous font rendering settings, which discarded font hinting completely. I tweaked those (because they were fairly insane), and we now default to using FreeType's autohinter, which tends to be very generous when bolding fonts (much like Apple's rendering, which roughly does the same thing: discard the font hinting, and do it heuristically instead).

So, you have two choices if this bothers you this much:

• Go back to the previous settings: set font.hinting.mode to 0 in data/cr3.ini
• Enable bytecode hinting (à la Windows, which is what the Kindle (and possibly Kobo) stock readers do: set font.hinting.mode to 1 in data/cr3.ini

(FYI: KOReader's UI probably defaults to using bytecode hinting, too, IIRC, but every other document-handler doesn't handle hinting (which is fairly stupid, if you ask me... It's much less annoying because those devices are relatively high DPI, but, still...)

07-25-2014, 01:30 PM	#15
NiLuJe BLAM! 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	@roger64: Yeah, cr3.ini is NOT shipped with KOReader, it's built at runtime the first time a CRe-handled document is opened. But your detailed recap of what you did was perfect, and answered my question [you indeed got a 'new' cr3.ini, whith the changes I linked to in the KOReader thread] . So, without further ado: it's probably because you're used to the previous font rendering settings, which discarded font hinting completely. I tweaked those (because they were fairly insane), and we now default to using FreeType's autohinter, which tends to be very generous when bolding fonts (much like Apple's rendering, which roughly does the same thing: discard the font hinting, and do it heuristically instead). So, you have two choices if this bothers you this much: • Go back to the previous settings: set font.hinting.mode to 0 in data/cr3.ini • Enable bytecode hinting (à la Windows, which is what the Kindle (and possibly Kobo) stock readers do: set font.hinting.mode to 1 in data/cr3.ini (FYI: KOReader's UI probably defaults to using bytecode hinting, too, IIRC, but every other document-handler doesn't handle hinting (which is fairly stupid, if you ask me... It's much less annoying because those devices are relatively high DPI, but, still...) Last edited by NiLuJe; 07-25-2014 at 01:33 PM.