Omni Systems, Inc. Mif2Go User's Guide, Version 55
> 5 Setting basic conversion options > 5.3 Identifying files and objects > 5.3.4 Working with Mif2Go FileIDs > 5.3.4.2 Replacing FileIDs with custom identifiers
Mif2Go-generated FileIDs are unique for all Mif2Go projects listed in .prj
files that reside in the same directory as mif2go.ini
.
If you want more associative names for FileIDs, after you have set up
a conversion you can edit mif2go.ini
to replace
generated FileIDs with identifiers of your own choosing. These identifiers
can consist of any valid file-name characters. Stick to lowercase letters
if possible, keep the identifiers short, and make sure they are unique.
Note:
Until your system is working flawlessly, do not change
the FileIDs Mif2Go writes to mif2go.ini
.
Keep in mind these restrictions:
Watch out for case sensitivity. Unless you specify [Options]CaselessMatch=No
,
Mif2Go regards AA
, Aa
,
aA
, and aa
as identical;
see §5.1.7 Specifying how to treat cases, spaces, and wildcards.
Duplicate FileIDs are allowed only for replaced FrameMaker files
There should be no duplicate FileID assignments
in mif2go.ini
, with one exception. If you change
the name of a FrameMaker file in your document, and there are cross references
to that file from other files, you might want to map both the old and
new FrameMaker file names to the same FileID, so that existing references
work. For example: