32.2.1 Deciding what to include in a configuration template

A configuration template should include settings and values that you normally use in most or all projects for a given type of output. The settings in the template file apply to any configuration file that references that template, reducing the need to add the same settings to every project configuration file.

Books that share a FrameMaker template probably can also share the same configuration template. You might want different configuration templates for TOC, IX, and regular chapters. Configuration templates for different books might all reference a company-wide configuration template that specifies logos and other boilerplate items.

Project overrides template

If a setting has a value in the template file that is different from its value in the project configuration file, the value in the project configuration file takes precedence, allowing you to override the template when necessary; see §31.1.2 Understanding precedence of configuration settings.

Define macros elsewhere

Do not include macro definitions in a configuration template; keep macro definitions in a separate library file. See §27.1.7 Including macro definitions in a library.

Specify run-time values elsewhere

Do not include [UserVars] or [UserVarPrompts] in a configuration template; these two sections must be in your project configuration file. See §32.4.3 Supplying run-time values for user variables.

Specify condition settings elsewhere

Do not include [ConditionsShown] in a configuration template; this section must be in your project configuration file. See §4.7.1 Applying condition Show/Hide settings.

Some settings are duplicated

Although the settings in Table 32-1 can be included in a configuration template, some will end up in the project configuration file anyway; either because Mif2Go originates them, or because their values can be changed at run time via Choose Project dialog or Export dialog (or by Mif2Go). If you remove one of these settings from the project configuration file, Mif2Go will put it back in, at the end of the section where it belongs. If the section itself is missing, Mif2Go places the section and the setting at the very end of the project configuration file.

Table 32-1 Configuration options determined at run time

Configuration section	Option	Reference
Automation	CompileHelp	33.8
	WrapAndShip	33.2
FDK	DCLSuffix	4.2.2
	DeleteMIF	4.2.3
	HTMLSuffix	4.2.2
	IDFileName	4.4.4.1
	MIFBookSuffix	4.2.2
	MIFSuffix	4.2.2
	PluginVersion	D.2.7
	PrjFileName	C.3
	UseExistingDCL	4.2.4
	UseExistingMIF	4.2.3
	WordPerfectSuffix	4.2.2
	WordSuffix	4.2.2
	WriteAllGraphics	4.10.2.1
	WriteEquations	4.10.2.1
	XMLSuffix	4.2.2
Graphics	UseGraphicPreviews	4.10.2.2
	UseOriginalGraphicNames	4.10.2.3
HelpOptions	MakeCombinedCnt	7.1.6

---

> 32 Automating Mif2Go conversions > 32.2 Importing settings from configuration templates > 32.2.1 Deciding what to include in a configuration template