View Single Post
Old 12-15-2025, 03:19 PM   #41
vermontcathy
Zealot
vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.vermontcathy ought to be getting tired of karma fortunes by now.
 
Posts: 121
Karma: 630876
Join Date: Dec 2009
Location: vermont
Device: Colorsoft, K3, K4, Oasis
Quote:
Originally Posted by jhowell View Post
That would be great but it seems unlikely to me.

Remember, this is Amazon. They allow books to be upload in a variety of formats, including DOCX. That is likely popular with self-publishers. And they allow editing of the uploaded content within their software before actually publishing it. Those features make it likely that they will just convert from their internal format to EPUB for downloading.

As a test I took a simple EPUB, converted it to Amazon's Kindle Publishing Format (KPF) using the Kindle Previewer and then back to EPUB using Kindle Create. Here are the results.

Original:


After conversion:


With CSS:



Perhaps the downloads they provide will be better than that, but I doubt it.
What difference does it make what the back-end code looks like, as long as it looks good on the kindle? When converting books to ePub in Calibre, Calibre seems to make more CSS groups than it needs to, but I don't care as long as it looks the way I want it to look on the kindle.
vermontcathy is offline   Reply With Quote