Invalid TOC links in some azw3 files

darryl · 04-24-2015, 02:22 AM

I find that when purchasing ebooks from Amazon and downloading an azw3 file it is not that uncommon for the file to have a table of contents with all the links pointing to, usually, the beginning of the book or a point in the first couple of pages. Despite this, chapter links seem to function as intended on the actual Kindle device or application. I haven't yet looked into why this is the case. However, because it is, the invalid TOC probably does not cause problems for most people. I first noted it when trying to read a file converted to epub in Moon Reader some time ago. Moon Reader seems to use these links in its normal operation, and so will usually refuse to go past the first few pages. Also, in the Calibre viewer application, the links in the TOC of course all jump to the incorrect location(s). It is likely, though I have not tested, that other non-Amazon devices and applications will suffer the same problems with the TOC links.

What I have established so far is that the particular problem lies with the azw3 files. It is not peculiar to a particular download method nor it would seem to the presence or otherwise of DRM. I have examined a number of books with the problem by downloading the file to a computer and importing to Calibre, and by importing to Calibre directly from the device. I have also copied a file without drm from the Kindle and opened it directly with the Calibre viewer, and the problem is present in all versions.

What I am currently doing is opening all azw3 files in Calibre viewer before any format conversions etc. to verify that the TOC does not suffer from this problem. On a small sample so far I would estimate about 1 in 10 books is affected. On these books I have been using the Calibre TOC editor to either automatically generate a new TOC if possible, or in other cases, manually correct the links.

I have only just looked at the problem, and if I do look into it further will post again on the topic. In the meantime, has anyone else come across this problem?

PandathePanda · 04-24-2015, 05:03 AM

I've also seen this happening with books from amazon, both on K4PC and Kindle for Blackberry.

eschwartz · 04-24-2015, 03:42 PM

Never seen this. Perhaps try submitting one of them for a (private) bug report, see if there is something calibre can do to sense them properly?

Hitch · 04-25-2015, 09:25 PM

Quote:

Originally Posted by eschwartz

Never seen this. Perhaps try submitting one of them for a (private) bug report, see if there is something calibre can do to sense them properly?

Ditto. I've never seen this in anything I've unpacked, etc. Do we have any idea if this is limited to "self-pubbed" files, or...? And when you say, AZW3, @Darryl, do you mean AZW? Or do you genuinely mean AZW3, because to the best of my knowledge, one can't upload an AZW3 file at the KDP for publication, nor FTP one for a bigger publisher. Just clarifying...?

Hitch

darryl · 04-25-2015, 09:36 PM

Quote:

Originally Posted by Hitch

Ditto. I've never seen this in anything I've unpacked, etc. Do we have any idea if this is limited to "self-pubbed" files, or...? And when you say, AZW3, @Darryl, do you mean AZW? Or do you genuinely mean AZW3, because to the best of my knowledge, one can't upload an AZW3 file at the KDP for publication, nor FTP one for a bigger publisher. Just clarifying...?

Hitch

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.

Hitch · 04-25-2015, 10:23 PM

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

darryl · 04-25-2015, 11:19 PM

Quote:

Originally Posted by Hitch

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

It is peculiar. As I said, my knowledge of TOCS and EBook structures is too limited at this stage. You seem to be much more familiar with the topic than I am.

I have seen a number of different examples but we are probably better to concentrate on the book I mentioned for the moment. If you are sufficiently interested, it might be a good start for you to download it and confirm my findings. This would eliminate the possibility that the problem is peculiar to my setup or that I am missing something. The download link is http://www.amazon.com/Exodus-Trilogy...exodus+andreas. It is free of charge and also of DRM. Alternately, if you wish, given the cirumstances, I don't think there is a problem with me emailing you the file for these purposes.

I have both unpacked the azw3 and examined it in the Calibre editor, and there is no sign of a toc.html file. There is a toc.ncx only.

For this book at least, there seems to be only one html file for the entire book. From memory, this is also true for at least most of the other instances I have seen, so you may be on to something there.

This is not a large or urgent problem. It affects very few people and even then just causes a little inconvenience. But it is, as you say, peculiar.

