Thread: Possible replacement for EPUBCHECK
View Single Post
Old 07-12-2026, 07:38 AM   #57
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,853
Karma: 24222221
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by Kayadelenium View Post
2) Inline elements / loose text at block level (your second example). Before I match this one, a quick question: what EPUB version is the book? The elements listed in the epubcheck message you quoted (address, blockquote, div, h1–h6, ol, p, table, ul…) are the XHTML 1.1 block-level content model, which points to EPUB 2. In EPUB 3 (HTML5), a <span> or loose text directly inside <body> is actually valid flow content, so epubcheck wouldn't flag it there — which is why the correct behaviour depends on the version. If you can confirm 2 vs 3 (or share the OPF version), I'll make sure I target the right content model.
EPUBCheck displayed the error message for an epub2 book with xhtml fies. In epub3 books, the same HTML code won't trigger an error message.
Doitsu is offline   Reply With Quote