Quote:
Originally Posted by DNSB
At a wild eyed guess, that is an artifact of using calibre's cover generation while the other filenames are generated internal to the KFXInput plugin.
|
Quote:
Originally Posted by jhowell
Yes, that is it. By default calibre's conversion will rename the cover page to titlepage.xhtml and the cover image to cover.jpeg. You can keep the originals as produced by the KFX Input plugin by selecting "Use cover from source file" in the Metadata tab of the conversion dialog.
Added: We have already had this conversation: Internal Filenames AZW/KFX --> Epub |
Quote:
Originally Posted by Jaws
The previous conversation didn't make clear to me whether the origin point for this particular filenaming issue was Calibre, or farther up the chain. Renaming in Calibre would be less likely to cause later problems on reconversion if the origin was Calibre than if, say, that was a hardcoded-in-the-KFX-spec filename/extension, which is possible since every book has one and Amazon has been known to take advantage of such things.
|
Perhaps re-reading the message immediately above your response might help. Heck, @jhowell even gave you the workaround to not have calibre replace the cover image.
Oddly the same advice was given in @jhowell's response to your post in the thread they linked to:
Quote:
Originally Posted by jhowell
Whenever calibre is instructed to replace the cover of a book, either during a conversion or polish operation, it will change the name of the HTML file containing the cover to titlepage.xhtml. That name is hardcoded into calibre. I do not know why that name was chosen but it has long been the case. There is a recent thread somewhat related to this: giude item "cover" displayed as "Title page"
Avoid replacing the original cover in the book to prevent the change of the file name during conversion. In the metadata tab of the conversion options select "Use cover from source file". |
Are you hoping to get a different answer by asking the same question multiple times?