For CHM files other than the default file (see §184.108.40.206 ), specify how FrameMaker files should be mapped to the other CHM files:
It is best to include a path to each FrameMaker file, because you could have several files with the same name in different books or projects from which you generate different CHM files. Without file paths, you would have no way to differentiate these files. Although you can use either forward slashes or backslashes in paths to FrameMaker files, forward slashes are preferred. FrameMaker stores cross-reference paths with forward slashes, and Mif2Go uses those cross-reference paths to find the referenced files. See §220.127.116.11 .
It is best not to specify paths for CHM files mapped in [ChmFiles], because Microsoft does not allow relative paths to CHM files. Although you can specify an absolute path, absolute paths are not a good idea. You cannot predict where the file will be placed on every system. When no path is specified, HTML Help uses the Windows Registry entry to find the CHM file, provided one of the following is true:
To link CHM files generated from multiple FrameMaker books in different Mif2Go projects, consider using a configuration template; see §4.5 . Specify [ChmFiles] mappings for all books in the template. If a given FrameMaker file appears in more than one book, the project configuration file for each such book must include a [ChmFiles] mapping for that file. The project-specific mapping takes precedence over the mapping in the configuration template.