View Single Post
Old 08-13-2022, 12:11 PM   #258
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: 47,399
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by jhowell View Post
I tested this just now by emailing an EPUB that does not contain a character encoding in its xhtml files. It was accepted by Amazon and it displays on my Kindle with garbled characters as expected. So it not the case that missing character encoding now automatically leads to rejection.
I was playing with emailing an ePub to a Kindle and found that the ePub which lacked the correct minimal directory structure was rejected. The ePub had all it's files in the root of the .zip container including the container.xml which must be located in the META-INF directory. It also had the mimetype file compressed which is, again, contrary to the ePub specification. This resulted from the author uncompressing the original ePub to do some image compression and then using a zip utility to add all the files into a new file.

For what it's worth, epubcheck was extremely unhappy with the ePub as I received it from the author.
DNSB is offline   Reply With Quote