Quote:
Originally Posted by siebert
Calibre had a debug option --kindlegen which used the kindlegen binary to build the mobi file.
Kovid removed that option a few days ago because he doesn't like me and my request to make that option selectable via the gui (though I'm obviously not the only person liking that feature), but if you are willing to use either an older or a modified version of calibre you don't need the mobiunpack step.
|
How would that be any different than feeding the epub directly to kindlegen? My reason for using calibre as an intermediate step is because calibre does a much better job of translating/flattening an ePub's CSS into a mobi that more accurately reflects the original (visibly) than kindlegen currently does. Kindlegen can then take the mobiunpack output and create the final mobi (with the approved tools). Or am I missing something?