Quote:
Originally Posted by kovidgoyal
In the EPUB2 guide there must be only one guide entry of type cover that points to the actual cover image and one entry of type titlepage that points to the actual HTML file that displays that cover. Any other setup gets forced into this form by calibre's EPUB2 input processing. The viewer (and indeed all of calibre) require this for various kinds of further processing they do.
|
Quote:
Originally Posted by kovidgoyal
cover refers to the actual IMAGE. titlepage refers to the HTML file that displays the image.
|
Hi, Kovid.
According to EPUB2 specification, the
Guide section says that:
Code:
Each reference must have an href attribute referring to an OPS Content Document included in the manifest, and which may include a fragment identifier
Now, it also defines:
Code:
OPS CONTENT DOCUMENT:
An XHTML, DTBook, or Out-Of-Line XML Island that conforms to this specification that may legally appear in an OPF Package Document spine element.
An entry pointing directly to the image file doesn't seem to be valid. Also, the cover image file is already marked in the Metadata section:
Code:
<meta name="cover" content="cover_image_file_id"/>
The specification also defines the types "cover" and "title-page":
Code:
cover: the book cover(s), jacket information, etc.
title-page: page with possibly title, author, publisher, and other metadata
The "title-page" type is very well defined, and does not refer to the cover page. Now, the "cover" type might be a little misleading, as it does not use the word 'page', but the that is implied by the other definitions (OPS Content Document).
The thing is calibre treats "title-page"/"titlepage" as equivalent to "cover". This happens not only in the Guide section, but also when adding a cover page using the Editor, Polish or Conversion.