Quote:
Originally Posted by slowsmile
Seems to be saying that a cover image should be added to the book content but this is not very clear.
|
It's very clear, but only if you stop conflating PAGE with IMAGE FILE.
An image
FILE (PNG, JPG, GIF, etc) for use as a book cover should be included (manifested) in the epub.
A cover
PAGE (xhtml) should not.
The conversion process knows which image to use for the cover by checking the META 'name="cover" ' entry for the manifest id of the image in the 'content="<insert manifest id here>" ' attribute/value pair.
Code:
<meta content="cover.jpg" name="cover" />
The above identifies the image with the opf manifest id of "cover.jpg" as the image to be used for the book's cover. In this case, the manifest id is also the file name, but that doesn't have to be the case. It could be any valid id value. For instance:
Code:
<meta content="cover_img" name="cover" />
would point to an image entry in the manifest list with the id "cover_img" that should be used as the book's cover. Something like:
Code:
<item id="cover_img" href="Images/img0001.png" media-type="image/png"/>
EDIT: or in the case of EPUB3, the manifest property "cover-image" would be added to the proper image's manifest "item" entry.
Code:
<item id="cover_img" href="Images/img0001.png" media-type="image/png" properties="cover-image" />