epubcheck
epubcheck copied to clipboard
w3c
The conformance checker for EPUB publications
See https://github.com/w3c/epub-specs/issues/1205
The requirement for par and seq elements to match the default reading order has been moved to the accessibility specification. Epubcheck shouldn't emit errors now if there's a mismatch. https://github.com/w3c/epub-specs/issues/1458
The lack of the following file extensions should not result in warnings: - .xhtml for xhtml content documents - .svg for svg content documents - .pls for pls lexicon files...
Without an epub:type, the nav element is just regular xhtml. https://github.com/w3c/epub-specs/issues/976
Pretty sure this is impossible to check, but opening for completeness. I suspect all this could ever be is an info message to check when overlays are present but no...
A mismatch should be reported as a warning. https://github.com/w3c/epub-specs/issues/1322
The 3.3 spec clarifies that if a script element contains a data block it is not a scripted content document. There shouldn't be an error that the scripted property is...
The requirement that [ordering of links in the toc nav](https://w3c.github.io/epub-specs/epub33/core/#sec-nav-toc) match both the spine order of content documents and the order of elements within them has been reduced to a...
EPUB 3.3 disallows w3.org and idpf.org from [custom attribute namespaces](https://w3c.github.io/epub-specs/epub33/core/#sec-xhtml-custom-attributes). See https://github.com/w3c/epub-specs/issues/1388 This is a change from 3.2 where only the following two specific URIs were forbidden: - http://www.w3.org/1999/xhtml -...
(This seems to be related to https://github.com/w3c/epubcheck/issues/173#issuecomment-27623760, although not to `rdf:RDF`, which is the original topic of that issue.) The [W3C SVG Logo](https://www.w3.org/StyleSheets/TR/2016/logos/W3C.svg) is not accepted by epubcheck, complaining about...
