### 38.2.1 Understanding how MIF files are generated

The Mif2Go MIF output type was designed to work with CVS revision-management software, to store full FrameMaker books. Special features make it possible to seamlessly reload the stored files into FrameMaker:

• MIF output files retain the same paths as the .fm files, rather than receiving new paths relative to the new location. This is different from FrameMaker File > Save As... behavior, which alters paths; a feature that can make reloading MIF files a nightmare.

• MIF output files are named with an .fm extension, so they load from the MIF (or native FrameMaker) book file.

• You can use a FrameMaker conversion template (see §2.4 Importing formats from a conversion template) to alter properties such as format definitions in the MIF output files, without affecting the original FrameMaker files.

Mif2Go first creates the MIF files in the same directory with your FrameMaker document files, using temporary file extensions; then moves the MIF files to the project directory, and changes the file extensions to whatever you specify. This two-step process accomplishes the following:

• Prevents FrameMaker from converting relative references (such as paths to external graphics files) to absolute references.

• Prevents FrameMaker from creating .backup files in the project directory. Any previous copies in the project directory are overwritten by the move.

Mif2Go does not support FrameMaker books that contain chapter files in other directories. MIF files are always written to a single outp[ut directory.

| 38.2 Generating MIF output |  | 38.2.2 Setting up a FrameMaker MIF project |