View Single Post
Old 03-03-2014, 03:15 AM   #3
AnemicOak
Bookaholic
AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.
 
AnemicOak's Avatar
 
Posts: 14,391
Karma: 54969924
Join Date: Oct 2007
Location: Minnesota
Device: iPad Mini 4, AuraHD, iPhone XR +
Quote:
Originally Posted by Nabodita View Post
I then took the same epub, ran it through KindleGen and created a mobi (output generated without errors) which also had the font embedded. This file, however, did not render correctly on the Kindle.
Mobi/AZW doesn't support embedded fonts, but KF8/AZW3 does. If you're using the latest version of KindleGen or Kindle Previewer for creation then it should be taking your ePub and creating a file that contains both a Mobi and KF8 along with the ePub source. Perhaps the Fire is reading the Mobi from this file instead of the KF8? Maybe use KindleUnpack to separate out the parts and try just the KF8/AZW3?


Disclaimer: I haven't been paying tons of attention to this subject lately so I may be slightly off on some details, but I'm sure someone will correct me.
AnemicOak is offline   Reply With Quote