Chapter

The chapters contain the building blocks of the document. Here the author expresses his thoughts and shows his results pertaining a specific topic. Depending on the complexity of the chapter's contents, the structure of such a chapter varies considerably.

As a minimum a chapter contains following files and directories:

• Makefile contains the rules on how to generate the chapter's result files from its source files and how to remove all intermediate junk files which are created in the process.
• Fig is a directory which stores the local result (usually figure) files.
• paper.tex is the author's text file. The L^ATEXlanguage allows the author to integrate push buttons and figures in his text (cite SEPHELP textour, referencing).
• foo.c is a possible source code file which is needed for generating the local result files but which is not shared with other chapters.

If the chapter contains a wealth of independent figures each with its own local source and executable files, it is beneficial to separate all rules and sources pertaining a single figure into small, manageable, separate subdirectories. The subdirectory's Makefile nevertheless deposits the final figure in the chapter's top figure directory Fig. The top Makefile lists all figures created in all of its subdirectories in its RESULT. Its clean rule has to descend into each subdirectory. The script makemake automatically generates such a top directory Makefile from its subdirectory Makefiles.

Some issues about how to organize a complex and interdependent document remain unresolved. For further illustration I suggest you have a close look at Claerbout's organization in his most recent books (cite TDF BEI).