33.12 Postprocessing separately from converting
If you have already converted a document and the results are still in the output folder, you can have Mif2Go carry out postprocessing steps without going through the entire conversion again. These steps can include:
• compiling for WinHelp or HTML Help
• running a search indexer and creating a JAR file for JavaHelp or Oracle Help
• any of the automation options available when you set WrapAndShip=Yes (see §33.2 Activating and logging production of deliverables).
To postprocess conversion results independently of conversion:
; OnlyAuto = No (default) or Yes (run only automation commands,
; rather than the full conversion)
When OnlyAuto=Yes, Mif2Go processes options specified in the [Automation] section of the configuration file, without first performing any document conversion.
System commands (see §32.4.2 Executing system commands before and after conversion) are not run when OnlyAuto=Yes. |
OnlyAuto=Yes takes effect only when at least one of the following is true:
• A value is specified for FTSCommand.
When OnlyAuto=No, Mif2Go runs the conversion before processing options specified in the [Automation] section.
Compilation is included for WinHelp, HTML Help
If the output type is WinHelp or HTML Help and you set CompileHelp=Yes (or you check Compile Help on the Export dialog), Mif2Go runs the appropriate compiler before placing the deliverable(s) in a shipping folder; see §33.8 Gathering and compiling Help-system files.
Indexing search terms is included for JavaHelp, Oracle Help
If the output type is JavaHelp or Oracle Help and you specify a value for FTSCommand in the configuration file, Mif2Go runs the designated indexer before archiving the deliverables and placing them in a shipping folder; see §10.4 Providing full-text search for JavaHelp / Oracle Help.
> 33 Producing deliverable results > 33.12 Postprocessing separately from converting