Omni Systems, Inc. |  | Mif2Go User's Guide, Version 55 |  |  |  |  |

> 35 Producing deliverable results > 35.1 Understanding Mif2Go pre- and post-processing

## 35.1 Understanding Mif2Go pre- and post-processing

When you convert a document, Mif2Go usually places all the files generated in the course of the conversion in the project directory. As a result, the project directory subsequently contains not only newly converted document files, but also configuration files and generated conversion files that are not part of the converted document. It might even contain obsolete output files from a previous conversion. See §C Document and conversion files.

For many output types, when you prepare a converted document for distribution you need to separate the wheat from the chaff. It is a good idea to copy the converted files, along with any other files that must be distributed with the output, to a directory where they can be accessed by others, or easily compiled or archived for distribution. In many cases Mif2Go can handle the compiling or archiving for you.

Before generating output files, Mif2Go can do the following:

• Delete prior MIF files from the project directory. If you have just edited and regenerated your FrameMaker documents, you do not need the MIF files from a prior conversion. Deleting them instead of overwriting them avoids creating FrameMaker back-up files, and speeds up conversion.

• Delete prior output and conversion files from the project directory. Best not to leave orphaned and obsolete files where they can be swept up into a new distribution.

• Copy needed files into the project directory, such as configuration files and CSS files that you keep in a central, safe location.

After generating output files, Mif2Go can do any or all of the following:

• Assemble files for distribution:

– Create a separate directory (or a directory structure) where results of a conversion, along with ancillary files such as graphics, can be assembled for compiling, archiving, distribution, or use. Or, use an existing directory (or directory structure) you designate for this purpose.

– Gather necessary files into the wrap directory (and subdirectories, if appropriate).

• Compile or archive deliverables, or both:

– Create a separate “shipping” directory for compiled or archived results, or use an existing directory you designate for this purpose.

– Run a full-text-search indexing program (JavaHelp; putatively, Oracle Help for Java).

– Run a compiler (WinHelp or HTML Help).

– Run an archiving program, and place the results in the shipping directory.

• Log any operating-system commands executed in the course of assembling, compiling, and archiving.

If your workflow is more involved than this, you can specify other pre- and post-processing custom steps and arrange for interactive prompts, via system commands; see §34 Automating Mif2Go conversions.

> 35 Producing deliverable results > 35.1 Understanding Mif2Go pre- and post-processing

| Mif2Go User's Guide: 35 Producing deliverable results |  | Mif2Go User's Guide: 35.2 Activating and logging production of deliverables |