Quote:
Originally Posted by DiapDealer
In all fairness ... there's technically not anything to "fix" in KDP (WRT this particular issue, anyway). Whatever processing is going on, it's producing a valid Kindlebook with a working internal NCX ToC--functional on all Kindle devices/apps. Problems only arose because KindleUnpack and calibre didn't (then) have a way of unbinary-ing them while retaining the functional ncx.  |
Thanks. This is of course correct. So, not being anything to "fix", there is no reason for them to fix it. So there is still hope for anyone curious enough to run a test case or two through KDP. At the moment we know the original input to KDP for Exodus was from Word and little else. I'm curious and will keep an eye on this thread in case there are further developments, but I can't think of any good reason beyond simple curiousity for anyone to waste further time now this anomaly has been fixed in Calibre and KindleUnpack.