MobileRead Forums - View Single Post

NiLuJe · 06-10-2014, 02:52 PM

@poet1: That vaguely looks like the folder structure of the K2/3/4 hack, so, err, a whole other kettle of fish

.

(And that's on a K4B, right?)

EDIT: Actually not terribly sure how the KF8 renderer deals with Code2000 there... In Mobi7 files, it's replaced by I18N.ttf by the hack, but it doesn't do anything about Code2000 in KF8 files.
As on the K5, I *suspect* (but not quite sure, since Amazon seems to handle Code2000 differently there) just adding a family supporting an exotic script in linkfonts/fonts (w/ KF8 support enabled) will do the trick, with the same layout caveats than I was speaking of here when using a custom FT.
The KF8 handling is *very* messy in the K2/3/4 font hack, so it might be tricky to delve deeper.

06-10-2014, 02:52 PM	#13
NiLuJe BLAM! 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	@poet1: That vaguely looks like the folder structure of the K2/3/4 hack, so, err, a whole other kettle of fish . (And that's on a K4B, right?) EDIT: Actually not terribly sure how the KF8 renderer deals with Code2000 there... In Mobi7 files, it's replaced by I18N.ttf by the hack, but it doesn't do anything about Code2000 in KF8 files. As on the K5, I suspect (but not quite sure, since Amazon seems to handle Code2000 differently there) just adding a family supporting an exotic script in linkfonts/fonts (w/ KF8 support enabled) will do the trick, with the same layout caveats than I was speaking of here when using a custom FT. The KF8 handling is very messy in the K2/3/4 font hack, so it might be tricky to delve deeper. Last edited by NiLuJe; 06-10-2014 at 03:29 PM.