![]() ![]() Its value should look something like kobo.206.1 (at least for KEPUB files from what I've seen) and it's the id of a in the HTML file. location_value will give you the line you're currently at. ![]() The location_source will give you the HTML file in which the bookmark is located (from what I understand EPUB and KEPUB are just archives with a bunch of HTML files). You can use the kobo_reading_state to look up an id for a given book_id and then use this id to check for a bookmark in kobo_bookmark. There are a couple tables prefixed with kobo_, but the ones of interest are kobo_reading_state and kobo_bookmark. The progress information for Kobo is stored in app.db. It references the IDs present in the metadata.db. Seems like the app database is being used to store the Kobo stuff, which you can find in /config/app.db (I use sqliteonline to inspect the content of the database). ![]() It happens at this endpoint, while here the values are being read or created. I went through the Kobo code and found out the section, where the reading status is being synced. It could be used to also save the synced kepub information? Or is there a reason for it not being used? I also found out that there is a last_read_positions table present in the metadata.db with the columns: Name That should be saved somewhere and should be somehow convertible to a percentage (see here for the kepub - epub relation). KEPUB has some additional elements with spans containing ids (which are unique in each chapter, so you need the chapter and id to know where you currently are). I am also currently interested in finding a way to save my reading progress in some way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |