View Single Post
Old 04-07-2012, 03:33 AM   #11
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,382
Karma: 27756918
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
The .mbp file format depends on the firmware version of the Kindle. Given the number of Kindle models this is not a trivial thing to accomplish robustly. IIRC, the changing nature of the .mbp file was what caused GRiker to give up on the fetch annotations function. Even the location of the .mbp file with respect to the ebook file varies in different models. And then lets not forget KF8 which will require a totaly different way of marking positions like the last read position in books. If Amazon holds to their promise of adding KF8 support to the current generation of e-ink devices, that means that this functionality will break when that firmware update happens and after the code will have to be modified to deal with whatever system Amazon uses for KF8, assumng that system is even exposed over the USB connection.

But if someone wants to have a stab at it, feel free, I wont refuse a patch, as long as they also commit to dealing with the bug reports along the lines of calibre is not showing the correct read status/last read position for my book.
kovidgoyal is online now   Reply With Quote