eschwartz · 04-25-2015, 11:22 PM

I "bought" the book, and cracked it open with calibre editor.

Inside is a single HTML file, all CSS is applied directly via style attributes, chapters are separated by

Code:

<div style="page-break-after:always"></div>

and there are no ids to direct a link to.

The tox.ncx in calibre editor shows a bunch of links to "text/part0000.html" -- no fragment identifier. The ebook-viewer sees the same, I imagine.

On my Kindle, the Go To menu can see the chapters just fine (what id is it pointing at?

). Same with swiping up/down (the KT still allows you to flip though chapters like that).

darryl, you can submit a bug report at http://calibre-ebook.com/bugs -- make sure to mark the bugreport as "private", since free books are still not permissible to redistribute. Submitting to a bug tracker (or private specialist) in private for development purposes is generally accepted as okay, allowing anyone to see the bug report and download the book (other than the developers in charge) is not.

darryl · 04-25-2015, 11:47 PM

Quote:

Originally Posted by eschwartz

I "bought" the book, and cracked it open with calibre editor.

Inside is a single HTML file, all CSS is applied directly via style attributes, chapters are separated by

Code:

<div style="page-break-after:always"></div>

and there are no ids to direct a link to.

The tox.ncx in calibre editor shows a bunch of links to "text/part0000.html" -- no fragment identifier. The ebook-viewer sees the same, I imagine.

On my Kindle, the Go To menu can see the chapters just fine (what id is it pointing at?

). Same with swiping up/down (the KT still allows you to flip though chapters like that).

Thanks for going to the trouble and having a look. This confirms my own experience. But where does this leave us? The Go To menu on the Kindle and on Kindle applications works presumably because it:
1. Does not rely on the toc.ncx; and
2. Does not rely on a toc.html as there is none; and
3. Identifies chapters directly from the div tags.
The Calibre viewer presumably uses the toc.ncx which, as you rightly point out, does not function as there are no ids to direct a link to. Moon Reader, when there is a toc.ncx present, seems to actually use the links to progress through the book, hence (with a converted epub, of course) will not progress past the first couple of pages unless the toc is corrected or removed. I haven't tested others, but imagine that most other non-Kindle readers and reading software will be fine reading the book (once again appropriately converted, of course) but the TOC links will not be functional.

I corrected the problem relatively easily in Calibre's toc editor by deleting the contents of the existing TOC and auto-generating a new working one. However, I recall one other book which had no TOC and where any of the existing auto-generation options resulted in an empty one. In this case I "gave up" and just created it manually as it would have taken me far longer to play with XPath expressions for a likely one-off case.

Is my description of what is happening correct? I am currently checking all azw3 files I download for this problem, and correcting it before importation to Calibre. I am finding probably about 1 in 10 books affected on a small sample so far. Can you think of any better solution than my current one?

I am reluctant to submit it as a bug, since I really don't see it as a problem with Calibre, and I also don't see any easy fix forthcoming. I suspect that the Calibre Developers have far more important priorities, as this thread now at least lets those concerned know what the problem is and how to correct it. What do you think?

Once again, thank you for your help.

eschwartz · 04-26-2015, 12:34 AM

I think whoever created these books deserves a slap.

I would say there is nothing else to be done, but... thing is, I was unaware there was any other way to identify chapters. Clearly, my Kindle disagrees with me, and for that reason alone it *might* be worth investigating and possibly utilizing that instead. Then again maybe it isn't really worth trying to fix for a clearly broken book.

Perhaps it is working off the page-breaks??? At least I can see the swipe-to-switch-chapters working that way, but the Go To menu is a puzzle.
Since I don't really know a lot about mobi7/8 internals, I am not going to try answering this mystery.

darryl · 04-26-2015, 01:28 AM

I don't think I'll report a bug. As you said, whoever created these books deserves a slap. It's just a shame that this seems to be happening with a not insignificant proportion of Amazon books. I think Hitch may be on to something, in that it could be exclusively or at least mostly happening with some self-published titles with the text in one html file, which he associates, no doubt correctly, with the original book source being a Word file.

