View Single Post
Old Yesterday, 12:18 PM   #5
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.8.0 is out, with 48 new sets. That makes 672, plus the two templates.

The largest group is EPUB 2: 21 sets on ops:switch from OPS 2.0.1 section 2.6.3.1. They cover where a switch may stand, what its case and default must hold, and whether the content of the default fits where the switch is, in body, in a paragraph, in lists, in a definition list and in tables. 11 of them are valid and 10 invalid, and both validators agree on all of them.

Then 15 CSS sets, which styloria asked for: pseudo-classes after a pseudo-element (Selectors 4), a second shadow part or a structural pseudo-class after a shadow part (CSS Pseudo-Elements 4), four style sheets whose last block is still open at the end of the file, and ui-serif as an @font-face family name. All of them are valid EPUB.

The third group answers a question I asked the EPUB working group in w3c/epub-specs#3115: what it means that an EPUB style sheet "MUST NOT include the direction property". The answer was that the property must be declared, that is, still there after the CSS parser has read the sheet, and that a style attribute counts as a style sheet. So a direction declaration that CSS throws away is valid: one with a value direction does not take, one inside an unknown at-rule, one in a rule with an invalid selector or an undeclared namespace prefix, one after a stray closing brace. Using direction only as an @supports condition is valid too. But direction or unicode-bidi in a style attribute is invalid, inline SVG included. Each book's README says why.

The last new book is an AES-encrypted content document whose encryption.xml has no EncryptedKey. It is valid: w3c/epub-specs#3112 made EncryptedKey optional and called it a fix. That change is in the EPUB 3.4 draft, and I apply it to EPUB 3.3 too.

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. Every book's epubveri output now comes from epubveri 0.47.0. Three older books get an extra advisory message from it, and none changes its verdict.

epubcheck 5.4.0 now disagrees with 92 of the books. In 45 it reports nothing where the specification says invalid, and in 49 it reports an error where the specification says valid (two books have both). For the new direction books I opened w3c/epubcheck#1781. epubveri reports an error on the six where CSS throws the declaration away, so it is marked too (it had no marks in v0.7.0), and it knows.

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.8.0
Kayadelenium is offline   Reply With Quote