-
Notifications
You must be signed in to change notification settings - Fork 418
Closed
Labels
spec: EPUB 2.xImpacting the support of EPUB 2.x specificationsImpacting the support of EPUB 2.x specificationsstatus: has PRThe issue is being processed in a pull requestThe issue is being processed in a pull requesttype: false-positiveThis issue is about valid content being incorrectly rejectedThis issue is about valid content being incorrectly rejected
Milestone
Description
Looks like version 5 gets the content modell for del and ins wrong for EPUB2 using XHTML1.1.
XHTML 1.1 allows 'flow mix' - block and inline, epubcheck 5.0.1 does not want block.
Something like
<del datetime="2011-09-02"
cite="#Z">
<h1>Title Old</h1>
</del>
<ins datetime="2011-09-02"
cite="#Z">
<h1>Title New</h1>
</ins>
results in:
Validating using EPUB version 2.0.1 rules.
ERROR(RSC-005): XHTML_ref.epub/Inhalt/test3.xhtml(54,5): Error while parsing file: element "h1" not allowed here; expected the element end-tag, text or element "a", "abbr", "acronym", "applet", "b", "bdo", "big", "br", "cite", "code", "del", "dfn", "em", "i", "iframe", "img", "ins", "kbd", "map", "noscript", "ns:svg", "object", "q", "samp", "script", "small", "span", "strong", "sub", "sup", "tt" or "var" (with xmlns:ns="http://www.w3.org/2000/svg")
ERROR(RSC-005): XHTML_ref.epub/Inhalt/test3.xhtml(58,5): Error while parsing file: element "h1" not allowed here; expected the element end-tag, text or element "a", "abbr", "acronym", "applet", "b", "bdo", "big", "br", "cite", "code", "del", "dfn", "em", "i", "iframe", "img", "ins", "kbd", "map", "noscript", "ns:svg", "object", "q", "samp", "script", "small", "span", "strong", "sub", "sup", "tt" or "var" (with xmlns:ns="http://www.w3.org/2000/svg")
Same test with EPUB3/HTML5 results in no messages.
(edited by @rdeltour for formatting)
Metadata
Metadata
Assignees
Labels
spec: EPUB 2.xImpacting the support of EPUB 2.x specificationsImpacting the support of EPUB 2.x specificationsstatus: has PRThe issue is being processed in a pull requestThe issue is being processed in a pull requesttype: false-positiveThis issue is about valid content being incorrectly rejectedThis issue is about valid content being incorrectly rejected