### 38.2.6 Specifying file extensions for MIF output

You can specify file extensions separately for the book file and for all other files; the default in either case is to retain the original FrameMaker file extension. For example:

[Setup]

; Settings for FrameMIF projects

; MakeBookMIF = Yes (default, make MIF of book file too) or No

MakeBookMIF=Yes

; OrigExtForMIF = Yes (default, use original FM file extensions) or No

OrigExtForMIF=No

; MIFBookSuffix = suffix to use for book file MIF, default ".mif"

MIFBookSuffix=.book

; MIFSuffix = suffix to use for MIF files, default ".mif"

MIFSuffix=.fm

If you leave file extensions alone, all the files in your document are saved with default extension .mif. You can specify different extensions, depending on the reason for saving your document as MIF.

If you specify OrigExtForMIF=Yes, Mif2Go saves all the files in your document in MIF format, but with their original FrameMaker file extensions: one extension for the book file (provided you also specify MakeBookMIF=Yes), and one for the files contained in the book.

If you specify OrigExtForMIF=No, you can specify one extension for the book file (provided you also specify MakeBookMIF=Yes), and another extension for the files contained in the book.

Why would you want MIF files to have FrameMaker extensions? Suppose you are saving as MIF so you can store your original document in a revision-control system such as CVS. You cannot just check binaries into CVS if you ever want to compare revisions using the CVS diff function, which is a huge benefit. You must store files in an ASCII format, so that CVS can provide metadata. You have these choices:

• Name the files *.mif, and rename them one by one every time you copy them into or out of the archive, from or to your working directory.

• Keep the original FrameMaker file extensions even though the files are in MIF format, so you can copy all the files to your working directory and open them in FrameMaker without changing the extensions.

You might want to specify different extensions if you are passing FrameMaker files back and forth with someone who is using FrameMaker on a different system with different file-naming conventions.

| 38.2.5 Saving FrameMaker 9 files as FrameMaker 7 MIF |  | 38.3 Converting to ASCII DCL |