At run time Mif2Go builds a configuration for each FrameMaker file in your project, starting with the most specific settings: those in the chapter.ini configuration file, if there is one. Next come settings in the project configuration file, mif2rtf.ini or mif2htm.ini.
Next, if chapter.ini includes a value for [FDK]ConfigTemplate, (see §4.5 ), settings in the referenced configuration template (and any additional templates chained to it) are applied. If chapter.ini does not reference a configuration template, next come settings in any configuration template referenced by the project configuration file; then on up the chain from that template. shows the precedence of settings in configuration files and templates.
A chain of configuration templates, if any, is applied to chapter.fm either from chapter.ini (preferentially) or from the project configuration file, but not from both. In either case, settings from the templates are applied after settings from the project configuration file, which are applied after settings from the chapter configuration file. For the same setting with different values in different configuration files or templates, the value in the most specific file takes precedence. See §32.2.3 .
> 31 Overriding configuration settings > 31.1 Using a different configuration for selected files > 31.1.2 Understanding precedence of configuration settings