Thread: Visible Table of Contents
View Single Post
Old 06-27-2015, 10:03 PM   #14
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,820
Karma: 146918083
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by arjaybe View Post
I'm still getting the hang of it. I run an ODT file through Calibre, and it makes an NCX TOC, right? Then I can tell Calibre to create an inline TOC if I want. (Just showing off that I learned what they're called.-) So far I haven't figured out how to tell the inline one where to go, though. My book has chapter titles, so it might look all right inline.
You are missing a very important step. After you convert the ODT file to ePub, you MUST have a look at the code. You MUST have a look inside the ePub. You MUST clean up anything that needs to be cleaned up. You MUST make sure the code in your ePub is as clean as can be made. Only then can you go to the next step of converting the ePub into a Kindle eBook.
JSWolf is offline   Reply With Quote