View Single Post
Old Today, 09:03 AM   #6
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.9.1 is out. With v0.9.0 from earlier today, that is 16 new sets, 688 in all, plus the two templates.

Seven of the new sets go back to the direction question from v0.8.0. The working group's answer was that direction is forbidden only when the parsed style sheet still holds it. styloria asked which at-rules keep it. A rule under a false condition is kept, @supports not (display: block) and @media not all, and so is a keyframe, so those books are invalid. CSS Paged Media 3 lists direction for @page and direction and unicode-bidi for its margin boxes, so those are invalid too. Firefox drops direction in @page, but the specification keeps it. An @supports rule whose condition does not parse is thrown away with its contents, and direction is not an @font-face descriptor, so those two books are valid.

Seven more are about the XHTML meta element, after a report in the epubveri thread. HTML asks for exactly one of name, http-equiv, charset and itemprop, and for content with name, http-equiv or itemprop. So a meta with only content, with no attributes at all, with both name and http-equiv, or with name and no content is invalid. A meta with property (RDFa) or with itemprop inside an item is valid. In EPUB 2, whose XHTML 1.1 meta needs only content, a meta with only content is valid.

The last two: an itemprop on an element that is in no item, and an AES-encrypted file with OriginalLength="0". Both are invalid.

v0.9.1 adds no sets. Every book's epubveri output now comes from epubveri 0.48.0, which fixed three of the four issues these books found in it. The eight books where it reported a direction declaration that CSS throws away are now valid in it, the four invalid meta books and the zero OriginalLength are now errors, and the other 677 books give the same output as before. epubveri now disagrees with one book, the stray itemprop.

epubcheck 5.4.0 disagrees with 96 of the books. In 47 it reports nothing where the specification says invalid, and in 51 it reports an error where the specification says valid (two books have both). I added the @supports and @font-face books to w3c/epubcheck#1781.

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