### 19.6.5 Enabling links to files in other projects

You can create HTML output from one Mif2Go project that has active links to HTML files in another Mif2Go project, provided the two projects meet the following requirements:

• For each project, all HTML files generated from a given FrameMaker file are in the same directory as the corresponding reference (.ref) file (see §C.5 Working with reference files for HTML or XML).

• FrameMaker file names in the two projects are unique (for example, you cannot have files in both called Intro.fm), unless there are no inter-project links to or from files that have the same name.

FileID files must match

All FrameMaker files in both projects must be listed in the same FileID file (mif2go.ini); see §5.3.4.1 Understanding how and where FileIDs are assigned.

To reference the same FileID file from the configuration files for both projects, include the following setting in each project configuration file:

[Setup]

; IDFileName = name of file that contains FileIDs for this project

IDFileName=F:/path/to/combined/mif2go.ini

See §C.4 Renaming or relocating the Mif2Go FileID file.

Reference files must reciprocate

If the two projects produce HTML files (and reference files) in different project directories, 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:

[RefFiles]

; original .fm filename = path to directory containing its .ref file

omnihelp=g:/omnisys/ug/oh

ohdesign=g:/omnisys/omhelp

You must include [RefFiles] sections in the configuration files for both projects, each with entries that point to the location of .ref files in the other project.

Wildcards in file names

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.

As a worst case, if you were to specify *=some/other/directory, Mif2Go would do the following:

• direct all interfile links in the second project to some/other/directory

• write all *.ref files for the second project to some/other/directory.

This is a spectacularly Bad Idea.

If a reference file is not found

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.

To find a reference file, Mif2Go looks in the following places, in this order:

• the directory (if any) you specified in [RefFiles]

• the directory where the FrameMaker file in question resides

• the project directory for the current conversion.

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 directory. 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 directory you specified, Mif2Go looks in the directory 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 directory; if a MIF file is present, Mif2Go creates a reference file in that directory.

If the write fails this time, or if there is no MIF file, Mif2Go looks in the current project directory. If the reference file is not there, Mif2Go creates a reference file in the current project directory.

| 19.6.4 Enabling links to renamed or relocated files |  | 19.6.6 Updating links between files in different projects |