Quote:
Originally Posted by Huwaetzel
Hi wold,
with your new version, which is working fine on my end, I opened my testbook again and found that all page numbers are set to 1 (see screenshot) Using the Pocketbook reader or also the viewer app they are still at the right page.
I used your new debug feature with the SQL raw export, thanks for that  , to create a log file (see .txt attachment)
There is nothing wrong with Avater, but the database entry for the page number may not be the right one. |
Thanks, and yeah, those rows seem to use a (older?) reduced data format.
For tag 101 the "anchor" field is missing, which avater uses to get the page, offset and location from.
Code:
15:03:28 Info: "788: 788 | 787 | 4 | 0 | 1656754282 | 74D7B0C5-57D2-5469-8CDF-C63CAC6E9C40 | 14328 | 788 | 101 | {\n \"created\" : 1654358266,\n \"updated\" : \"2022-06-04T15:58:24Z\"\n}\n | 1654358306" || 11
# expected example:
19:02:58 Info: "8: 8 | 5 | 4 | 0 | 1613764943 | 52910225-37BA-51F5-B144-AB98A277929C | 206 | 8 | 101 | {\"anchor\":\"pbr:/page?page=17&offs=991#epubcfi(/6/14!/4/2/2/2/2/6/14/5:59)\",\"created\":1613764943} | 1613764943" || 11
With that missing, the only location info we get is with tag 104, and that's just the epubcfi, no page/offset. There's a chance the debug might be incomplete
But it should be pretty thorough, getting all rows and columns for a given note ID (can't hurt to check).
For now, any idea why these are different? The testfile worked earlier, or did you create a new one with the 'faulty' data?
Are these regular epub files?
Do they perhaps have page info already stored inside?