The Go To menu is clearly a puzzle. It seems to me that it must either not in fact use the toc.ncx in any case, or somehow be able to identify that the toc.ncx contains invalid links. Or perhaps it only uses a toc.html and defaults to this other method (perhaps the divs with the page breaks) as a final fallback if there is no toc.html. I suppose this could be tested relatively easily by anyone curious enough. I don't know if I am at this stage.

I usually read Kindle Unlimited titles on my Paperwhite 2 and most others on my H2O. I have, however, recently acquired a Huwaei Ascend Mate 7 Android Mobile with a 6 inch screen, which I find I am using quite often when out of the house in preference to carrying a separate ereader. The Kindle App on this phone works well. However, Moon Reader is excellent for not only reading but for text to speech, using Ivona Nicole, which I do like to use from time to time. Moon Reader also works well with calibre2opds. I am mainly inconvenienced by this TOC problem at the moment when the TOC links fail to work on my H2O, or where Moon Reader fails to work when I want a text to speech interlude.

Hitch · 04-26-2015, 05:09 AM

Quote:

Originally Posted by eschwartz

I "bought" the book, and cracked it open with calibre editor.

Inside is a single HTML file, all CSS is applied directly via style attributes, chapters are separated by

Code:

<div style="page-break-after:always"></div>

and there are no ids to direct a link to.

The tox.ncx in calibre editor shows a bunch of links to "text/part0000.html" -- no fragment identifier. The ebook-viewer sees the same, I imagine.

On my Kindle, the Go To menu can see the chapters just fine (what id is it pointing at?

). Same with swiping up/down (the KT still allows you to flip though chapters like that).

darryl, you can submit a bug report at http://calibre-ebook.com/bugs -- make sure to mark the bugreport as "private", since free books are still not permissible to redistribute. Submitting to a bug tracker (or private specialist) in private for development purposes is generally accepted as okay, allowing anyone to see the bug report and download the book (other than the developers in charge) is not.

eschwartz:

I have an idea/question: what style attribute(s), EXACTLY, define the chapter elements (hearders)?

And when you say that the "Go To" menu works, generally, the Go To goes to Beginning, TOC (if one is there and identified in the guide), Cover, and, depending on the bookmaker, etc., some of the other frontmatter. Normally, the Go To itself does not go to the individual chapters, nor display them on the Go To Menu. Are you saying that the Go To menu is displaying individual chapters?

Oh! Can you also do a fast search for anything identified with a #? As in the old ahref naming scheme, like "start?" Thanks.

@Darryl said:

Quote:

You seem to be much more familiar with the topic than I am.

Dear Odin, I certainly would hope so! It's my line of biz. And no, I shouldn't expect you to know that, of course.

Hitch

darryl · 04-26-2015, 06:55 AM

@Hitch. I suppose I should have visited the link in your signature. I've now remedied this oversight. I should have realised I was dealing with a professional! It's a shame that the author did not use your services, and also a shame that Amazon did not make him! Not worth your professional effort.

However, I gather you are now probably too curious to leave it alone, so I will attempt an answer to your questions to eschwartz.

1. So far as chapter elements are concerned, here are a couple of examples:

Prologue

Spoiler:

Chapter One

Spoiler:

Chapter 12

Spoiler:

Epilogue

Spoiler:

2. Each chapter is in fact shown in the Go To menu. The first entry, as you might expect, is "Beginning". Then page or Location, then Cover. This is followed by an entry for each chapter beginning at the Prologue, going through to the epilogue and even a couple of author links etc listed in the invalid ncx file. The final entry is End.

3. A "grep -i "#?" part0000.xhtml" in the extracted OEPBS Text directory yields no result, but I'm not totally clear on what it is I should be searching for here. A search for just "?" would not be too practical.

regards,

Darryl

darryl · 04-26-2015, 08:56 AM

@Hitch. On looking at your post again I think this is probably more what you were looking for in your third question, though it doesn't seem to be much help as it looks like the "#" characters in the file are only used in the color tags.

Code:

