View Single Post
Old 09-27-2019, 02:39 PM   #300
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
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
Okay, back home, found my notes, which are possibly dated, so there may be some overlap with what @jackie_w just posted:

Code:
Speaking of fonts, if the UI and the ACCESS (KePub) reader mangles some styles with custom fonts, make sure the Panose stuff is sane (OS/2 > Panose).
Keep the usual Kindle line-height tweaks in mind, that might also help w/ the line-height < 1.0 issue...
c.f., https://www.mobileread.com/forums/showpost.php?p=2866441&postcount=218 for the line-height thing,
and https://www.mobileread.com/forums/showpost.php?p=3606469&postcount=2 & https://www.mobileread.com/forums/showpost.php?p=3608181&postcount=9 for the Panose tweaks.

Also, supposedly kerning has to be old-style for the ACCESS renderer to make use of it...
Keeping in mind that I generally go the extra-mile of murdering the extra space between lines, hence the line-height mentions .

(I'm happily using a patched Bookerly this way).

Last edited by NiLuJe; 09-27-2019 at 02:41 PM.
NiLuJe is offline   Reply With Quote