View Single Post
Old 01-28-2020, 06:16 PM   #93
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
@rtiangha: Used to be Qt 4.x, is now 5.2. They kept the filenames as-is to make updates less painful (since it's basically a tarball with no scripting capabilities, so migrating folders & filenames was not easily doable post-install).

FWIW, wonky stem heights is typical of FT autohinting going awry, so, it all tracks . You'd get "fuzzier" rendering if truly unhinted, but with "perfect" (as in, honoring the font's design) shapes. The higher the DPI, the sharper the rendering. Plus, eInk has a tendency to make that fuzziness much less noticeable than on LCD to begin with.

Last edited by NiLuJe; 01-28-2020 at 06:19 PM.
NiLuJe is offline   Reply With Quote