Quote:
Originally Posted by DNSB
If available, KindleUnpack will extract the epub source file stored inside the azw3 container. Calibre has become much better but it still likes modifying the CSS, removing inline styles, flattening the CSS, etc. There are relatively small differences but enough to sway me to use KindleUnpack. As a test, I just unpacked one azw3 and also converted it. The converted one had 27 added css entries where inline styles were converted to stylesheet entries. 24 of them were paragraph indents ranging from 12 to 23 pixels plus the occasional italic or bold. In the unpacked one, I simply looked for the style= with a bit of regex while the calibre converted one took 4 passes to get the same result.
|
How do you get KindleUnpack to extract the ePub source? All I've seen is KindleUnpack shifting the KF8 code to ePub. In most cases, it works well because the source was an ePub. But in some cases, not well at all because the KF8 is a real mess.
Quote:
|
Much the same. When I edit the book, I tend to leave unused spans as <span> and then strip the empty spans using ModifyEpub. Basically, ModifyEpub does everything that Polish does other than adding soft hyphens and adds more functions that I find useful such as removing inline javascript and files.
|
I use Modify ePub because It does more then Polish and I use it on every ePub I edit.
Quote:
|
I seldom use the kepub renderer on my Kobo since being a bit of a typography nerd, I prefer the font handling in RMSDK. I do make exceptions for ebooks that require kepub such epub3 FLO books and the occasional book where there are enough high resolution images to make the image zoom worth having (I think I might need one hand to count those books).
|
Would that be "where the are
not enough high resolution images"?