View Single Post
Old 02-10-2019, 02:12 PM   #10
Trane
Groupie
Trane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensions
 
Posts: 165
Karma: 51147
Join Date: Dec 2016
Device: android tablet
Quote:
Originally Posted by theducks View Post
[...]

What you mini TOC (NCX) does is ONLY point to the Part #

[...]

The readers TOC allows the user to jump to a Part, Then the user has to follow the link to the sub sections (not as elegant as an auto collapsed would have been)
I'm still unclear how this works navigation-wise, so let me say what I think you might be explaining since I am slow on the uptake! The HTML TOC in the front matter would present with the Part#s only, [which would be named after the H1 headings]... then if they clicked on a Part# (or H1-named heading) that would take them to the associated Part# xhtml page.... and *that* page would have the sub-chapters from which they could navigate to what they want?

Am I close??

If I do have that right, can I copy the appropriate code sections from the original (full) TOC into each Part# xhtml page? (e.g. Chapter 1 H1 to the last sub-chapter for that section into "Part1.xhtml" then Chapter 2 section to last sub-chapter into "Part#2.xhtml," etc) or will copying the TOC code screw it up since those pages will not technically be part of a TOC?

Last edited by Trane; 02-10-2019 at 02:49 PM.
Trane is offline   Reply With Quote