Quote:
Originally Posted by DNSB
That functionality was intended for use when doing a quick and dirty check on how a book displayed as a kepub. In a "real" kepub, each sentence is wrapped in a span. This is assigned a unique id. The location system uses these ids. If you just change the extension, when you close and reopen a book, you will always be taken to the start of the chapter you were in and stored annotations will not be re-displayed in the book.
The KoboTouchExtended driver and kepubify will add those extra spans for you.
|
Do you (or does anybody reading this) know how important the kobo.js file is to the renderer for kepubs? I know the KTE driver can use a reference.kepub.epub file in Calibre's plugin directory to copy the kobo.js file contained therein into its own converted kepub files, but also that KTE doesn't ship with a copy of this file by default (which is why it asks you to provide your own reference.kepub.epub file). But I'm not super clear on what configuring this adds.
According to this page, Kobo eReaders don't even support JavaScript anyway, which would seem to make the point rather moot.
