Thread: [GUI Plugin] Annotations
View Single Post
Old 01-16-2019, 06:59 PM   #561
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 Dfaure View Post
Hi,
I just found this: https://www.albertopettarin.it/exportnotesodyssey.html

Which may be worth getting your plugin to work with Bookeen e-readers.
That is basically just a script to parse the annot files that the Adobe RMSDK produces. Which means the Bookeen ereaders are using the RMSDK for reading epubs. Which is not that surprising as it is the only way that I know of to support books with Adobe DRM.

There is still a lot to do before it can be used. It reads only one annot file. But, I would expect there is one file per book that has been opened. The Kobo devices do this for epubs, as well as their database which the plugin reads.

Then there needs to be a way to map the annotations back to the books. Unless there is a database somewhere, that can be a pain and inaccurate. It depends on how they are stored and how the driver for the device handles it.

If someone wants to add support for the Bookeen devices, then this is probably the way to go. I'll be happy to help, but, without the device in my hands, it's not something I am interested in doing myself.

This does suggest something else, and I'm a little embarrassed I didn't think of it before. This could be used to add generic support for RMSDK readers. Or at least a framework to support them. That is a bit more interesting to me. But, again, it isn't something I'm likely to do without some help from someone with a device that would use it. At the least, someone is needed for testing. Ideally, I would like someone with the device for writing the device specific code.
davidfor is offline   Reply With Quote