View Single Post
Old 10-19-2021, 10:31 AM   #9
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,109
Karma: 92190133
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by emdashery View Post
Sorry for asking in the wrong place! Should I move it over?
You will probably get more relevant responses from members experienced in publishing on Amazon if you have the thread moved. If you want that to happen you can request a moderator to do it by reporting (!) the first post in the thread.

Quote:
Originally Posted by emdashery View Post
Sooo JHowell...are you suggesting I give up on embedding fonts altogether?
That is for you to decide. I am just trying to inform you regarding the potential pitfalls of embedding fonts.

Quote:
Originally Posted by emdashery View Post
Here is an example page from the book for reference:
...
OK now this is weird...I just sideloaded the latest mobi file onto my decade-old Kindle 4...and the embedded fonts are working (with some very jacked-up line-heights)??? But not working on the newer Kindle 5? Color me confused!
The Kindle Previewer will show you how the book will appear in KFX format (Enhanced Typesetting). That will be how most users of newer Kindle apps and devices should see it.

Kindle 4th and 5th generation devices both use KF8 format and support embedded fonts. The difference in your results is most likely due to one device being configured to show the Publisher's Font and the other to show one of Amazon's fonts. Check in the Aa menu.
jhowell is offline   Reply With Quote