• For HTML Help Workshop to accept them, Mif2Go must treat differently the <Hn> 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.
• The sequence in which HTML Help Workshop uses the <Hn> 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, which is required if you merge CHM files at run time. See §6.5.8 .