To specify which files DITA2Go should delete from the project directory before conversion:
[Automation] WrapAndShip=Yes ; EmptyOutputFiles = list of files to delete, separated by spaces, ; wildcards allowed but not paths, no spaces within an item EmptyOutputFiles = *.htm *.ref *.grx
If you do not include a setting for EmptyOutputFiles, depending on the value of EmptyOutputDir (see §44.4.1 Specifying when to delete old files from the project directory), by default DITA2Go deletes the following old files from the project directory before conversion:
*.htm *.html *.ref *.grx |
|
*.xml *.ref *.grx |
|
*.dita *.ditamap *.bookmap .ref .grx |
|
*.rtf *.grx |
Note: If you list either *.dcl or *.dcb for EmptyOutputFiles, DITA2Go ignores EmptyOutputDir and logs a warning. To delete .dcl and .dcb files, see §4.1.9 Reusing or discarding ASCII DCL files.
Use wildcards; do not use paths
The file specifications you assign to EmptyOutputFiles must be separated by spaces, and no spaces are allowed within a file specification. You can use wildcards in file specifications, but you cannot include paths.
Warning! Do not specify *.* or *.ini, or you will lose your configuration file(s); and for Help systems, you might lose a great deal more.
Depending on the value of EmptyOutputDir (see §44.4.1 Specifying when to delete old files from the project directory), DITA2Go deletes the specified files before conversion begins.
Files get deleted on compiling and indexing, also
Note: EmptyOutputFiles takes effect not only when WrapAndShip=Yes, but also when one of the following is true for the output type specified:
HTML Help: [Automation]CompileHelp=Yes
WinHelp: [Automation]CompileHelp=Yes
JavaHelp: [JavaHelpOptions]FTSCommand=path/to/indexer
Oracle Help: [OracleHelpOptions]FTSCommand=path/to/indexer
See §44.10 Gathering and processing Help-system files.
§4.1.9 Reusing or discarding ASCII DCL files
§44.4.1 Specifying when to delete old files from the project directory
§44.4.3 Understanding when not to delete .ref and .htm files