Quote:
Originally Posted by davidfor
Are you saying that whatever is used on the first page then affects all the rest of the pages when reading?
|
Exactly so, yes. A bare image item as the first element in <spine> will do this reliably.
Quote:
Originally Posted by davidfor
In any case, I'll have to do some experiments to see what is happening here.
|
Here's a reliable test. Check out the following OPF fragments as an example:
Code:
<manifest>
<item href="cover.jpg" id="coverimg" media-type="image/jpeg"/>
<item href="cover_r1.xml" id="cover" media-type="application/xhtml+xml"/>
<item href="toc_r1.html" id="toc" media-type="application/xhtml+xml"/>
...more content here...
</manifest>
<spine toc="ncx">
<itemref idref="coverimg" linear="no"/>
<itemref idref="cover" linear="no"/>
<itemref idref="toc"/>
...more content here...
</spine>
The bolded line is the key. If it's present, and the image is smaller than the screen dimensions, the rest of the book gets rendered
in that area, starting at the top left corner of the device, with the rest of the screen remaining blank. Delete that line, and the book renders across the entire screen. Works every time, and the LINEAR attribute doesn't affect it either way. The key is that the bolded ITEMREF refers to an image.