2.3 Understanding Mif2Go configuration files
To control the conversion process, Mif2Go uses conversion settings read from configuration files. A Mif2Go configuration file is an ASCII text file with extension .ini. A configuration file lists the options and settings that drive a particular conversion. To specify these options and settings, you must edit configuration files with a text editor, outside of FrameMaker; see §4 Editing configuration files.
The configuration file you work with most will most likely be your project configuration file, located in the project directory for your Mif2Go conversion project.
As you work with Mif2Go, you might need any or all of the following additional configuration files, depending on the type and complexity of your projects:
Configuration files Mif2Go creates for you
Configuration files from previous conversions
Configuration files for individual chapters
Configuration template files hold settings that rarely change from project to project. Mif2Go maintains a hierarchy of configuration template files chained together; the chain is referenced from your project configuration file. Also, you can create one or more configuration templates of your own, or direct Mif2Go to use an existing configuration file as a template; see §30 Working with templates.
Configuration files Mif2Go creates for you
For each new conversion project, Mif2Go creates a project configuration file for you, if a file of the same name is not already present in the project directory. Table 30-1 lists the names of these starting configuration files. Each name begins with an underscore, to help you find the file in the project directory.
If you put a project configuration file in the project directory before you run Mif2Go via FrameMaker, Mif2Go cannot make certain initial settings for you; see §1.5 How Mif2Go works. For this reason it is best to allow Mif2Go to create a new project configuration file when you start a new conversion project.
Configuration files from previous conversions
If you already have configuration files with the right settings for a particular document (perhaps a configuration file from a previous installation of Mif2Go or mif2rtf), you can place that configuration file in the project directory and Mif2Go will use it.
Note: If you had Mif2Go version 3.3 on your system, each of your existing Mif2Go projects already has, in the project directory, a configuration file named either mif2rtf.ini (for RTF output) or mif2htm.ini (for HTML/XML output). Mif2Go version 4.0 uses those files if they are present, even though they do not have the newer file names.
Configuration files for individual chapters
If you are converting a FrameMaker book, in special cases you might also need individual configuration files for certain chapter files; see §33.1 Using a different configuration for selected files.
For each FrameMaker book or single-file document, Mif2Go creates a FileID (“file identifier”) file in the same directory as your FrameMaker book or document, unless this file is already present. The FileID file is named mif2go.ini; see §C.2.1 Conversion files created during set-up.
> 2 Planning a conversion project > 2.3 Understanding Mif2Go configuration files