### D.2.6 Check for file corruption

A slightly corrupted FrameMaker file might cause hard-to-trace problems with Mif2Go. To rule out this possibility, try cleaning out any corruption by saving the offending file as MIF and replacing the binary version with the MIF version. Mif2Go can do this for you (even in the evaluation version), and report the results in the FrameMaker console window.

Clean a single file

To clean a FrameMaker binary file: with the file open and active, on the FrameMaker File menu choose Wash Via MIF. Mif2Go does the following:

1. Saves the file as MIF with extension .tmb (for Temporary MIF Backup), to avoid conflict with any existing MIF file of the same name.

2. Closes the file without saving.

3. Opens the .tmb MIF file.

4. Saves the .tmb MIF file as .fm, overwriting the original file.

5. Deletes the .tmb MIF file.

Note: FrameMaker version 11 seems to get as far as Step 3 and then stop; and fails to process chapter files when run on a book.

Clean all files in a book

To clean all files in a FrameMaker book: with the book file active, hold down the Shift key, and on the FrameMaker File menu choose Wash All Files in Book Via MIF. Mif2Go processes each file in the book as described for Wash Via MIF, afterward closing any file that was not open in the first place.

Back-up copies are saved first

If you have set up FrameMaker to save back-up files, when you “wash” files via MIF, Mif2Go saves the previous .fm or .book file as filename.backup.fm or filename.backup.book.

File(s) decontaminated, and the problem still exists? Next: Check for broken links (HTML or XML output).

| D.2.5 Check path names, file names, and drive location |  | D.2.7 Check for broken links (HTML or XML output) |