## 35.2 Activating and logging production of deliverables

To have Mif2Go assemble files and optionally archive deliverables, either check Wrap and Ship on the Export dialog, or specify the following option in your project configuration file:

[Automation]

; WrapAndShip = No (default) or Yes (use WrapPath, ArchiveCommand,

; ShipPath, CopyGraphicsFrom, and CopyCssFrom)

WrapAndShip=Yes

When WrapAndShip=Yes, Mif2Go acts on all options in the [Automation] section of the configuration file. To have Mif2Go place deliverables in a shipping directory, you must also specify a value for ArchiveCommand; see §35.11 Archiving deliverables.

When WrapAndShip=No (the default), Mif2Go ignores most [Automation] settings, unless you have Mif2Go run a compiler or indexer for a Help system (see §35.10 Gathering and processing Help-system files). Table 35-4 shows which [Automation] settings are activated when Mif2Go runs a compiler or indexer for a Help system.

Note: If you specify CopyOriginalGraphics=Yes, graphics are copied regardless of the value of WrapAndShip; see §35.7.1 Copying referenced graphics to a distribution directory.

Log the actions taken

To have Mif2Go log the commands executed when WrapAndShip=Yes:

[Automation]

WrapAndShip=Yes

; LogAuto=No (default) or Yes (log all automation commands)

LogAuto=Yes

When LogAuto=Yes, each command Mif2Go executes to carry out an automation option is recorded in the Mif2Go log file, provided logging is enabled; see §5.2 Logging conversion events. LogAuto takes effect only when WrapAndShip=Yes.

Log runfm diagnostic messages

If you plan to use runfm for unattended production runs (see §36 Converting via runfm), while you work out the process you might want to log additional diagnostic messages to the FrameMaker console window:

[Automation]

; RunfmDiagnostics = No (default) or Yes (include more diagnostic

; messages in the Frame console file when running from runfm)

RunfmDiagnostics=Yes

RunfmDiagnostics takes effect only when WrapAndShip=Yes. When you use runfm, you can also capture FrameMaker console messages in a log file. See:

§36.5.1 Increasing console diagnostics: runfm -diag option

§36.5.2 Capturing console diagnostics: runfm -log option.

| 35.1 Understanding Mif2Go pre- and post-processing |  | 35.3 Understanding path values for deliverables |