View Single Post
Old 07-10-2024, 04:16 PM   #10
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,092
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by kovidgoyal View Post
The *only* valid reason for me to dumb down calibre's output is if that output causes issues with a significant fraction of real world reading software. epubcheck simply isn't a reason I will ever do that. As I said in the FAQ, if this is a problem for you, then calibre is not the software for you.
Or you use calibre realizing that you may have to check and correct issues spit out by epubcheck if you are preparing an ePub for commercial use where they seem to love using epubcheck. For the end user, the renderer you use is supposed to treat any unknown/unimplemented items as nulls. For me, items such as role: in an ePub2 have never caused me any issues when reading.

For me, the time saved by using calibre more than covers the time to correct any issues that epubcheck may have with a calibre generated epub. Specifying ePub3 as the output helps so role:, epub:type, epub:prefix, etc. are not considered errors.
DNSB is offline   Reply With Quote