Oddity in e²->e³ conversion

[DNSB]

I converted an ePub2 to ePub3 using the e²->e³ plugin. When I opened the converted ePub, epubcheck complained about a missing title and an issue with an missing li in the nav document. epubveri, OTOH, complained about a missing </spine> element.

OEBPS/Text/Section0001.xhtml	6	158	Col: 10: ERROR(RSC-005): Error while parsing file: Element "title" must not be empty.
OEBPS/nav.xhtml	23	631	Col: 12: ERROR(RSC-005): Error while parsing file: element "ol" incomplete; missing required element "li"

OEBPS/content.opf	17	998	FATAL RSC-016: OPF is not well-formed XML: unclosed <spine> at line 15; expected </spine> but found </package>

The weird item is that when I look at the content.opf file in Sigil, the last lines are:

  </manifest>
  <spine toc="ncx">
    <itemref idref="Section0001.xhtml"/>
  </spine>
</package>

and the </spine> element is present.

If I simply save the document, open the ePub in 7-Zip and open content.opf in Notepad++ from there.

</manifest>
<spine toc="ncx">
<itemref idref="Section0001.xhtml" />
</package>

OTOH, if I place the cursor in the last line below </package> and hit a backspace, epubveri is now happy and the </spine> element is present in the saved file.

[DiapDealer]

Are you talking about Kevin's Epub3-itizer plugin or something else?

[DNSB]

Originally Posted by DiapDealer

Are you talking about Kevin's Epub3-itizer plugin or something else?

That's the plugin I was using.

[KevinH]

Does your epub2 actually pass epubcheck before trying to convert it? Specifically if the content opf is broken, the plugin will stand no chance of working.

So before running ePub3-itizer, running epubcheck and fixing errors is highly recommended. Please also make sure you are using the very latest version of ePub3-itizer.

[KevinH]

After eyeballing the code, there is one code path that could result in a possible missing spine close tag. So would you please copy and paste just the epub2 original content.opf here so I can try to see how that code path actually gets triggered and find the bug if one exists.

That is assuming that epubcheck is okay with the original epub2 opf. Otherwize the plugin is bound to have issues with a broken opf.

[philja]

I've converted an epub2 to epub3 a few days ago using the epub3itizer plugin. The epub2 was in good shape and passed F7 and epubcheck ok.
The only problems noted by epubcheck after the conversion were expected ones concerning inline width=x% for images, which epub3 wants in the CSS stylesheet.
There was nothing about a missing </spine> tag.

[KevinH]

Yes, not a common bug if a bug at all but I would like to figure out how triggered to prevent any future issue.

Thanks!