### 8.9.1 Identifying WinHelp jump destinations with FileIDs

For a jump from a hypertext link, Mif2Go uses one of the following:

• the link text, for links within the same file

• the ObjectID, combined with the FileID or an ad hoc unique ID, for interfile links (see §5.3 Identifying files and objects).

Unless your project consists of only one file, with no cross references to other files, use the following default setting:

[HelpOptions]

; UseFileIDs = Yes (default, xrefs and ObjIDs)

; or No (single topic file)

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 have an existing WinHelp conversion project that uses the FileIDs you listed under [FileIDs] in your configuration file.

If you want to continue using the FileIDs listed in your configuration file, specify the following option:

[Setup]

; UseLocalFileID = No (default, use IDFile IDs)

; or Yes (use [FileIDs] here)

UseLocalFileID=Yes

If you want 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.

| 8.9 Creating jumps and pop-ups for WinHelp |  | 8.9.2 Configuring pop-up topics |