@Tex - yes I used proper H1, etc headings throughout and it goes as deep as H5 in places. The TOC displays beautifully, it's just that it's very long and I expected e-readers to collapse it by default to H1 unless clicked on. Two pages of H1 headings is doable (might even be one page collapsed), but 10 pages of TOC...
Quote:
Originally Posted by theducks
If you have coded the NCX with NESTED TOC items, then it is the VIEWER on the device that controls the display (if collapsed)
|
If by 'nested' you mean using the headings (H1, H2, etc) then yes... Which is why I expected the TOC pages to be auto-collapsed...
Quote:
The other option is to Make the NCX, a 'quick TOC' (to keep Amazon et al happy
Then have one of those item, the full (HTML) TOC or Section (HTML)TOC < These can not be marked as TOC with semantics
|
I wish I was smart enough to know exactly what you mean, and then how to do that quickly... or even slowly.
This book has been happily kicking my you-know-what every day for the past 6 years... even now at the very end it's not done with me yet.
Aside from being too tired this late [after working 30hrs on it the last 2 days] to get my brain to wrap around what you're saying, my first upload will be to Amazon and I don't own a Kindle so can't check it if I screw it up royally... unless I guess the Kindle Previewer (done beforehand) would throw up on me if I did something wrong...
@Doitsu - it's an epub2. I started it long before I knew there WAS an epub3. I did install the Sigil Plugin to convert to epub3 but am trying to finish it as it is for now.
Thanks guys for all your help... will read this again in A.M. and hope it translates when my brain has had some rest!