To make a master index for Cheetah, just head on over to this form. If you really want to know how the whole thing works, read the remainer of the current page.
The master index generation program is a KornShell 93 script that lives at the following pathname:
This script takes one argument, which must be the pathname of a book description file (BDF). The BDF is an ASCII file describing all of the books comprising the master index. Each line of the BDF must have the following format:
directory four-letter-abbreviation "Book Title" ...
For example, the complete BDF for Cheetah docs looks as follows:
By the way, the MM.ksh script ignores comment lines (beginning with a #).
Each directory listed in the BDF must contain a realindx.htm file or a link named realindx.htm. The realindx.htm must contain the index for a book. The MM.ksh builds the master index out of all the realindx.htm files.
I'm not going to describe how MM.ksh works. I'll just mention that whenever we change the WebWorks template that produces an index, the MM.ksh file has to be modified.
I just added a front end to MM.ksh. The front end consists of two other pieces of software:
ORG_FILE_REAL.
ORG_FILE_REAL and places that subset in
ORG_FILE. Then MM.cgi invokes MM.ksh.
If you don't want to use the CGI front end, you can simply invoke MM.ksh from a UNIX shell, by doing the following:
/udir/fscott/BooksInProgress_HTMLandPDF/html by typing:
or
The output of MM.ksh is quite cryptic. Sorry about that. the bottom line is that it will typically build the master index without many complaints unless the BDF is bogus.