Thread: Signalling needed properties for EPUB3
View Single Post
Old 05-21-2016, 11:55 PM   #48
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,435
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Quote:
Originally Posted by bentleymaniac View Post
Obviously, while eink ereaders keep using epub2, there is probaly no need, but are the changes implemented in epub3.1 good enough to warrant including it in Calibre?
EPUB 3.1 is not finalised yet -- and no, I dont see anything in it that makes it worth implementing support for. They basically just get rid of most of the metadata properties they created in EPUB 3 and specify that EPUB is meant to be rendered in browsers so the relevant spec becomes HTML 5. Basically, they declare their own irrelevance.
kovidgoyal is offline   Reply With Quote