View Single Post
Old 08-19-2017, 10:21 PM   #6
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: 46,728
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Phaedrus Wolfe View Post
We are quite experienced at using styles. Thanks for the notice regarding the new plugin. However, when used, it does not show any epubcheck errors in Calibre, yet the IDPF Epub validator continues to report the error.

Any more suggestions?

Phaedrus
Interesting that you don't see the error running epubcheck 4.0.2 locally while the remote validation shows the error. I don't use the Calibre editor but the epubcheck plugin for Sigil uses the same Java jar file as the online checker and I would suspect the Calibre version does the same. It's possible the dc:type metadata in the epub is hooped so it is not running the correct profile.

One question that comes to mind is what is wrapped around those spans?

Could you try adding a <p> or <div> at the start and </p> or </div> at the end of the error lines to see what that does for the error message?
DNSB is offline   Reply With Quote