If I take an untouched retail ePub with a perfectly functioning TOC (ie, which guaranteed navigates to the correct position in the book), convert it to Mobi, and then either to htmlz for editing or even directly back to ePub, the conversion puts the TOC navigation anchors in the wrong spot.
When I look at the intermediate html code, the Mobi conversion has placed tags like:
<pagebreak id="something">
...but it places these
BEFORE the <div class="mbppagebreak"></div> code, so when you navigate in the final converted ePub, it goes to the bottom of the page before page break and the actual chapter you want.
It should be putting these tags AFTER the <div>
And while I'm at it, why doesn't it just add the id=whatever to the <div> tag so you don't need the extra non-standard <pagebreak> tag? The problem is that <pagebreak> isn't a real html tag, and it hangs tools like HTMLTidy, the file can't be processed to clean up the code with these <pagebreak> tags in it, they have to be manually converted to something else like <p> or <div> before Tidy can be used.
Is this something that can please be fixed? manually changing the tags and them moving them to fall after the <div class="mbppagebreak"> tag takes a lot of effort.
Thanks
The REAL Joe