Quote:
Originally Posted by jhowell
I went a step further and looked at the raw HTML in the KF8 version of the book and I discovered that I was wrong about it not having dual covers. The KF8 format has a second cover image as the first page in the book. This is the same as I saw in the Look Inside and the free sample.
I had only looked at the cover in KFX format for this book and there is only one in that case. So it appears that for some reason the extra cover detection and removal process for this book was effective for KFX, but not for KF8.
I sideloaded the KF8 format to my Kindle and discovered that it opens at the second cover, which is location 2 in the book, not the real cover. This is different from the KFX format which has only a real cover and opens there the first time.
|
I wonder if this is new? We have a client that suddenly has the dreaded double-cover (as I mentioned above) in the LITB, but not in the book itself, by all appearances/downloads.
If this were new, it
might explain why it would suddenly show up in the LITB, when it's not in the book itself. The old dreaded Double Cover used to exist because the MOBI was built with an image (think of a frontispiece) already in the source file, AND the cover was thence added. It was a mistake.
Now we're seeing a double cover--only in the LITB--with a commercially-built book (ours). I don't think I've seen this since...hell, 2012 or so?
So, jhowell, you think that for some reason, the double-detection failed, for KF8?
(FYI, we've discovered that not using the semantic for the cover, versus using it, does make a difference in the build, but we're still investigating.)
Hitch