Pages are not visible

[Daniele Giampà]

Hello community!

I have created a large work with InDesign, enriched with animations, and exported it as an EPUB3:
https://www.edgedpub.com/sample_work_4.php

I have edited the work on Sigil, and luckily, all the animations work fine.
However, I edited two pages, and they don't appear in the EPUB3 document.
These are the pages with the credits and the title page: credits.xhtml and titlepage.xhtml.

1) These two pages can't be seen in the EPUB3. When you open the document, you see the cover, and then you jump to the title.

2) EPUB-Cheker reads that these two files are not in the manifest and are not spine items. But I inserted them in the manifest and the spine.

3) Because of these two files, the entire TOC is shifted by 2 pages. For example, if you click on Title, which is on page 4, you go to Introduction, which is on page 6.

4) There are a few errors related to the fonts, but I think they are irrelevant.

I have created two different versions of the same EPUB3 document to test whether it works either way: version 02 includes the two files, and version 03 does not.

I don't see the error. The files are in the spine and the manifest.
I would be happy if somebody could help me sort this out.

Thank you.

Daniele

[Doitsu]

Manifest:

<item id="Tale_of_Tales_credits.xhtml" href="Tale_of_Tales_credits.xhtml" media-type="application/xhtml+xml"/>
<item id="Tale_of_Tales_titlepage.xhtml" href="Tale_of_Tales_titlepage.xhtml" media-type="application/xhtml+xml"/>

Spine:

<itemref idref="Tale_of_Tales_titlepage"/>
<itemref idref="Tale_of_Tales_credits"/>

You also might want to fix the many incorrect mime types and create fallback items for non core mime types, e.g. application/x-bplist and text/xml.

[Daniele Giampà]

Originally Posted by Doitsu

Manifest:

<item id="Tale_of_Tales_credits.xhtml" href="Tale_of_Tales_credits.xhtml" media-type="application/xhtml+xml"/>
<item id="Tale_of_Tales_titlepage.xhtml" href="Tale_of_Tales_titlepage.xhtml" media-type="application/xhtml+xml"/>

Spine:

<itemref idref="Tale_of_Tales_titlepage"/>
<itemref idref="Tale_of_Tales_credits"/>

You also might want to fix the many incorrect mime types and create fallback items for non core mime types, e.g. application/x-bplist and text/xml.

Thank you for the quick reply!

In Version 02, I wrote the code strings in the same way.

Manifest

610 <item id="Tale_of_Tales_credits.xhtml" href="Tale_of_Tales_credits.xhtml" media-type="application/xhtml+xml"/>
611 <item id="Tale_of_Tales_titlepage.xhtml" href="Tale_of_Tales_titlepage.xhtml" media-type="application/xhtml+xml"/>

Spine

619 <itemref idref="Tale_of_Tales_titlepage"/>
620 <itemref idref="Tale_of_Tales_credits"/>

And they are also present in the TOC:

13 <li><a href="Tale_of_Tales_titlepage.xhtml">Title page</a></li>
14<li><a href="Tale_of_Tales_credits.xhtml">Credits</a></li>

86 <li><a href="Tale_of_Tales_titlepage.xhtml">i</a></li>
87 <li><a href="Tale_of_Tales_credits.xhtml">ii</a></li>


I don't understand why EPUB-Checker doesn't find them. (screenshot attached)

[Jellby]

"Tale_of_Tales_credits.xhtml" is not the same as "Tale_of_Tales_credits".

[KevinH]

Yes the spine uses idrefs to the files in the manifest. So the spine entries must exactly match the id specified in that manifest entry.

Next time use Sigil and its menus/tools to create the proper OPF and spine entries for you.
Then no need to hand edit the OPF.