View Single Post
Old 03-25-2020, 02:49 PM   #11
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,424
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by hobnail View Post
Internally it's still an epub3 and the kobo will recognize it as such. I doubt if there's any advantage of downloading the epub3 over the epub2; I used to download the epub3 versions but now just get their epub2s. Somewhere I'd downloaded a book that had @ lines at the top of the css which caused my kobo to ignore all of the css; dunno if it was Standard Ebooks or somewhere else.
Unfortunately, the only way to have the epub recognized by the Kobo as an epub3 is to rename it to .kepub.epub which will trigger the use of the epub3 renderer. Kobo does not inspect the ebook to see which renderer to use. The rename does allow more epub3 features but highlighting and other features which depend on the spans added to a 'proper' kepub will not be happy campers. My work flow for epub3 is to run them through either the KoboTouchExtended driver or to use kepubify to add those spans.

If you use the epub2 renderer, RMSDK does have the nasty habit of dumping the CSS after it sees an error. At times, I wonder about Adobe's inability to write a decent error handler.
DNSB is offline   Reply With Quote