##### 20.3.6.5 Manually copying and deleting output files

To get rid of any orphaned HTML files left over from a previous conversion run, for a stand-alone project (no links to other projects) it is best to delete all HTML output files before each full conversion, then copy new HTML output files to the appropriate compilation directory after conversion. For large projects, deleting and then recreating the help\html subdirectory is noticeably faster than deleting HTML files one by one.

Do not delete until after all conversions

If HTML output files contain cross references to another project (as in a merge situation), those cross references would be broken if you were to delete HTML files from the project directory, because DITA2Go would not be able to update the missing files. In that situation, update all projects that need updating before you copy HTML files from the project directory to the compilation directory; and delete HTML files from the project directory only when you start a full conversion of every project involved.

Previous Topic: 20.3.6.4 Specifying a path for search-index links

Next Topic: 20.3.7 Configuring the helpset file

Parent Topic: 20.3.6 Creating a directory structure for JavaHelp / Oracle Help

Sibling Topics:

20.3.6.1 Understanding the JavaHelp / Oracle Help directory structure

20.3.6.2 Letting DITA2Go set up the directory structure and copy files

20.3.6.3 Locating graphics files for JavaHelp and Oracle Help

20.3.6.4 Specifying a path for search-index links

Table of Contents • Index