Once you have created a conversion project with the DITA2Go Project Manager (see §2.1 Creating a DITA2Go conversion project), you can use the DITA2Go Project Manager to execute the conversion. However, you can also run DITA2Go from a command line; see §2.7 Converting documents from the command line.
To operate DITA2Go with the Project Manager:
Under Automation Options, specify any post-conversion steps you need for the current run, or turn off those you do not need. With appropriate settings in place (see §1.3.7 Establish system-wide configuration settings), DITA2Go can produce a ready-to-distribute archive of your completed conversion, and place the archive in the shipping directory.
Under Advanced Options, you can choose whether to involve creation or use of an intermediate format: ASCII DCL. Your choice has the following effect:
ASCII DCL files, if any, are converted to the output format. |
|
DITA XML files are converted first to ASCII DCL, then the ASCII DCL files are converted to the output format. |
When you run normally, with Use ASCII DCL set to Both or Neither, you get the full automation effect: both Start and End automation tasks. If instead you run with Use ASCII DCL set to Output, you get only the Start automation tasks, because the files processed by End do not exist yet. If Use ASCII DCL is set to Source, you get only the End automation tasks, because the files removed by Start are needed for your current process.
Also, you can choose to run only automation tasks.
Note: If you choose Run only automation tasks, you must have the bookmap or ditamap in place in the output directory, even though it is not needed for these tasks.
You can specify options to display a console window while the conversion is running, and a log file when the conversion is complete. See §2.6 Customizing the DITA2Go Project Manager.