Thread: KindleUnpack (MobiUnpack): Extracts text, images and metadata from Kindle/Mobi files
View Single Post
Old 06-18-2024, 04:50 PM   #1308
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,213
Karma: 170056770
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by TK423 View Post
Beginner question here but what is the actual difference between using KindleUnpack versus simply using Calibre to convert a AZW3 file to EPUB?
For me, the main difference is that the calibre conversion messes with the css files and calibre can split a single xhtml file into multiple files where some nudnick has used multiple header tags in a single file. When the input file to Amazon was an ePub, KindleUnpack is a lot closer to the original structure.

If you are not planning on actually mucking with the ePub in an editor (Sigil, calibre ebook-editor, whatever), there is not much real difference. If you are planning on editing the ePub, KindleUnpack is the way to go.

I won't get into the philosophical differences I have with Kovid Goyal over attempting to create output files that are compliant to the ePub specs. There is quite a bit of cruft in the ePub specs but many publishers will insist that your ePub pass epubcheck before it will be accepted for publishing.
DNSB is offline   Reply With Quote