When you convert a document, Mif2Go usually places all the files generated in the course of the conversion in the project folder. As a result, the project folder subsequently contains not only newly converted document files, but also configuration files and conversion files that are not part of the converted document. It might even contain output files from a previous conversion, that are no longer needed. See §C .
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 folder 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.
• Delete prior MIF files from the project folder. 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.
- Create a separate folder (or a folder 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 folder (or folder structure) you designate for this purpose.
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 §32.4 .
> 33 Producing deliverable results > 33.1 Understanding Mif2Go pre- and post-processing