Quote:
Originally Posted by davidfor
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.
|
I had always assumed that the chapter position was calculated off of the current 1024-character page.
Quote:
|
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.
|
I haven't looked closely at the files of a DRM-stripped kepub. So there are no modifications to the kepub itself to support things like annotations or dictionary lookup? If not (which seems to be the case since you can just rename an epub), then as you say, the only reason DRM-free epubs couldn't be rendered by either engine is the extra step in identifying which epub file has DRM and which doesn't.