View Single Post
Old 02-06-2014, 12:25 AM   #7
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
It is actually the other way around. ACCESS, the kepub renderer, has no support for the Adobe DRM. It is only used for kepubs, but has support for DRM-free epub2 and epub3 (I have no idea about the DRM for epub3). Any changes the new Adobe code brings in will only affect the RMSDK based renderer. This handles epub2 and PDF.

Personally, I have been expecting Kobo to move epubs to ACCESS. I think the Adobe DRM is what has been stopping them. But, they could use ACCESS for all kepubs and DRM-free epubs without much work.

And before anyone comments: Kobo would have to add support for a different reading position system to ACCESS. But, I suspect all they would really need to to is re-enable it. I am fairly sure the reading position used for kepubs is something that Kobo adds. If they do this, hopefully they will use the epub3 method. It will also work for epub2. And yes, here would be lots of wailing about the header and the page numbering system. There is already some evidence in the firmware that these might be changing.
davidfor is offline   Reply With Quote