FrameMaker file(s)

The smallest fragments that yield the problem; see Step D.2.10 in §D.2 Things to check first. No unzipped files.

MIF file(s)

The .mif file(s) Mif2Go creates from the above .fm file(s).

FrameMaker conversion template

If your project uses a conversion template, and the problem is a display problem, include the conversion template.

Book file

If Mif2Go crashed while you were converting a book.

Output file(s)

Whatever output (if any) shows the undesired result.

Log file

Located by default in your project directory; see §5.2 Logging conversion events.

Configuration file(s)

Your project configuration file, plus any chapter-specific configuration file used by the problem FrameMaker file.

Configuration templates

Include all configuration files and templates in every chain that might affect the result, except the distribution templates. However, if you have placed settings in a file in %OMSYSHOME%\m2g\local\config\*, copy those settings to your project configuration file before you create the package.

Macro libraries

If the problem file uses Mif2Go macros located in library files.

CSS file(s)

If your project uses CSS (HTML output only), and the problem is a display problem.

Mif2Go project file

MyDoc.prj, located in the input directory; see §C.1 Locating document and conversion files.

Mif2Go FileID file

mif2go.ini, located in the input directory; see §C.1 Locating document and conversion files.

Help project file

If the problem occurs when you generate one of the following:

• WinHelp: MyDoc.hpj.

• HTML Help: MyDoc.hhp.

• JavaHelp or Oracle Help for Java: MyDoc.hs.

Graphics files

Any external graphics referenced by the problem-file fragment.