View Single Post
Old 10-27-2014, 02:54 PM   #225
shalym
Wizard
shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.shalym ought to be getting tired of karma fortunes by now.
 
shalym's Avatar
 
Posts: 3,058
Karma: 54671821
Join Date: Feb 2012
Location: New England
Device: PW 1, 2, 3, Voyage, Oasis 2 & 3, Fires, Aura HD, iPad
Quote:
Originally Posted by DNSB View Post
The epub renderer is Adobe's RMSDK. The main reason for it's existence is to support Adobe's ADEPT DRM so we can borrow/purchase DRMed epub ebooks. Adobe/Datalogics/whatever have been slowly moving towards epub3 compatibility. The release of RMSDK 11 has taken more steps in that direction through adding chunks of the Readium epub3 technology but RMSDK 11 is not yet available on Kobo's eInk readers. From what I've read, ADE 4.0 which has a similar code base to RMSDK 11 is best described as feature incomplete when it comes to epub3 support.

So I would characterize your belief that Kobo is slighting epub2 as being at best a paranoid fantasy.
I don't understand how Nooks and Sonys were ever able to read borrowed epubs, since they were somehow able to fix some of these issues. Or am I wrong about that? JSWolf, did your Sony have these same issues with epubs that are being reported here?

Shari
shalym is offline   Reply With Quote