Thread: TOC in AZW3
View Single Post
Old 08-18-2012, 03:29 PM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,828
Karma: 206879174
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I think you're confounding/conflating/confusing the inline (html) TOC and the NCX navigation TOC. Kindlegen (Previewer) doesn't create an inline TOC, so you must be referring to the navigational (ncx) TOC when you say Kindlegen's version is "OK."

I suspect the the NCX TOC on the calibre converted AZW3 is OK too. Which means that the automatically created/detected inline (html) toc that calibre builds is where you're having trouble.

Unfortunately, it must be the Structure Detection settings you're using in calibre that are at fault, because using calibre's default settings... I get the same (expected and correct) NCX and inline TOC using calibre or Kindlegen. I definitely don't see any of the footnotes in either TOC.
DiapDealer is offline   Reply With Quote