From: Andreas K. <and...@ac...> - 2007-05-22 21:09:06
|
> It's maintained by hand as a TMML master document. > > If so, we could maybe put the category information into the manpages, as > > proper markup using a new 'category' command, or as temp. hack using > > 'comment' with special contents. > In my experience, this usually isn't the best way to go -- > it's easier to maintain the TOC if the overall structure > is stored in a single file. (For example: splitting up > subsections when they get too big, making sure that "intro" > manpages appear first in each subsection, that sort of thing.) > > The main drawback is that when new manpages appear, someone > has to determine where they fit in the TOC by hand. I was > hoping that you were already maintaining this as a doctools::toc > document. I had forgotten that we havethis format. Well, at least it did not come to mind when I was thinking about this ... So, no, currently I do not have such a document. However I see nothing against writing such a toc document and testing if that can be made to work. Can you send me the TMML master ? And maybe some of your scripts so that I can see how it fits into your workflow ? Another thing to try is to extend SAK to tell us which manpages, if any, are not listed in the TOC yet. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com Tel: +1 778-786-1122 |