Quote:
Originally Posted by isarl
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.  |
Umm... the RMSDK renderer used for epub does not support Javascript. You do remember that Kobo uses 2 renderers? The webkit based renderer used for kepubs can and does support a subset of JS. To quote the page you referenced: "
Kobo’s eInk and Desktop platforms have limited support for JavaScript, and do not support interactive JavaScript elements." Though I will admit the main attachment I have to the kobo.js file is one of the comments:
Quote:
|
Move directly to a page. Remember that there are no real page numbers in a reflowed EPUB document. Use this only in the context of the current document.
|
which appeals to my sense of humour.
All that aside, the main use of the kobo.js file is in the applications such as the Desktop App for Windows and Mac and Kobo app for iOS and Android.
OTOH, when you look at that page please note the majority of the content in the readme.md has not been updated in quite a while. The change last year was simply a change to email address for rendering issues.