8.2.10.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 folder for compilation, then copy (do not move) the required files to that folder: .htm, .hhk, .hhc, .hha, and .hhp. Because the project folder 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 folder. Also, place your CSS file in the compilation folder.

Note:

If you manually copy files to another folder for compilation, do not check Compile Help in the Mif2Go Export dialog; that option works only on files in the project folder or in a folder you specify via [Automation]WrapPath. Compile from HTML Help Workshop instead.

You can use macros (see §27 Working with Mif2Go macros), and on some systems you can use system commands (see §32.4.2 Executing system commands before and after conversion), to move just the compilable HTML Help files into place after converting a FrameMaker document. For sample macros and system commands, look in the [MSHtmlHelpMacros] section of file m2hmacro.ini, in your Mif2Go distribution folder.

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

[BookFileCommands]

BookStartCommand=<$SetUpHHDirs>

BookEndCommand=<$CopyHHFiles>

If you copy graphics files to the compilation folder, set the following option in configuration file mif2htm.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.

---

> 8 Generating Microsoft HTML Help > 8.2 Setting up an HTML Help project > 8.2.10 Compiling and testing an HTML Help project > 8.2.10.2 Copying output files and compiling later