• For each project, all HTML files generated from a given FrameMaker file are in the same folder as the corresponding reference (.ref) file (see §C.5 ).
All FrameMaker files in both projects must be listed in the same FileID file (mif2go.ini); see §188.8.131.52 .
See §C.4 .
If the two projects produce HTML files (and reference files) in different project folders, for each project you must tell Mif2Go where to find the appropriate reference files that go with the FrameMaker files in the other project. For example:
You can use wildcards in the FrameMaker file names you specify in [RefFiles], provided the result does not inadvertently subsume the name of any FrameMaker file in the other project. The settings in section [RefFiles] are the first things Mif2Go checks.
If Mif2Go cannot find (or create) a reference file, links to any HTML files split from the FrameMaker file in question revert to links to the base name of that FrameMaker file, with extension .htm; and those links do not work.
If you specify a path in [RefFiles], but the required reference file is not in the specified location, Mif2Go creates a reference file in that folder. Mif2Go goes on to look at other possibilities only if writing the new reference file fails, perhaps due to server permissions.
If Mif2Go cannot create a reference file in the folder you specified, Mif2Go looks in the folder where the link is pointing: at the FrameMaker file. If the reference file is not there, Mif2Go looks for a matching MIF file in the same folder; if a MIF file is present, Mif2Go creates a reference file in that folder.
If the write fails this time, or if there is no MIF file, Mif2Go looks in the current project folder. If the reference file is not there, Mif2Go creates a reference file in the current project folder.
> 18 Creating HTML links > 18.6 Linking to other files and other Mif2Go projects > 18.6.5 Enabling links to files in other projects