2.3 Working with Mif2Go configuration files
To control the conversion process, Mif2Go uses conversion settings in a configuration file. A Mif2Go configuration file is an ASCII text file with extension .ini that lists the options and settings that drive a particular conversion. You can edit a configuration file outside of Mif2Go to specify these settings; and for some conversions you must do so.
A configuration file contains several sections, and each section contains a number of settings. Each setting in a configuration file specifies a single Mif2Go option when you convert a document.
The configuration file you work with most is the project configuration file, located in the project folder for your Mif2Go conversion project. You can specify another location for configuration template files that hold settings that rarely change from project to project. As you work with Mif2Go, you might need any or all of the following 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
Sample library file for macros
If you have created one or more configuration templates, or if you direct Mif2Go to use an existing configuration file as a template, the template files are located wherever you tell Mif2Go you put them; see §4.5 Using Mif2Go configuration templates.
Configuration files Mif2Go creates for you
Mif2Go creates one or more of the following configuration files for you, if they are not already present:
• In the project folder (where you tell Mif2Go to place converted document files):
![[spacer]](1p.gif){kind=small}
Conversion settings for RTF output (Word, WordPerfect, WinHelp) |
|
Conversion settings for HTML output (HTML, XHTML, XML, HTML-based Help) |
• In the input folder (where your FrameMaker document is located):
If you put a configuration file in the project folder 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 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 folder and Mif2Go will use it.
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 §31.1 Using a different configuration for selected files.
Sample library file for macros
The folder where you installed Mif2Go contains a sample macro library file:
To use m2hmacro.ini, you must copy it to the project folder. You can also create your own macro library files; see §27.1.7 Including macro definitions in a library.
For converting to RTF, the Mif2Go plug-in allows you to specify most settings via GUI, from inside FrameMaker.
For converting to HTML, you must use a text editor (such as Notepad) to specify most settings. For converting to any output type, you can use a text editor to change settings in a configuration file to customize it for your conversion project. The Mif2Go plug-in opens a configuration file for you in Notepad, from within FrameMaker, so you can edit conversion settings without leaving FrameMaker.
To learn how to specify settings in a configuration file, see §4 Setting configuration options.
> 2 Planning a conversion project > 2.3 Working with Mif2Go configuration files