Quote:
Originally Posted by NiLuJe
@IceHand: IIRC, because this came up w/ KOReader when I looked into it, the kerning mentioned is only FreeType's very, very, very basic kerning support, which is (according both to FT's docs and my testing) fairly useless. Kerning's the job of a layout engine (w/ a FT/FC stack, usually harfbuzz, or something using harfbuzz [cairo+pango/Qt]), something that's mostly nonexistent with CRe.
TL;DR: Nope.
|
If you look at this screenshot of HackedUpReader (which as I understand is using the same crengine code as KOReader), you see that basic kerning on a KT is working okay (check for "Tochter" or "Tau" in the middle of the screen):
http://bhaak.net/kindle/hackedupreader_blindtext.png
But this is not with the builtin freetype library but the one we compiled separately for the K5 devices. The builtin is missing LOTS of features, including any kerning support (if you look closely, you'll notice that the Amazon fonts are designed to look good with no kerning, so they know about it).
I don't know if the K3 can use the same freetype library and I agree that the crengine code is not a full layout engine.
But for a alphabetic left-to-right language, it is better than the Amazon engine (which does nothing) and far from useless.