33.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 the configuration file:
; WrapAndShip = No (default) or Yes (use WrapPath, ArchiveCommand,
; ShipPath, CopyGraphicsFrom, and CopyCssFrom)
When WrapAndShip=Yes, Mif2Go acts on all options in the [Automation] section of the configuration file.
When WrapAndShip=No (the default), Mif2Go ignores [Automation] settings, unless you have Mif2Go run a compiler or indexer for a Help system (see §33.8 Gathering and compiling Help-system files). Table 33-4 shows which [Automation] settings are activated when Mif2Go runs a compiler or indexer for a Help system.
To have Mif2Go log the commands executed when WrapAndShip=Yes:
; LogAuto=No (default) or Yes (log all automation commands to
; the FrameMaker console window)
When LogAuto=Yes, each operating-system command Mif2Go executes to carry out an automation option is recorded in the FrameMaker console window. Only the commands themselves are recorded; results and error messages are not included. LogAuto takes effect only when WrapAndShip=Yes.
If you plan to use runfm for unattended production runs (see §34 Converting via runfm), while you work out the process you might want to log additional diagnostic messages to the FrameMaker console window:
; RunfmDiagnostics = No (default) or Yes (include more diagnostic
; messages in the Frame console file when running from runfm)
RunfmDiagnostics takes effect only when WrapAndShip=Yes. When you use runfm, you can also capture FrameMaker console messages in a log file. See:
§34.5.1 Increasing console diagnostics: runfm -diag option
§34.5.2 Capturing console diagnostics: runfm -log option.
> 33 Producing deliverable results > 33.2 Activating and logging production of deliverables