18.6.3 Retaining FrameMaker file paths in interfile links
By default, Mif2Go removes paths from interfile links in your FrameMaker files. If your HTML files will be maintained in a folder structure identical to the structure used for the FrameMaker files from which they are generated, you must direct Mif2Go to retain the paths in all interfile links, and then move the output files after conversion.
To retain file paths in interfile links:
; RemoveFilePaths = Yes (default, strip hyperlink and xref paths)
When RemoveFilePaths=Yes (the default), Mif2Go places all HTML files in the project folder, regardless of where the originating FrameMaker files are located. Links work as created, regardless of the original folder structure. A problem arises only if both of the following are true:
• Your FrameMaker files are in a non-flat folder structure (some FrameMaker files are in different folders).
• You move the resulting HTML files to an identical folder structure.
You might still get link errors (see §4.2.5 Checking for broken links in HTML or XML output) for links between FrameMaker files, especially if you are using the CodeStore property (see §27.7.3 Surrounding or replacing text with code or macros); however, the links should work. |
When RemoveFilePaths=No, you must place HTML output files in a folder structure on the target system that is identical to your FrameMaker folder structure. This means that after conversion, you must move HTML files from the project folder to other folders that correspond in name and relative position to the folders where the FrameMaker files are located. You can do this with system commands; see §32.4.2 Executing system commands before and after conversion.
> 18 Creating HTML links > 18.6 Linking to other files and other Mif2Go projects > 18.6.3 Retaining FrameMaker file paths in interfile links