Omni Systems, Inc. |  | Mif2Go User's Guide, Version 55 |  |  |  |  |

> 6 Converting to print RTF > 6.11 Converting cross references and hypertext links > 6.11.5 Enabling interfile cross references and hypertext links > 6.11.5.1 Identifying Word link destinations with FileIDs

#### 6.11.5.1 I dentifying Word link destinations with FileIDs

For active interfile links in Word, link code must include file identification. The following default setting ensures that cross references and hypertext links in your document include FileIDs:

[WordOptions]

; UseFileIDs = Yes (default, needed for identifying xrefs) or No

UseFileIDs=Yes

When UseFileIDs=Yes, Mif2Go includes a FileID in the link code, so links do not get confused if a cross-reference number or ObjectID is not unique. Mif2Go assigns FileIDs to your FrameMaker files; see §5.3.4 Working with Mif2Go FileIDs.

Keeping or replacing FileIDs

Suppose you are still using an RTF conversion project that has FileIDs listed under [FileIDs] in your configuration file; you can either continue using the existing FileIDs, or switch to the newer (preferred) method.

To continue using FileIDs listed in your configuration file, specify the following option:

[Setup]

; UseLocalFileID = No (default, use IDFile IDs)

; or Yes (use [FileIDs] here)

UseLocalFileID=Yes

See §5.3.4.4 Keeping legacy FileIDs in the configuration file.

To switch to mif2go.ini FileIDs, stay with the default, UseLocalFileID=No; and update settings in any configuration sections that reference the original FileIDs, such as the [Graph*] sections. See §5.3.4.3 Updating files and references when FileIDs change.

> 6 Converting to print RTF > 6.11 Converting cross references and hypertext links > 6.11.5 Enabling interfile cross references and hypertext links > 6.11.5.1 Identifying Word link destinations with FileIDs

| Mif2Go User's Guide: 6.11.5 Enabling interfile cross references and hypertext links |  | Mif2Go User's Guide: 6.11.5.2 Creating Word bookmarks for interfile cross references |