Thread: Help: missing embedded fonts after ePub3 transfer to Kindle
View Single Post
Old 03-03-2023, 05:53 PM   #28
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,116
Karma: 92190133
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by Nightjar View Post
Ok, after quite a long time I still haven't found a solution, so I have made a sample template based on the Epub3 standard template we created from scratch. It is 100% valid with both EPUBCheck 5.0.0 and Ace by DAISY. CSS3 is also valid, with the exception of a minor sets of hyphens warnings.
...
Any help would be greatly appreciated. I enclose my sample ePub3 file.
I downloaded your EPUB and was able to confirm that sending it to a Kindle device as a personal document using send-to-kindle results in significantly different rendering when compared with sideloading a Master MOBI file produced from it using the Kindle Previewer.

I copied the AZW3/KF8 send-to-kindle file from my Kindle and compared it to the Master MOBI and the original EPUB using calibre's editor. The CSS in the Master MOBI file produced using the Kindle Previewer is almost identical to the original EPUB. However there are several changes to the CSS in the send-to-kindle file. Most of the call outs to the embedded fonts have been stripped.

Amazon does not adhere to industry standards. They only provide vague "guidelines" on how source files should be formatted for Kindle e-books.

Amazon's publishing process is picky about what it allows for embedded publisher fonts. And unfortunately the rules are undocumented. Experienced book formatters have learned what to use and what to avoid by trial and error. The best advice I have seen is to keep things as simple as possible.

The current version of the Kindle Previewer performs only a subset of the processing that is done when a book is published on Amazon. And it used to be that personal documents converted by Amazon using send-to-kindle were also minimally processed.

That changed recently. It appears that with the introduction of the Kindle Scribe Amazon has revamped the send-to-kindle pipeline to be much closer to what published books go through. That allows the Scribe to use Amazon's newer KFX format for personal documents. (It is necessary because the Scribe's annotation features all rely on KFX.) Unfortunately for you it means that more restrictions now apply.
jhowell is online now   Reply With Quote