grep -i "#" part0000.xhtml 
   <p style="margin:0.00% 0.00%; line-height:200%; "><span style=" font-size:1.0rem">Website: </span><a href="http://www.christensenwriting.com/"><span style=" font-size:1.0rem; text-decoration:underline; color:#0000ff">http://www.christensenwriting.com</span></a></p> 
   <p style="margin:0.00% 0.00%; line-height:200%; "><span style=" font-size:1.0rem">Blog: </span><a href="http://www.christensenwriting.com/blog"><span style=" font-size:1.0rem; text-decoration:underline; color:#0000ff">http://www.christensenwriting.com/blog</span></a></p> 
   <p style="margin:0.00% 0.00%; line-height:200%; "><span style=" font-size:1.0rem">Amazon: </span><a href="http://www.amazon.com/author/andreaschristensen"><span style=" font-size:1.0rem; text-decoration:underline; color:#0000ff">http://www.amazon.com/author/andreaschristensen</span></a></p> 
   <p style="margin:0.00% 0.00%; line-height:200%; "><span style=" font-size:1.0rem">Twitter: </span><a href="http://www.twitter.com/achr75"><span style=" font-size:1.0rem; text-decoration:underline; color:#0000ff">http://www.twitter.com/achr75</span></a></p> 
   <p style="margin:0.00% 0.00%; line-height:200%; "><span style=" font-size:1.0rem">Facebook: </span><a href="http://www.facebook.com/christensenwriting"><span style=" font-size:1.0rem; text-decoration:underline; color:#0000ff">http://www.facebook.com/christensenwriting</span></a></p>

eschwartz · 04-26-2015, 11:06 AM

Hitch -- as for the Go To menu, it has always shown individual chapters, for a given value of "whatever has been properly formatted into the navigational ToC.
The nav elements are scrollable and sort of appear in an embedded view in the Go To menu, almost like the toc.ncx is rendered in an iframe as its own Go To element. Guide elements appear above and below.

I have been made aware that Kindle Previewer shows stuff a little different from the way E-Ink Kindles do, but I figure you'd know this already, what with all the testing devices you own.

04-24-2015, 02:22 AM	#1
darryl Wizard Posts: 3,108 Karma: 60231510 Join Date: Nov 2011 Location: Australia Device: Kobo Aura H2O, Kindle Oasis, Huwei Ascend Mate 7	Invalid TOC links in some azw3 files I find that when purchasing ebooks from Amazon and downloading an azw3 file it is not that uncommon for the file to have a table of contents with all the links pointing to, usually, the beginning of the book or a point in the first couple of pages. Despite this, chapter links seem to function as intended on the actual Kindle device or application. I haven't yet looked into why this is the case. However, because it is, the invalid TOC probably does not cause problems for most people. I first noted it when trying to read a file converted to epub in Moon Reader some time ago. Moon Reader seems to use these links in its normal operation, and so will usually refuse to go past the first few pages. Also, in the Calibre viewer application, the links in the TOC of course all jump to the incorrect location(s). It is likely, though I have not tested, that other non-Amazon devices and applications will suffer the same problems with the TOC links. What I have established so far is that the particular problem lies with the azw3 files. It is not peculiar to a particular download method nor it would seem to the presence or otherwise of DRM. I have examined a number of books with the problem by downloading the file to a computer and importing to Calibre, and by importing to Calibre directly from the device. I have also copied a file without drm from the Kindle and opened it directly with the Calibre viewer, and the problem is present in all versions. What I am currently doing is opening all azw3 files in Calibre viewer before any format conversions etc. to verify that the TOC does not suffer from this problem. On a small sample so far I would estimate about 1 in 10 books is affected. On these books I have been using the Calibre TOC editor to either automatically generate a new TOC if possible, or in other cases, manually correct the links. I have only just looked at the problem, and if I do look into it further will post again on the topic. In the meantime, has anyone else come across this problem?

