Quote:
Originally Posted by DiapDealer
Not sure. That might be the reference, but that spine entry itself won't produce an epubcheck error like that. An empty epub3 created by Sigil contains that same spine entry and does not trigger that particular EpubCheck error. It might be something else. What does the line number in the opf error correspond to?
|
The line 127 in content.opf is
Code:
<item id="navid" href="nav.xhtml" media-type="application/xhtml+xml" properties="nav"/>
This is the final entry in the manifest just before the </manifest> tag.
Edit: I've been trying a few things and if I change the last line in the spine from
<itemref idref="navid" linear="no"/> to
<itemref idref="navid" linear="yes"/>
and then run epubcheck again, there is the good news 'No problems found!'
This is repeatable when linear is no, there's the problem, yes gets rid of it. I've gone backwards and forwards several times.
Further: IIRC KevinH said somewhere that an empty entry is taken as 'yes' by default so I tried
<itemref idref="navid"/>
and again 'No problems found!'