Thread: On repairing defective apnx files.
View Single Post
Old 11-02-2019, 04:45 PM   #5
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,798
Karma: 103362673
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by KevinH View Post
You could use kindleunpack to generate the Adobe pagemap.xml and use search on the custom form of id you want to verify and/or fix the pagemap.xml file. Then add it to the unpacked epub and pass it through kindlegen and strip out the apnx info into a separate file.
I've used kindleunpack on each of the azw3 files, once with the original apnx file and once with the repaired apnx file that I generated with kindlegen on epubs with a pagelist appended to the toc.ncx. I think the resulting page-map.xml files support my speculation that page information supplied by the publishers had multiple errors due to misidentified HTML link targets as page IDs.

The 3 pairs of page-maps are attached as pagemaps.zip
Attached Files
File Type: zip pagemaps.zip (12.3 KB, 345 views)
j.p.s is offline   Reply With Quote