Quote:
Originally Posted by KevinH
I have never seen that issue. Would you please provide a specific example of when you have seen this or is this just theoretically more correct?
|
I discovered this issue because the tests/mo/epub2_base tree triggers it, as
https://github.com/pettarin/ePub3-it...ontent.opf#L88
references toc.xhtml, which is not in the spine. If you just add it to the "guide" <nav> in the nav.xhtml file, without adding toc.xhtml to the spine, you will trigger the RSC-011.
(And yes, toc.xhtml comes from the epub3_base from which epub2_base has been "backported". Nevertheless epub2_base is a valid EPUB2 publication.)
The issue stems from the fact that EPUB2 did not mandate that the <guide> reference item points to an item in the spine (?), while EPUB3 requires:
Quote:
|
All EPUB Content Documents linked to from the EPUB Navigation Document must be listed in the spine, as well, regardless of whether the Navigation Document has been included in the spine.
|
(from
http://www.idpf.org/epub/301/spec/ep...sec-spine-elem ). See also this epubcheck issue:
https://github.com/IDPF/epubcheck/issues/545 .
Note that the same problem should not occur when "translating" the NCX into the corresponding <nav> in the nav document, since the referenced content documents were required to be in the spine by EPUB2 already. (Hence, adding a similar filter block for the TOC <nav> would be redundant.)
Quote:
Originally Posted by KevinH
So it all looks good. Please generate a pull request and I will merge it tonight when I get home from work.
|
Done.