View Single Post
Old Yesterday, 04:48 PM   #386
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: 277
Karma: 364036
Join Date: Jul 2026
Location: Planet Earth
Device: Kobo Forma
epubveri 0.44.0 - a small release: one new advisory, and CSS urls inside other functions are now checked like any other url.

https://github.com/veripublica/epubv...es/tag/v0.44.0

If you use one of the plugins, there is nothing to do: all three fetch the latest release on their own. They also turn advisories on, so the new one will show up there. epubveri still never writes to a book.

New advisory: a link whose spelling differs from the file name (ADV-025). This came from the kepubverto thread. In one of my books the manifest names a chapter Agatha'nin_Anahtari_split_000.html, and the table of contents links to Agatha%27nin_Anahtari_split_000.html. Both tools find the file, because they decode %27 back to an apostrophe before they look. A reading system that compares the two names as written sees two different files. My Kobo did exactly that: it counted the chapter twice, and the book opened at page 89 of 178. epubveri now reports such a link when you pass --advisory. It is usage level, so it never changes the verdict. In EPUB 3 it checks the way the URL Standard compares URLs, and in EPUB 2 it reports an encoded apostrophe, bracket, ampersand and the like.

Why only an advisory? Read literally, EPUB 3.3 section 4.2.5 makes this an error: a link must equal the file's URL after parsing, and %27 is not an apostrophe to a URL parser. But epubcheck's own test for that section calls content%26001.xhtml a correct link to content&001.xhtml, and the editors described it the same way in an earlier issue. The text and its own test disagree, so I asked the EPUB Working Group which one is meant: w3c/epub-specs#3116. Until they answer, epubcheck's verdict stands.

What can now fail: a url() inside another CSS function, such as image-set(url(a.png) 1x), gets the same checks a url() gets on its own. A space or a stray character in it is an invalid URL, and a ?query is not allowed. A remote file is allowed only for fonts, audio and video, and then the document needs the remote-resources property. Its target was already checked. epubcheck 5.4.0 never looks inside the function. One check stays at the top level on purpose: a function like image-set() can list its own fallback, so a nested url is not reported for a missing fallback.

Where this goes against epubcheck, each case is listed with its clause and the epubcheck issue under "Known differences from epubcheck" in AGENTS.md.

How I checked. epub-test-books now has 626 published sets. On all 626, epubveri 0.44.0 gives the verdict the specification gives, and epubcheck 5.4.0 does on 547. epub-test-books also built 138 books for the spelling cases above. They are not published yet.

If a book gets a finding you did not expect, the ID it names should make it quick to show me.

crates.io: https://crates.io/crates/epubveri
npm: https://www.npmjs.com/package/@verip.../epubveri-wasm
Kayadelenium is online now   Reply With Quote