v0.7.0 is out, with 24 new sets. That makes 624, plus the two templates.
These are mostly the cases I held back until 15 November because neither validator caught them. In the container: a compressed mimetype file, a "version needed to extract" of 63, a file name of 256 bytes, the mimetype file listed in the manifest, a ZIP entry that promises a data descriptor and has none, and 22 bytes slipped inside the mimetype data so that every offset after it is off. In content documents: dir=" rtl" with a leading space, bdo with dir="auto", an img with no alt, and a fixed-layout viewport with a height of 0. For EPUB 2 there are six OPS 2.0.1 rules (an object whose type differs from the manifest, noscript before its script, a style element of type text/plain, align="char", and SVG animation and script) and four OPF 2.0.1 ones.
Three of the new books are valid, and they may be the most useful ones for anyone who writes a ZIP reader. In each, the local header of one file disagrees with its central directory entry: on the compression method, on the compressed size, or on the CRC-32. The ZIP specification asks for a corresponding central record, but not for equal fields, so I read them as valid. Readers still differ on them: Info-ZIP's unzip reports a bad CRC on two of them, while Python's zipfile reads all three.
Every book is on one
index page, with what it should give and what each validator says, and the release has them all as downloads.
epubcheck 5.4.0 now disagrees with 81 of the books. In 44 it reports nothing where the specification says invalid, and in 39 it reports an error where the specification says valid (two books have both). The new misses are in two issues I opened today,
w3c/epubcheck#1779 (the EPUB 3 container and ZIP cases) and
#1780 (the OPS 2.0.1 cases). No book is marked against epubveri, but only because it was fixed for these cases before the release. Its output on the 602 older books did not change.
One case is still held on purpose: EPUB 3.4 drops the "www" from the structure vocabulary's prefix URL, and that book waits until 3.4 is a Recommendation. The cases with no clear rule stay in the
open questions issue.
As before, the expected results are my readings of the specifications, and anyone can dispute them. If one looks wrong to you, say so here or under the book's issue. If you have a case you would like to see, tell me and I'll make the book.
https://github.com/veripublica/epub-...ses/tag/v0.7.0