Quote:
Originally Posted by compurandom
While that's true, it's harder to check. The first thing in the spine is probably a jpg that is marked as the cover, so the first html/xhtml in the spine is chapter 1. Or something like that, not that I claim to understand spine construction.
|
Are you are talking about the problem discussed
in this thread? If so, the first entry in the spine is a HTML/XHTML file and the contents of that file go over more than one page. That's the real problem. That first file is treated differently by the kepub renderer and you really just want to limit it to one page. And, if you have a cover image, then just displaying that in the page makes sense.
Also, I don't think you can have an image file in the spine, but I'm sure someone will correct me if I am wrong.
Quote:
Searching for orphaned images works but gets a lot of false positives where the book just has extra images in it, but the title page is OK. Also, I'm not sure that polishing the book fixes the orphaned image problem, so they still show up in the search after being fixed.
|
Orphaned images are perfectly valid in an epub. And, it is legitimate to mark an image as the cover image and use something else on the first page of the book. It is more just a custom that the first HTML/XHTML file and hence the first page contains the cover image. But, what everyone forgets is that a kepub is
not an epub. Kobo sets the specs for kepubs, and while they are largely the epub specs, there are differences. One of them is that
Cover images must be contained in their own XHTML files. And that means you get the problems described in the thread above.
Quote:
I'm sure that the problem books the title page is an image instead of an html file, I looked at the book in the calibre editor, it even marks it as an error but won't fix it automatically.
|
I don't think I have seen that error, but I am careful about the covers in my books. I'd probably need to see the book that has the problem to work it out.
Quote:
I don't think there is a suitable option...this is a feature request.
|
That's not how the post read. And unfortunately, it's not likely to be done as no-one is making changes to the plugin.