On Wednesday 26 July 2006 2:46 pm, Bill Ward wrote: > If you send the TOC to a file and include it on the next troff run, it > works fine. In particular, if you write a file (using the troff stream > feature) on run "n" with each line a call to a macro that writes one > TOC line, then this file can be included on the command line in the > appropriate place in the document in run "n+1" to create the TOC.
Yep. That's basically the way my proposed `toc.tmac' will handle it; it will provide a macro capability to write TOC records to an intermediate stream, in a format which `pdfroff' will recognise, which also can, (and will), be `sourced', to generate the TOC "inline", wherever required in the finished document. I'm also planning a mechanism for segregating the TOC into named "classes", so that one may create `Tables of Contents', `Tables of Figures', etc., or even `Mini-TOCs' for individual chapter heads, and place them as required. > After you work on a document a while, the TOC doesn't change that > much. For the final copy, just make sure you run troff twice. And, since `pdfroff' is a multipass wrapper for `groff', it will take care of that automatically... > Since one can forget to rerun, it's not foolproof, but it is simple. ...so with `pdfroff', it should be foolproof too! :-) Regards, Keith. _______________________________________________ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff
