7.3.1 Understanding how Mif2Go produces contents and index
How Mif2Go generates contents (and index, for HTML-based Help) depends on which of the following you are converting:
Chapter of a previously converted book
When you convert a FrameMaker book, Mif2Go produces the following:
*.btc, a separate contents data file for each chapter file
*.bhc, a separate contents data file for each chapter file
*.bhk, a separate index data file for each chapter file
MyDoc.lst, a file that contains a list of the chapter files in book order
After all chapters are processed, Mif2Go combines entries from the chapter data files to create the final contents (and for HTML-based Help, the final index).
For HTML-based Help, Mif2Go recreates list file MyDoc.lst each time you run a conversion from the book file. Mif2Go uses MyDoc.lst to merge data files and produce the final contents and index files. See also §7.3.4.2 Maintaining the list file when the book file changes.
Chapter of a previously converted book
If the book file is open in FrameMaker when you convert a single chapter, Mif2Go produces from the chapter a contents data file (and for HTML-based Help, an index data file); then merges these data files with any from other chapters to regenerate the final contents (and index).
When you convert a document that consists only of a single FrameMaker file, Mif2Go produces final contents (and index) directly, omitting intermediate data files.
> 7 Producing on-line Help > 7.3 Producing contents and index for Help systems > 7.3.1 Understanding how Mif2Go produces contents and index