MobileRead Forums - View Single Post

NiLuJe · 06-09-2014, 12:58 PM

My bad, I wasn't precise enough. The *layout* engine doesn't do complex layout

, even though it theoretically could in the case of the one used for KF8 files (FT+FC+Pango+Cairo).

EDIT: That's not entirely accurate, see Doitsu's original post, and my adventures below.
TL;DR: On a vanilla Kindle, Code2000 does complex layouts, but not Publisher Fonts.
On a hacked Kindle, it gets complicated, but you might be able to get away with complex layouts with a custom font.

So, yeah, it should mostly behave like a K3 on FW 3.4, with a wider unicode coverage, and possibly slightly less/different issues

.

Fontconfig settings aren't usually terribly readable to begin with, but it's especially messy on the Kindle, so don't necessarily expect that what you see is what you'll actually get

.

06-09-2014, 12:58 PM	#4
NiLuJe BLAM! Posts: 13,480 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	My bad, I wasn't precise enough. The layout engine doesn't do complex layout , even though it theoretically could in the case of the one used for KF8 files (FT+FC+Pango+Cairo). EDIT: That's not entirely accurate, see Doitsu's original post, and my adventures below. TL;DR: On a vanilla Kindle, Code2000 does complex layouts, but not Publisher Fonts. On a hacked Kindle, it gets complicated, but you might be able to get away with complex layouts with a custom font. So, yeah, it should mostly behave like a K3 on FW 3.4, with a wider unicode coverage, and possibly slightly less/different issues . Fontconfig settings aren't usually terribly readable to begin with, but it's especially messy on the Kindle, so don't necessarily expect that what you see is what you'll actually get . Last edited by NiLuJe; 06-09-2014 at 10:15 PM.