Quote:
Originally Posted by Notjohn
In my experience, that's where the dread double-cover problem arises, when I pointed to the included cover. (Very few examples to go by, to be sure. I think I did this only once, and that was a trial to see if I could force the downloaded book to open at the cover if I gave it the "semantic" of text. I ripped out both cover and semantic the same day and haven't gone back to that well since.)
|
NO. That is 100% wrong, NJ.
All you have to do is remove the cover.html. Leave the cover.jpg (or whatever) image in the Files folder. Point to it,
and assign the COVER semantics. Build MOBI.
Voila. Do that, and you will NEVER have a double-cover.
We haven't had one in, geeze, I don't know, four years now? Which would be somewhere in the 2,000 book figure? I'm pretty sure, if it were going to happen, in that scenario, it already would have.
@Doits:
Yes. You are correct. Dead on. If you forget, and leave the cover.html or XHTML file in, it's a crapshoot. Sometimes, it suppresses the "extra" and sometimes, it doesn't. The safest method is, remove the cover.html file, and follow the rest of the destructions. :-)
Hitch