Omni Systems, Inc. Mif2Go User's Guide, Version 55
> 9 Generating Microsoft HTML Help > 9.9 Generating contents and index for HTML Help > 9.9.3 Generating contents and index with HTML Help Workshop
If you specify RefFileType=HHW
,
HTML Help Workshop constructs the Contents panel, and uses your <H
n>
tags as the
source of the line items. This has two consequences:
<H
n>
tags in the
body file from which the .hhc
file is created,
by omitting all attributes, including CSS style; therefore you lose control
over much of their appearance in the body file.
<H
n>
tags is determined by the sequence of the files listed in the .hhp
file; if a file is out of order in the list, its contents appear out
of order in the .hhc
file. When many of your files are
created by splitting, keeping the .hhp
list
up to date becomes a maintenance nightmare.
When HTML Help Workshop creates the index, Mif2Go embeds FrameMaker index markers (minus the parts that HTML Help
does not understand) as K-type index entries in the .htm
files. This has two consequences:
It is best not
to use HTML Help Workshop to modify the contents and index files, but
to include these files in the compilation as is,
for this reason: Mif2Go uses the [sort]
information
from FrameMaker to order the entries in the index file. If you regenerate
this file using HTML Help Workshop, that work is trashed, and sorting
goes by text only. The same is true if you specify a binary index.
Note: A binary index is required if you merge CHM files at run time.
See §7.5.9 Customizing index sort order.