View Single Post
Old 01-30-2020, 04:35 AM   #19
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,121
Karma: 92500001
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by mergen3107 View Post
It can only fetch the current location from /var/local/cc.db, because cc.db is updated only on book closing. It should, in future, be able to redraw the progressbar at every page turn by using a new location estimate. I think I should try to fetch a more precise new location that appears in 'showlog -f' at every page turn, but they seem to be in the units of html symbols or something instead of locations.
See this thread for information on parsing files that contain reading progress and are (AFAIK) updated with every page turn: KRDS - A parser for Kindle reader data store files

(Added: Post #7 in that thread has a little info about how to interpret reading positions.)

(Further added: The translation table between "positions" and "locations" in KF8 (azw3) format is contained in the DATP MOBI record.)

Last edited by jhowell; 01-30-2020 at 05:09 AM.
jhowell is offline   Reply With Quote