Quote:
Originally Posted by NiLuJe
@NullNix: They're surprisingly sprightly at tracking upstream FreeType, despite the god-awful state of the rest of the rootfs  .
It's also unfortunately heavily patched, more and more as time passes, so, who knows...
Also, interesting tidbit: I'd have to re-double check, but, for instance, I'm pretty sure the new Bookerly is completely fine in KOReader when rendered... *actually* unhinted. Okay, now I see what you mean, if they kept the autohinter on for the new Bookerly, that was a dumb rookie mistake (but mildly understandable if you're familiar with how tricky getting FT to actually do what you want can be ;p). |
Honestly, the autohinter (especially not the new one) isn't supposed to make things worse: if it's turning a nice-looking unhinted font into a baseline-wobbly thing like the new Bookerly, that's still a bug
you can't expect users to go around fiddling the autohinter on and off for specific fonts! (Assuming they even can: Amazon could do it in this case, but nobody else could.)