Quote:
Originally Posted by rtiangha
I noticed the same problem on my Glo HD at the smallest font sizes. It's less noticeable at higher font sizes. I normally read at one size higher than when the problem starts to become more visible which is why I've never noticed.
It's interesting to read the documentation on QT embedded and fonts (I believe that's what Kobo uses; not sure about Kindle). Since it uses Freetype, if a font has no hinting information, default behaviour is that it'll default to using the Freetype autohinter. The only way to disable that (I believe) is for the renderer to turn it explicitly off with FT_LOAD_NO_HINTING. I don't know if Kobos or Kindles do that or not.
I don't know if I'm interpreting this correctly, but does that mean it's possible that all of these fonts are getting autohinted despite some of us explicitly removing hinting information from our sideloaded fonts? Would it be better to rely on a font's default hints or things like ttfautohint to update fonts with crappy (or old) hinting information after all in order to avoid Freetype's autohinter? |
Here is the link to ttfautohint. It's great for adding hinting to a font.
https://www.freetype.org/ttfautohint/index.html
And here is the link to the source on Github so it can be built for Linux.
https://github.com/source-foundry/ttfautohint-build