View Single Post
Old 03-17-2015, 08:43 PM   #28
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 BryanK View Post
Are you implying that Kobo has the ability to add those features to the RMSDK engine and chooses not to? Or that the ACCESS engine has the ability to read Adobe DRM epubs and provide the same features on them as it does on kepubs? As far as I know, neither is true, but I would be happy to learn otherwise.
Well, I'm the one who made the claim, but yes. The other David's post went into details, but a lot of what we are talking about is probably not in the renderer but in the interface application around it. As an example, the chapter graph in the in-book stats for kepubs is a graph of the word count of each chapter. The word count is calculated for a kepub the first time it is opened and the graph based on that. I think it would be possible to do this for epubs as well. The current position in the epub is available to the application and I'd be surprised if the chapter word count or an equivalent number wasn't as well. And of course, the 1.9.x firmware had an indicator showing the position and chapter positions along the bottom menu when it was displayed. That shows something similar is possible.

And there is no real reason Kobo can't open DRM-free epubs with the kepub reader. The reading position system used is the problem. I would be surprised if the ACCESS engine doesn't also support either the RMSDK or the epub3 reading position. My assumption has been that Kobo has turned this off and added their own position system as part of the justification of their own format. Or, they implemented it a long time ago and have decided to keep it.
davidfor is offline   Reply With Quote