Quote:
Originally Posted by davidfor
Also, there is a difference between the converted kepubs and the kepubs generated by the extended driver. The conversion uses the full conversion pipeline. That means that other change can happen. The driver directly changes the code to add the spans without touching things like the toc or styles. There shouldn't be any difference when reading, but the contents will be different.
|
I noticed that. I'm running a batch conversion now using the normal method and some epubs have failed in converting this way as opposed to using the extended driver. Also, the normal way of converting through Calibre doesn't allow for the creation of black and white covers.
Hmm, maybe I don't know how to use Calibre properly (and sorry for going slightly off topic!), but is there a way to call on the extended driver instead then to do the epub conversions in advance (ideally in parallel to take advantage of my multi-core machine) and save those kepubs alongside the regular epubs in Calibre so that it doesn't do those conversions one-at-a-time when sending to the device? Or conversely, have the extended driver save the kepub into its associated Calibre entry rather than deleting it after transfer? I know there's a setting to save them all to one directory, but then I'd have to click and drag them to their corresponding Calibre entries to store them then, wouldn't I? That'd take a while for anyone whose collections are in the high hundreds or thousands.
Really, all I want is to have to save the processing step by doing that part ahead of time so I can just skip ahead to the transferring step whenever I have to recover from a factory reset.