Thread: Firmware 4.8.11073
View Single Post
Old 05-28-2018, 09:13 PM   #41
John F
Grand Sorcerer
John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.
 
Posts: 7,951
Karma: 70880793
Join Date: Feb 2009
Device: Kobo Clara 2E
Quote:
Originally Posted by ottdmk View Post
It's not an omission. Kobo uses Adobe's RMSDK to display epub books. (Note: I'm glad they do, as it's RMSDK that enables library loans to my Kobo.) RMSDK doesn't implement that feature.

Kobo uses its own display engine for kepubs. They've added several features there, which is straightforward to do, as they control the software.

So it's not that Kobo neglected to implement something: it's that they can't implement changes to RMSDK. That's Adobe's department.
I thought that Kobo used Readium, not "their own display engine"?

And as far as not being able to implement changes to RMDSK, maybe they don't have to, and could still get the functionality; it looks like all the info is there, it may just be a little harder to get than a simple API call.
John F is offline   Reply With Quote