View Single Post
Old 10-27-2014, 10:19 PM   #232
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by shalym View Post
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?
I'm not JSWolf, but each of the devices and reader applications that use the RMSDK have problems.

They all use the RMSDK, but they use different versions or builds within the version. Each has different bugs in it. Earlier this year, Kobo updated to RMSDK 10. I think they were using RMSDK 8 before that. I suspect that Sony uses RMSDK 9. Unless you know exactly what version and build is used on each device, it is hard to compare the bugs. Some might not be visible because the device doesn't use a function. And there might be some workarounds in the device to handle a bug differently.
davidfor is offline   Reply With Quote