View Single Post
Old 11-27-2022, 10:41 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,355
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
I thought this topic had been beaten to death with multiple threads about the topic. The most likely problem is that your epubs are not marked as using UTF-8. You can use calibre's Modify Epub plugin to correct this before sending the epubs to Amazon (turn off all the options except Encode HTML in UTF-8). BTW, the epub standard requires an epub to use either UTF-8 or UTF-16 encoding though I've only seen 2 epubs that used UTF-16.

One other item is that calibre's ebook-viewer is chromium based and like most web browsers tends to hide many errors. It is not a good test bed for how an epub will display on an eInk reader or most apps.

Last edited by DNSB; 11-27-2022 at 10:44 PM.
DNSB is offline   Reply With Quote