Quote:
Originally Posted by John F
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.
|
The two renderers are Adobe's RMSDK (compability with Adobe DRM) and ACCESS's Netfront BookReader (epub3 and Japanese typography). Oddly Tolino's firmware has some Readium code but anytime I open an epub3 on an Tolino epos, I get a popup warning me the book may not display properly. It is possible that this may be used in future for their implementation of TEA's DRM (based on Readium's LCP).