Quote:
Originally Posted by dwanthny
Still didn't say yes or no to version 0.7.44? This version came out Friday evening EST (-5 GMT) about 39 hours ago. It also included this new feature.
Quote:
|
MOBI Output: Use the book uuid as the ASIN field and set cdetype to EBOK to allow Amazon furthest read tracking to work with calibre generated MOBI files.
|
I don't have a Kindle but I thought that is what you were asking about. |
I don't think hoyasaxa is referring to synching "furthest read". I think they're referring to problems with the NCX file (which, on the Kindle, enables skipping back and forth between chapters without bouncing back to the inline/HTML TOC each time.)
Quote:
Originally Posted by hoyasaxa
Hey guys- quick question. I had an HTML book. When originally converted to MOBI it had chapters about halfway through, including the bookmarks so you could skip chapters. But I think the book had too many chapters so Calibre ignored the excess.
|
Ummm... what exactly do you mean when you say it "had chapters about halfway through"...?
Quote:
Originally Posted by hoyasaxa
I corrected this and now the TOC includes all chapters.
|
When you say "TOC" do you mean an inline, HTML TOC? Or do you mean the NCX/EPUB TOC which adds "tick marks" to the progress bar on the Kindle?
Quote:
Originally Posted by hoyasaxa
Sadly, there are now no bookmarks at all and skipping chapters is impossible without going all the way to the table of contents.
|
Maybe it's just me, but I'm finding it really confusing trying to work out what's happening here, hoyasaxa.
There are two types of TOC:
1. An NCX file, which contains navigation points coded in XML - most EPUB readers will use the NCX file to present a TOC to the user, which they can use to navigate around the book. However in a MOBI book on a Kindle, the NCX file simply adds tick marks on the progress bar (corresponding to the navigation points), and makes it possible to skip to previous/next navigation points (usually chapters) using the 5-way control button.
2. An inline HTML TOC which forms part of the book content. While not usually needed in an EPUB, this is the only type of TOC which the Kindle will present to the user. Ideally, in a Kindle ebook, you want both an inline TOC and an NCX file.
Please do correct me if I'm wrong, but it sounds like you initially had no HTML TOC and NCX navigation for the first half of the book, but now you have an inline, HTML TOC but no NCX navigation? I'm sure I must have picked that up wrong - could you explain again what's happening, but clarifying when you're referring to an inline TOC and when you're referring to the NCX navigation? That way, someone might be able to advise.
