Quote:
Originally Posted by KevinH
So it looks like creating an apnx for a PW2 is not going to be helpful. Sorry about that.
|
No problem. I'm glad that you looked into the possibility of creating such a tool at all when hardly anybody else did. And your tool does seem to work with other KF8-capable Kindles and apps, which is a major improvement over the "fake page numbers" that Calibre generates.
I really don't understand why Amazon don't release the tool that they use to generate .apnx and .azw3r files.
In case Kovid read this, my model's serial number prefix is 90D4 and my firmware is 5.4.3.2. The latest Calibre version obviously cannot generate .azw3r files, because the format hasn't been reverse engineered yet, and transferring .apnx files to sidecar folders is pointless, because they'll be deleted when the book is opened for the first time.
BTW, I'm still puzzled about the "page number drift" that happened on my K3 after the first three pages. I most likely specified the page targets incorrectly or overlooked some other constraints. Maybe someone else who successfully implemented page numbers for a commercial Kindle book can shed some light on this.
Quote:
Originally Posted by KevinH
So can you locate where things appearing to be off by one starts and let me know so that I can try and see if the original xhtml coding is an issue or if the issue is just that more than one page is on the screen at the same time (which is device specific).
|
Each chapter should start with an odd page number, you can see this for example, when you open chapter 3, which should start with page 7, but page 6 is being displayed. All .html pages are identical, except for the page target ids.