I maintain a user manual for diving software (subsurface-divelog.org). The 
html manual is becoming quite large in size and also in terms of the number 
of headings. Consequently the toc is becoming very long and, consequently, 
less useful. We believe that decreasing the number of heading levels in the 
toc would be counterproductive. But I need to do something to make the text 
more navigable by the first-time user. There are  a few options, but all of 
these mean that the toc should be more interactive. I am acutely aware that 
asciidoc is not meant to generate dynamic in-text features but is in 
principle comparable to a layout language such as latex. But I am trying to 
find out what is still possible within the asciidoc environment.

1) Using a .toc2 instruction, the scrollable toc could be placed on the 
left. However two problems: a) the width of the frame within the toc sits 
is rather narrow, at least for heading that are more than just two or three 
words, the width of the frame is, as far as i am aware not user-changeable. 
Consequently a specific heading wraps around several times, making the text 
less readable. can one control the font size in the .toc2 implementation at 
all to try and reduce the amount of wrapping of individual toc items?

2) Using the .toc instruction, the toc is placed within the main text. 
Ideally une would only list the chapter headings in the toc, but with each 
chapter heading being expandable to see all the headings within that 
chapter. But I have not seen that asciidoc has such a feature.

Any suggestions on how to deal with long toc's would be highly appreciated.
Kind regards,
willem ferguson



-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.

Reply via email to