04-25-2015, 11:22 PM	#8
eschwartz Ex-Helpdesk Junkie Posts: 19,422 Karma: 85397180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I "bought" the book, and cracked it open with calibre editor. Inside is a single HTML file, all CSS is applied directly via style attributes, chapters are separated by Code: <div style="page-break-after:always"></div> and there are no ids to direct a link to. The tox.ncx in calibre editor shows a bunch of links to "text/part0000.html" -- no fragment identifier. The ebook-viewer sees the same, I imagine. On my Kindle, the Go To menu can see the chapters just fine (what id is it pointing at? ). Same with swiping up/down (the KT still allows you to flip though chapters like that). darryl, you can submit a bug report at http://calibre-ebook.com/bugs -- make sure to mark the bugreport as "private", since free books are still not permissible to redistribute. Submitting to a bug tracker (or private specialist) in private for development purposes is generally accepted as okay, allowing anyone to see the bug report and download the book (other than the developers in charge) is not. Last edited by eschwartz; 04-25-2015 at 11:28 PM.

04-26-2015, 06:55 AM	#13
darryl Wizard Posts: 3,108 Karma: 60231510 Join Date: Nov 2011 Location: Australia Device: Kobo Aura H2O, Kindle Oasis, Huwei Ascend Mate 7	@Hitch. I suppose I should have visited the link in your signature. I've now remedied this oversight. I should have realised I was dealing with a professional! It's a shame that the author did not use your services, and also a shame that Amazon did not make him! Not worth your professional effort. However, I gather you are now probably too curious to leave it alone, so I will attempt an answer to your questions to eschwartz. 1. So far as chapter elements are concerned, here are a couple of examples: Prologue Spoiler: <p style="margin:0.00% 0.00% 1.43%; text-indent:3.0em; line-height:150%; "><div style="page-break-after:always"></div><br style="page-break-before:always; clear:both"/></p> <div style="page-break-after:always"></div><h1 style="margin:0.00% 0.00%; page-break-before:always; line-height:150%; "><span style=" font-size:1.2rem; font-weight:bold">Prologue</span></h1> <p style="margin:0.00% 0.00%; text-indent:3.0em; line-height:200%; "><span style=" font-size:1.0rem"> </span></p> Chapter One Spoiler: <div style="page-break-after:always"></div><h1 style="margin:0.00% 0.00%; page-break-before:always; line-height:150%; "><span style=" font-size:1.2rem; font-weight:bold">Chapter 1</span></h1> <h2 style="margin:2.57% 0.00% 0.00%; page-break-after:avoid; line-height:150%; font-weight:normal"><span style=" font-size:1.0rem; font-style:italic">November 2072 ~ North Africa</span></h2> Chapter 12 Spoiler: <div style="page-break-after:always"></div><h1 style="margin:0.00% 0.00%; page-break-before:always; line-height:150%; "><span style=" font-size:1.2rem; font-weight:bold">Chapter 12</span></h1> <h2 style="margin:2.57% 0.00% 0.00%; page-break-after:avoid; line-height:150%; font-weight:normal"><span style=" font-size:1.0rem; font-style:italic">208</span><span style=" font-size:1.0rem; font-style:italic ;letter-spacing:0.25rem">6</span><span style=" font-size:1.0rem; font-style:italic"> </span><span style=" font-size:1.0rem; font-style:italic ;letter-spacing:0.25rem">~</span><span style=" font-size:1.0rem; font-style:italic"> Interstellar space</span></h2> Epilogue Spoiler: <div style="page-break-after:always"></div><h1 style="margin:0.00% 0.00%; page-break-before:always; line-height:150 %; "><span style=" font-size:1.2rem; font-weight:bold">Epilogue</span></h1> <h2 style="margin:2.57% 0.00% 0.00%; page-break-after:avoid; line-height:150%; font-weight:normal"><span style=" fo nt-size:1.0rem; font-style:italic">2245 ~ Aurora</span></h2> 2. Each chapter is in fact shown in the Go To menu. The first entry, as you might expect, is "Beginning". Then page or Location, then Cover. This is followed by an entry for each chapter beginning at the Prologue, going through to the epilogue and even a couple of author links etc listed in the invalid ncx file. The final entry is End. 3. A "grep -i "#?" part0000.xhtml" in the extracted OEPBS Text directory yields no result, but I'm not totally clear on what it is I should be searching for here. A search for just "?" would not be too practical. regards, Darryl

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
epub --> azw3 links loss	kerliza	Conversion	9	09-26-2014 01:09 AM
"invalid start byte" when trying to open a azw3 file with calibre	berlineirn06	Conversion	4	12-26-2012 01:44 PM
Generated TOC links back to TOC page in the book	Caleb666	Sigil	7	08-17-2011 11:58 AM
Redundant/Invalid TOC entries	Stinger	Kobo Reader	4	06-26-2010 09:02 PM
patch: LrfError: page id invalid in toc	grimborg	Calibre	0	04-07-2010 05:22 AM

