9.12.2 Listing and mapping OmniHelp subprojects
To designate subprojects to be merged, list their project names in the [HelpMerge] section of the main-project configuration file. Each [HelpMerge] entry specifies a subproject name and the title to be displayed for that subproject in the main-project contents. For example:
; subproject name = Title of subproject
If your main-project FrameMaker document includes links to FrameMaker files that are part of a subproject listed in [HelpMerge], specify how those linked-to FrameMaker files are mapped to their subprojects. For example:
; Mapping of Frame files which are linked to by files in the current
; project, but are themselves part of another OH project that is
; listed in [HelpMerge], to the name of that project.
It is best to include a path, because you could have several files with the same name (such as Glossary) in several different books from which you generate different OmniHelp projects; without file paths, you would have no way to differentiate them.
To handle several possible paths to the same file, you can add a line for each path. For example:
Although you can use either forward slashes or backslashes in paths, forward slashes are preferred. FrameMaker stores cross-reference paths with forward slashes, and Mif2Go uses those cross-reference paths to find the referenced files.
> 9 Generating OmniHelp > 9.12 Merging OmniHelp projects > 9.12.2 Listing and mapping OmniHelp subprojects