9.14.1 Directing Mif2Go to run the HTML Help compiler
When you check Compile Help in the Mif2Go Export dialog (see §3.6 Converting documents), or specify the following options in the configuration file, Mif2Go automatically runs the HTML Help compiler after generating output files:
For large projects, you might want to stick with CompileHelp=No; then after Mif2Go finishes the conversion, compile directly from HTML Help Workshop. Otherwise you might encounter memory limitations when Mif2Go tries to run the compiler.
If the HTML Help compiler is not on your system PATH, you must tell Mif2Go where to find it. For example:
; Compiler = path to hhc.exe, not required if its directory is in the
; system PATH environment variable.
You might also want to set the following option, so you can see any error messages that result:
; KeepCompileWindow = No (default)
; or Yes (so any error messages can be seen)
When KeepCompileWindow=Yes, a system window opens when the compiler runs. If there are no compilation errors, you will see only a command prompt when compilation finishes. You must dismiss the window before Mif2Go can continue processing.
If the compiler does not run when CompileHelp=Yes, try copying hh.exe and hhc.exe to C:\Windows, and hha.dll to C:\Windows\System32. Then restart FrameMaker before you run Mif2Go again.
To have Mif2Go copy the .hhp file to another directory for compiling, specify the following:
; WrapPath = path to dir for compiling and distribution,
See §35.6 Assembling files for distribution.
§7.2.4 Compiling and distributing Help systems
§9.3.10 Locating graphics files for HTML Help
§9.14.2 Copying output files and compiling later
> 9 Generating Microsoft HTML Help > 9.14 Compiling and testing HTML Help > 9.14.1 Directing Mif2Go to run the HTML Help compiler