View Single Post
Old 11-13-2026, 01:29 PM   #3
Kayadelenium
Addict
Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.
 
Kayadelenium's Avatar
 
Posts: 293
Karma: 364036
Join Date: Jul 2026
Location: Planet Earth
Device: Kobo Forma
v0.6.0 is out, with 376 new sets. That makes 600, plus the two templates.

Everything on last time's "not built yet" list is in. There are 72 sets on EPUB 3.3 fixed layout (the rendition properties, the viewport meta tag and its syntax, the initial containing block), 77 on EPUB 2 (OCF 2.0.1 and OPS 2.0.1 content documents), and 74 on CSS, from CSS Syntax 3 encoding and error recovery to selectors and the cascade. AES-encrypted books are in the container section now, next to ZIP64 and obfuscation. The other new sections are media overlays (46) and more content documents (70): dir and bdo, scripting, epub:type and prefixes, RDFa and microdata, switch, trigger and SVG content documents.

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 disagrees with 61 of the books. In 24 it reports nothing where the specification says invalid, and in 39 it reports an error where the specification says valid (two books have both). Most of the second kind are CSS that EPUB 3.3 allows but its CSS parser does not know yet, such as nested rules. Each of those books quotes the clause and links the issue I opened on epubcheck. As before, these are my readings, and anyone can dispute them.

One of the open questions went to W3C, and the working group discussed it at its meeting on 12 November: an encryption.xml entry for a file that is not in the container. Their answer is that it is an error, and a pull request that says so in the EPUB 3.4 draft has been approved. A second question, whether encryption.xml always needs an EncryptedKey, is open as w3c/epub-specs#3112.

No book is marked against epubveri again, but only because I fixed what these sets turned up in it before the release.

The expected results of the new books are still checked only by me, so that is where help is most useful. If one looks wrong to you, say so here or under the book's issue.

A few cases are still held until 15 November, and the ones with no clear rule stay out until W3C answers; both are listed in the open questions 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.6.0
Kayadelenium is offline   Reply With Quote