30.4 Including chapter-specific configuration files
A chapter-specific configuration file contains settings that apply only to a single chapter file in your FrameMaker document. Each chapter-specific configuration file is named for its FrameMaker chapter file, with extension .ini.
Chapter-specific configuration files do not include a [Templates]Configs setting; Mif2Go inserts each at the very bottom of the configuration chain, below the project configuration file, and processes the chapter configuration first. A chapter configuration file can override anything in the project configuration file except the [Templates]Configs setting.
Table 30-2 shows the chain of configuration files and templates for the title-page file of the Mif2Go User's Guide, for the HTML edition.
Table 30-2 Configuration chain for Mif2Go User's Guide title page
The title-page chapter has its own chapter configuration file (ugmif2go.ini) with settings specific to that chapter alone; those settings override any values for the same settings in the project configuration file (_m2html.ini).
The project configuration file (_m2html.ini) for the HTML edition of the Mif2Go User's Guide references (and overrides settings in) a configuration template named m2gug_htm_document.ini that contains settings common to all HTML and XML output types for the Mif2Go User's Guide.
In turn, m2gug_htm_document.ini references (and overrides settings in) m2gug_document.ini, which contains settings common to all Mif2Go User's Guide projects, including those for RTF output types.
The project configuration file also references the general chain of configuration files, including all local and system configurations, from local_m2htm_config.ini through omsys.ini.
§4.1 Working with Mif2Go configuration files
§33.1 Using a different configuration for selected files
> 30 Working with templates > 30.4 Including chapter-specific configuration files