Quote:
Originally Posted by KevinH
I am glad to hear that a sideloaded apnx file can be consumed and that the .azw3r and .azw3f funny pieces are created during reading.
|
The PW2 only creates an .azw3r file if an .apnx was copied to the .sdr folder prior to opening the ebook for the first time. (It also creates an addional .mbp1 file in .sdr folders of mobi7 files.) However, it seems that it cannot create an .azw3r/.mbp1 that contains valid page number references from the reverse-engineered .apnx files.
I've created another set of test files with page numbers wrapped in <div>...</div> tags with ids. I've also added page target links to the HTML TOC for testing purposes.
When accessing pages via that TOC, my K3 always displayed the correct page number, it also displayed the correct page numbers at the beginning of a new chapter when using the page forward/backward buttons.
However, when I selected the next chapter with the four-way button, my K3 would display the previous page number for azw3 files and the correct one for mobi7 files. IMHO, this is as good as it gets and I won't do any more research about this.
Please find attached the updated files generated with KindleUnpack_v072f_test. (This time I've also included the mobi7 sidecar files generated by my PW2 and the .mbp and .han files generated by my K3.)