30.5.4 Editing an output-specific configuration file

For settings that are specific to an output type or a group of output types, but that apply to all or most of your FrameMaker source documents, Mif2Go maintains user-modifiable output-specific general configuration files in directory %OMSYSHOME%\m2g\local\config. You can customize these files with settings that are appropriate for your particular environment. Table 30-6 lists the output-specific general configuration files you can edit.

Table 30-6 Editable local output-specific configuration files

Category	Output type	Editable configuration file	Ref.
HTML-based Help	All HTML-based Help outputs	local_m2help_config.ini	7
	Eclipse Help	local_m2eclipse31_config.ini local_m2eclipse33_config.ini	12
	Microsoft HTML Help	local_m2htmlhelp_config.ini	9
	JavaHelp	local_m2javahelp_config.ini	11
	OmniHelp	local_m2omnihelp_config.ini	10
	Oracle Help for Java	local_m2oraclehelp_config.ini	11
HTML	All HTML-based outputs	local_m2html_config.ini	13
	XHTML 1.0	local_m2xhtml_config.ini	13
XML	DITA XML	local_m2dita_config.ini	15
	Docbook XML	local_m2docbook_config.ini	17
	Generic XML	local_m2xml_config.ini	14
RTF	WinHelp	local_m2winhelp_config.ini	8
	All RTF-based outputs	local_m2rtf_config.ini	6
Intermediate	ASCII DCL	local_m2dcl_config.ini	38
	FrameMaker MIF	local_m2mif_config.ini	38

Near the top of each configuration file you will find a setting that links that file to an eponymous configuration template in \m2g\system\config that contains settings commonly needed for the output type you selected. Do not edit the referenced templates; they will be overwritten each time you update Mif2Go. Instead, override settings as needed in the editable configuration files.

For example, in local_m2xhtml_config.ini:

[Templates]

; Where the rest of the configuration settings are:

Configs=%omsyshome%\m2g\system\config\m2xhtml_config.ini

Avoid disturbing this setting, or you might break the chain that leads to all the other configuration settings for your conversion project.

---