View Single Post
Old 07-06-2020, 09:36 PM   #12
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
For the record, the most likely reasons for something like this to happen are:
  • Corrupt database. This prevents the annotations from being stored and reread later. This is most likely to happen after the book has been closed and even more likely if the device is restarted.
  • Epub loaded as a kepub without the spans added. Without the spans, the locations in the book cannot be recorded properly. This means the annotations will be lost.
  • Kepub with the spans applied incorrectly. Again, this means the locations in the book cannot be recorded properly. There have been some issues with the some recent versions of the extended driver and Kepub Output plugin that might have caused problems, but, this wasn't something that I explicitly looked at. I believe all issues have been fixed. But, all of this is done by reverse engineering from purchased books, so it might be wrong.

From the original report, I don't know which of the above is the most likely to have been the cause.
davidfor is offline   Reply With Quote