A configuration file is a plain ASCII text file, with file extension .ini. When Mif2Go creates a configuration file for you, Mif2Go writes a couple of header lines as comments. However, header text is not required.
A configuration file contains a series of sections. Each section consists of a section name in square brackets, followed by a list of settings of the form Key=Value or Key=Command, each on a separate line; and possibly by one or more comments:
Section names must be unique. If you use the same section name twice in your configuration file, only the first section is processed. Otherwise, order of sections does not matter, except for macro sections (see §18.104.22.168 ).
Each Key= setting in a given section must be the only setting for that key in that section. A common error is to add a setting to a section that already has a setting for that key. For example, any repeated lines assigning additional values to the same format name are ignored; only the first line is processed. Instead, place any additional values on the same line as the first, separated by spaces.
Configuration files contain two kinds of sections: those with fixed keys (key names predefined by Mif2Go) and those with variable keys. For example, sections such as [HTMLOptions] and [WordOptions] are for settings with fixed key names; sections such as [HtmlStyles] and [HelpStyles] are for settings with key names you specify, typically names of FrameMaker formats.
In a fixed-key section, the order of settings does not matter. Order is important only in sections where you can use variable keys, and then only if you use wildcards in key names (see §4.1.6 ).
Often the variable-key names you specify are names of formats in your FrameMaker document, such as paragraph, character, or table formats. Make sure each format you use for a key name actually appears in the appropriate catalog in FrameMaker; Mif2Go cannot process formats that are not in a FrameMaker catalog.
Some variable-key sections allow multiple values for each key: sections such as [HtmlStyles], [WordStyles], and [HelpStyles], where you can assign multiple properties to each FrameMaker format. Use spaces between values.
Comparisons of key names are caseless, unless you turn on case sensitivity; see §4.2.8 . (However, when you override a configuration setting with a configuration variable, the key name is case sensitive; see §31.2.4 .)
• "?" and "*" are treated as wildcards, unless you turn off wildcard usage; see §4.2.8 . (However, when you override a configuration setting with a configuration variable, Mif2Go does not recognize wildcards in the key name; see §31.2.4 .)
• Spaces and tabs before the Key and before the equal sign are ignored, unless [Options]SpacelessMatch=No, in which case those before the Key are not ignored (see §4.2.8 ).
Lines that start with a semicolon ";" are comments. For a line to be treated as a comment, the semicolon must be the first character on the line (no leading blanks or tabs). Mif2Go pays no attention to comment lines; you can use them to add your own notes. However, do not try to "comment out" a section by inserting a ";" in front of the section name; all settings that follow such a line, up to the next line that starts with a "[", would be added to the settings for the preceding section. Comments are never required.
You can specify as many unique settings as you like in a section. However, on Windows 95/98 and Windows ME systems, you are limited to 32KB worth of settings per section. This limitation does not exist on Windows NT, Windows 2000, or Windows XP.