10.3.9 Getting OmniHelp supporting files in the right place
Before you can use the OmniHelp viewer, all OmniHelp supporting files must be placed in the same directory structure as the HTML or XHTML output files Mif2Go generates from your document. Supporting files include:
After you run Mif2Go, control files and viewer files must be copied from the viewer directory (see §10.2 Setting up OmniHelp viewer control files) to the final distribution directory for your project. Mif2Go can do this for you; see §10.13 Assembling OmniHelp files for viewing.
To view OmniHelp, the view directory must contain the following:
• all files marked Required in column View? in Table 10-1 (including either oh*.htm or ox*.htm, depending on the start-up file type; see §10.2.1 Choosing XHTML vs. HTML OmniHelp control files).
• all files listed in Table 10-2.
Graphics files must be placed either in the same directory as the generated OmniHelp HTML files, or in a subdirectory. If your graphics files are located elsewhere, they must be copied to the directory with the HTML files, or to a subdirectory.
To tell Mif2Go to fetch your referenced graphics:
When CopyOriginalGraphics=Yes, Mif2Go follows the file paths in your FrameMaker source to find the graphics files to copy.
To tell Mif2Go where to put copies of the graphics (for example):
The path you specify for GraphPath should be relative to the wrap directory (see §35.3 Understanding path values for deliverables). This path will be used in HTML output, as the relative path from the HTML files to their referenced graphics. If you use backslashes in the path, Mif2Go converts them to forward slashes before inserting the references in your HTML output. If you specify CopyOriginalGraphics=Yes, Mif2Go copies graphics files to the directory specified by GraphPath, after generating HTML files.
§10.13 Assembling OmniHelp files for viewing.
§23.3 Locating graphics files for HTML
§35.7 Placing graphics files for distribution
A browser loads optional files (marked Optional under View? in Table 10-1), only when you specify the features they support, via configuration settings. Your project might not require all the optional files. For example, if you do not want full-text search, you can omit ohfts.js from the OmniHelp view directory; and if you are not merging OmniHelp projects, you do not need ohmerge*.* in the view directory.
See §10.2 Setting up OmniHelp viewer control files.
> 10 Generating OmniHelp > 10.3 Setting up an OmniHelp project > 10.3.9 Getting OmniHelp supporting files in the right place