9.14.2 Copying output files and compiling later

If you do not want Mif2Go to automatically copy output files and run the HTML Help compiler, you can create a separate directory for compilation, then copy (do not move) the required files to that directory: .htm, .hhk, .hhc, .hha, and .hhp. Because the project directory contains a lot of other files that are all part of the conversion machinery, you must keep a set of these files in the project directory. Also, place your CSS file in the compilation directory.

Note:  If you manually copy files to another directory for compilation, do not check Compile Help in the Mif2Go Export dialog; that option works only on files in the directory specified by[Automation]WrapPath (see §35.3 Understanding path values for deliverables). Compile from HTML Help Workshop instead.

You can use macros (see §28 Working with macros), and on some systems you can use system commands (see §34.4 Executing operating-system commands), to move just the compilable HTML Help files into place after converting a FrameMaker document.

For example, you could define macro <$SetUpHHDirs> to create the compilation directory at the start of conversion, and macro <$CopyHHFiles> to actually copy files to the compilation directory after conversion. You would add the following settings:

[Automation]

SystemStartCommand = <$SetUpHHDirs>

SystemEndCommand = <$CopyHHFiles>

If you copy graphics files to the compilation directory, set the following option in project configuration file m2htmlhelp.ini, to remove path information from references to the graphics files:

[Graphics]

StripGraphPath = Yes

When Mif2Go finishes converting your document, select the .hhp file in HTML Help Workshop, and compile the project.

---

> 9 Generating Microsoft HTML Help > 9.14 Compiling and testing HTML Help > 9.14.2 Copying output files and compiling later