View Single Post
Old 03-29-2018, 09:20 PM   #2
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,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
This is a long standing bug in the highlighting for epubs.

This happens when you close and reopen the book. When you first create the annotation, the location is correctly stored and displayed. When you close and reopen the book, the location details are lost and always show as 0% in the chapter the book opens to.

This happens because for epubs, the annotations are stored in two places. One is the internal database. The other is a file maintained by the Adobe RMSDK used for rendering epubs. When the book is reopened, these two copies of the bookmarks are merged and, unfortunately, the location details are lost.

A workaround for this is to replace a directory on the device with a file. The RMSDK stores the annotations in files in the directory "Annotations" which is in "Digital Editions". If you remove the "Annotations" directory and replace it with a file of the same name, the annotations files cannot be created and this prevents the problem happening when a book is reopened.

Alternatively, kepubs are not affected by this problem as the RMSDK is not used for them. Converting to kepubs or using the KoboTouchExtended driver in calibre will prevent this problem occurring.
davidfor is offline   Reply With Quote