View Single Post
Old 05-09-2024, 03:52 PM   #17
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,066
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Peter Blaise View Post
Regarding epubcheck, I presume from W3.org, do you expect that program to FIX malformatted metadata?
To fix, no. To let you know that there is an issue? Yes. epubcheck, does not have a fix option, it simply lets you know where the error occurred and what it thinks the error is. Even for errors that are caught elsewhere and offer an automatic fix, I will hit fix manually. All too often, the results of an automatic fix have been unexpected, interesting and a pain to fix.

Expecting the same results from a standards compliancy checker and a renderer is a bit of a stretch. The calibre ebook-viewer is Chrome based and is very forgiving of errors as most web browsers tend to be. The calibre ebook-editor BooK Check tool is not as forgiving and epubcheck is basically that martinet who screamed at you over a misplaced comma.

I also use the W3C CSS validation service to check the CSS files for errors such as using a CSS3 (ePub3 uses that flavour) in an ePub2 (CSS 2.1 flavour). It helps to prevent unpleasant surprises for the end user.
DNSB is online now   Reply With Quote