Quote:
Originally Posted by compurandom
I have (had) lots of epubs that had a cover image that the calibre editor showed marked as a cover image. When the book is converted to kepub and sent to the kobo, the kobo displays it on the home screen as a cover image, but when the book is opened, it treats the first html file in the book as the cover page, which is extremely annoying if it is suppose to be text to read.
The conversion from epub to kepub should wrap the cover image in an html file, even if that file is not included as part of the text.
The kobo wants an html for the kepub cover, not an image.
At least, that's what I've been told is in the kepub specs.
And yes, a lot of gutenberg books are a mess in general.
|
I seem to remember having this discussion here in the last couple of months.
The kepub specs are clear in how it treats the first HTML in the book. And it is also clear what it considers to be the cover for use elsewhere. And that these two things are not the same. There is absolutely no reason that the book has to have that cover image displayed anywhere. It could be because the cover image is optimised as a cover and a different version is displayed at the start of the book. Or it could be the book creator didn't want to display the cover.
When sending a book to the device using the extended driver, it attempts to work out what image is the cover and mark it as such. But, if it doesn't, it isn't an error, just sub-optimal for the device. The driver makes no attempt to do anything different with the first file. This is not the best, but the driver has always worked on the principal that the source file is suitable to be sent.
If you do a conversion to kepub, the handling is different. This will usually show the cover image as a separate file and as the first file in the book. You can turn this off, but the default is to have the cover page.
And, even in an epub, the defined cover image does not have to be used on the first page or anywhere else. The epub specs include how to say what is the cover image and nothing more. The various readers and apps are all deciding what to do. Some use the image directly, some, like Kobo, render the first page.
There is a bug in the initial report because the results seen are different depending on the navigation method. But, the behaviour of the first file is a design decision on Kobo's part.