04-24-2015, 05:03 AM	#2
PandathePanda a toy panda Posts: 2,567 Karma: 26020474 Join Date: Mar 2014 Location: Onboard the Queen Anne's Revenge Device: Various Android dvices	I've also seen this happening with books from amazon, both on K4PC and Kindle for Blackberry.

04-24-2015, 03:42 PM	#3
eschwartz Ex-Helpdesk Junkie Posts: 19,422 Karma: 85397180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Never seen this. Perhaps try submitting one of them for a (private) bug report, see if there is something calibre can do to sense them properly?

04-26-2015, 12:34 AM	#10
eschwartz Ex-Helpdesk Junkie Posts: 19,422 Karma: 85397180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I think whoever created these books deserves a slap. I would say there is nothing else to be done, but... thing is, I was unaware there was any other way to identify chapters. Clearly, my Kindle disagrees with me, and for that reason alone it might be worth investigating and possibly utilizing that instead. Then again maybe it isn't really worth trying to fix for a clearly broken book. Perhaps it is working off the page-breaks??? At least I can see the swipe-to-switch-chapters working that way, but the Go To menu is a puzzle. Since I don't really know a lot about mobi7/8 internals, I am not going to try answering this mystery.

04-26-2015, 01:28 AM	#11
darryl Wizard Posts: 3,108 Karma: 60231510 Join Date: Nov 2011 Location: Australia Device: Kobo Aura H2O, Kindle Oasis, Huwei Ascend Mate 7	I don't think I'll report a bug. As you said, whoever created these books deserves a slap. It's just a shame that this seems to be happening with a not insignificant proportion of Amazon books. I think Hitch may be on to something, in that it could be exclusively or at least mostly happening with some self-published titles with the text in one html file, which he associates, no doubt correctly, with the original book source being a Word file. The Go To menu is clearly a puzzle. It seems to me that it must either not in fact use the toc.ncx in any case, or somehow be able to identify that the toc.ncx contains invalid links. Or perhaps it only uses a toc.html and defaults to this other method (perhaps the divs with the page breaks) as a final fallback if there is no toc.html. I suppose this could be tested relatively easily by anyone curious enough. I don't know if I am at this stage. I usually read Kindle Unlimited titles on my Paperwhite 2 and most others on my H2O. I have, however, recently acquired a Huwaei Ascend Mate 7 Android Mobile with a 6 inch screen, which I find I am using quite often when out of the house in preference to carrying a separate ereader. The Kindle App on this phone works well. However, Moon Reader is excellent for not only reading but for text to speech, using Ivona Nicole, which I do like to use from time to time. Moon Reader also works well with calibre2opds. I am mainly inconvenienced by this TOC problem at the moment when the TOC links fail to work on my H2O, or where Moon Reader fails to work when I want a text to speech interlude.

04-26-2015, 11:06 AM	#15
eschwartz Ex-Helpdesk Junkie Posts: 19,422 Karma: 85397180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Hitch -- as for the Go To menu, it has always shown individual chapters, for a given value of "whatever has been properly formatted into the navigational ToC. The nav elements are scrollable and sort of appear in an embedded view in the Go To menu, almost like the toc.ncx is rendered in an iframe as its own Go To element. Guide elements appear above and below. I have been made aware that Kindle Previewer shows stuff a little different from the way E-Ink Kindles do, but I figure you'd know this already, what with all the testing devices you own.

Advert

Advert