True enough. I'm just saying that it may be unreliable to the point that it's not worth the effort to add support for that. Frankly, like you, I wonder why DropBook requires images to be in a separate directory to begin with. It's an unnecessary complication.
Originally, the directory conflict bugged me because I thought importing a *.pml file would collect the images into a *.pmlz file in much the same way that importing a *.html file does. Since that's not the case, and I have to bring in either a PDB or a PMLZ (neither of which is useful to DropBook anyways), I may as well create them to Calibre's standard.
I looked into adding the ability to import the Cover Page from a PDB file, but I don't see an easy way to do it since you have to partially decode the file to get the "cover.png" image. At this point, I've created a preprocessing plugin (on add to database) for any eReader PDB files that returns a *.pmlz file. This way I have PML text properly cleaned. I then just tell it to re-read the meta-data and all of the details show up. With the added code, the cover page is pulled in as well (using calibre-debug).
Man, Calibre has become 10 times more useful since adding eReader support. Thanks for all the work you put into this!
- Jim
|