Quote:
Originally Posted by PoP
No, same size but different md5:
Code:
# MD5 checksums generated by MD5summer (http://www.md5summer.org)
# Generated 2018-04-18 07:00:56
fc72d7aa8f3ed258a71df77079dab8bf *XRAY.entities.B00JCDK5ME.asc
|
Thanks. So file size might be a useful information, but not md5sum.
Quote:
Originally Posted by PoP
By the way, this file is an sql data base that you can inspect using DB Browser for SQLite, I don't know how X-ray should be constructed but I saw that the "entity" table has null values where I think there should be book locations ...perhaps explaining the problem. |
That got my hopes up, but my (few) other books with X-ray are the same and X-ray works as far as I can tell on those books. That is, in the entity table only the first row has an entry in the loc_label column. In all cases the id is 0 and loc_label is 1.
I think the problem might be that the excerpt table might have too few rows (only 165), but I haven't had any luck finding any of the first few in it, or figure out the start column. The start column doesn't seem to be the "location" number. It might be the byte number in the azw3.
Argh, I'm just now figuring out the value in the id column of the excerpt table is not related to the value of the id column of the entity table. It does look like the numbers in the related entries column are the id values in the entity column (seems to be the case in other books). In that case, all the values are from 777 through 809 (far too few), but entity they run 1 to 776, so no excerpt can ever be found.