44.2 Activating and logging production of deliverables

To have DITA2Go assemble files and optionally archive deliverables, 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, DITA2Go acts on all options in the [Automation] section of the configuration file. To have DITA2Go place deliverables in a shipping directory, you must also specify a value for ArchiveCommand; see §44.11 Archiving deliverables.

When WrapAndShip=No (the default), DITA2Go ignores most [Automation] settings, unless you have DITA2Go run a compiler or indexer for a Help system (see §44.10 Gathering and processing Help-system files). Table 44-4 shows which [Automation] settings are activated when DITA2Go 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 §44.7.1 Copying referenced graphics to a distribution directory.

Log the actions taken

To have DITA2Go 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 DITA2Go executes to carry out an automation option is recorded in the DITA2Go log file, provided logging is enabled; see §4.2 Logging conversion events. LogAuto takes effect only when WrapAndShip=Yes.

Previous Topic:  44.1 Understanding DITA2Go pre- and post-processing

Next Topic:  44.3 Understanding path values for deliverables

Parent Topic:  44. Producing deliverable results

Sibling Topics:

44.1 Understanding DITA2Go pre- and post-processing

44.3 Understanding path values for deliverables

44.4 Clearing out old files before converting

44.5 Gathering additional files before converting

44.6 Assembling files for distribution

44.7 Placing graphics files for distribution

44.8 Placing CSS or XSL files for assembly

44.9 Gathering files for an HTML project: an example

44.10 Gathering and processing Help-system files

44.11 Archiving deliverables

44.12 Placing deliverables in a shipping directory

44.13 Postprocessing separately from converting