|  |     To generate a table of contents for each chapter, you can process
    each chapter separately in an element build and use the /contents
    qualifier. For example, to do an element build for a chapter 
    named FIRST_CHAP.SDML, which is part of a book with a profile 
    called GREAT_BOOK.SDML, you use the command:
    
    DOCU FIRST_CHAP doctype destination /profile=great_book /content
                                                               
    Before you can do an element build, you must first have done
    a complete bookbuild, so that you have a cross-reference file for
    the whole book.
    
    You cannot generate a table of contents for the whole book that
    is less detailed than the seperate chapters. All your chapter headings
    are included automatically in any table of contents.
    
    
    
 | 
|  | Re: .2
Will your method create a TOC that starts the chapter, with the page accounted
for? That is, will the TOC for Chapter 1 end up on page 1-1? I think that's what
.1 is looking for. I'd also like to create such a style, with a detailed TOC for
each chapter and a simple TOC for the book.    
    
 | 
|  | There is a very messy way to do this.
1. Process a chapter, using /contents and /keep=tex.
2. Cut and paste the chapter_contents.tex file into the chapter.tex
   file. You have to do some housecleaning, such as deleting the
   extra \begintexinput command, and the \begintoc and \endtoc commands. 
   The _contents.tex should come after the chapter heading. For the
   moment, the page numbers will be wrong.
3. Repeat step 1 and print out your new contents file. This has the
   correct page numbers.
4. Edit the chapter.tex file from step 2. You have to change the page
   numbers in the contents you inserted, to match the contents from step 3.
I tried this method, and it works (at least in one local doctype). Of course,
to get a less detailed contents for the book, you'd have to delete the
subentries from the book_contents.tex file.
 |