Quote:
Originally Posted by darryl
I've only noticed it relatively recently, and so far only in actual azw3 files downloaded from Amazon. It may extend to older mobi files also. One thing which really puzzles me so far is that links to chapters etc seem to work in Kindle devices or applications, despite the invalid links in the TOC. When I get the chance I'm intending to improve my knowledge of TOC's, but I am even wondering whether there is something in Kindlegen which creates a TOC valid only on a Kindle or Kindle application.
A reasonably typical example is the Amazon azw3 ebook "Exodus" by Andress Christensen. This is Part 1 of "The Exodus Trilogy" and is currently available for free and without DRM. i have both downloaded the file to computer and had delivered to the Kindle. The behaviour is the same. On the Kindle the TOC links work. In Calibre Viewer, the book can be read normally but TOC links do not work. If converted to EPub and loaded in Moon Reader it will not progress past the first couple of pages, presumably because Moon actually uses the TOC if present to page through the Book in normal reading.
|
Well, this seems at best peculiar. I don't see how non-functional file links, in a book, can work, if they are broken, unless the PW (Publishing Workflow)creates some sort of Kindle (Amazon_specific) redirect sort of thing, but again...never seen this. Bizarre.
We are discussing the toc.html, right, and not the NCX? (Just to narrow down the discussion). And, can you advise, @Darryl, do you think you are seeing this in MOBIs that are built from an ePUB-like structure (multiple files, one per section/chapter, using a spine, etc.) or are they Word-file uploads, with a single HTML file, arguably, for the entire book?
Hitch