### 8.2.8 Setting basic WinHelp options in the configuration file

If you are setting up a WinHelp conversion by editing the configuration file instead of using the Set Up WinHelp Project dialog, you must provide your own WinHelp.hpj file (see §8.2.5 Understanding initial set-up requirements), and add or modify the configuration settings as follows:

1. For each heading format that starts a topic, specify properties:

[HelpStyles]

; style = key list, where list members are separated

; by spaces only

ParaFmt = Property1 Property2 Property3 ...

where:

ParaFmt | is the name of the FrameMaker heading format
PropertyN | is a help style attribute, such as Topic, Browse, or Key.

2. For each topic-starting heading format that should appear in the .cnt file, specify a Contents level. For example:

[HelpCntStyles]

ParaFmt=Contents level

See §8.13.2.1 Understanding WinHelp contents level numbers.

3. Specify whether you want a combined .cnt file:

[HelpOptions]

; MakeCombinedCnt = Yes (default, when processing from open book)

MakeCombinedCnt=Yes

4. Specify whether you want to run the help compiler automatically as the last conversion step (not recommended for large projects); if so, provide a name for the help project file:

[Automation]

; CompileHelp = No (default, run help compiler separately), or Yes

CompileHelp=Yes

[HelpOptions]

; HPJFileName = name of .hpj to use when compiling help

HPJFileName=myproj.hpj

The default value of HPJFileName is the name of your FrameMaker book.

To have Mif2Go copy the .hpj file to another directory after generating output files, specify the following:

[Automation]

WrapAndShip=Yes

; WrapPath = path to dir for compiling and distribution,

; default is output dir

WrapPath=.\help

See §35.6 Assembling files for distribution.

| 8.2.7 Accommodating platform differences |  | 8.2.9 Including ObjectIDs in WinHelp |