Hi Doitsu,
I am trying to track down the "off by one" issue but I am not having any luck.
Here is your original epub pagemap info
Code:
<page-map xmlns="http://www.idpf.org/2007/opf">
<page href="TOC.xhtml" name=""/>
<page href="chapter1.xhtml#id1" name="i"/>
<page href="chapter1.xhtml#id2" name="ii"/>
<page href="chapter1.xhtml#id3" name="iii"/>
<page href="chapter2.xhtml#id4" name="4"/>
<page href="chapter2.xhtml#id5" name="5"/>
<page href="chapter2.xhtml#id6" name="6"/>
<page href="chapter3.xhtml#id7" name="7"/>
<page href="chapter3.xhtml#id8" name="8"/>
<page href="chapter3.xhtml#id9" name="9"/>
Here is what the created azw3 PAGE section says about page names and offsets
[None, 'i', 'ii', 'iii', '4', '5', '6', '7', '8', '9']
[319, 1204, 4739, 8106, 12062, 15606, 18982, 22948, 26492, 29868]
Here is what the generated apnx file from that page section says about page numbers and offsets :
Decode APNX
mobi8-mobi8-pagemap.apnx .APNX
1 75 10 32
2 r 1
5 a 4
[None, 'i', 'ii', 'iii', '4', '5', '6', '7', '8', '9']
[319, 1204, 4739, 8106, 12062, 15606, 18982, 22948, 26492, 29868]
So the page names and page offsets are absolutely identical as they should be.
And here is the page-map.xml generated when the azw3 was unpacked by KindleUnpack
Code:
<page-map xmlns="http://www.idpf.org/2007/opf">
<page name="i" href="Text/part0001.xhtml#id1" />
<page name="ii" href="Text/part0001.xhtml#id2" />
<page name="iii" href="Text/part0001.xhtml#id3" />
<page name="4" href="Text/part0002.xhtml#id4" />
<page name="5" href="Text/part0002.xhtml#id5" />
<page name="6" href="Text/part0002.xhtml#id6" />
<page name="7" href="Text/part0003.xhtml#id7" />
<page name="8" href="Text/part0003.xhtml#id8" />
<page name="9" href="Text/part0003.xhtml#id9" />
The only difference I can see is that the unnamed page at the beginning of the document that represents the TOC.xhtml did not get assigned a name in the unpacked page-map because that page had no name (it was a nullstring). But that is not the cause of the issue as all of the id="idX" tags align perfectly with the correct page names.
Hmm ... so nothing appears to be off by one here.
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).
Thanks,
KevinH