Omni Systems, Inc. Mif2Go User's Guide, Version 55
You can tell Mif2Go to look for replacement files that differ from the original files in any or all of the following respects:
To map referenced graphics to replacements:
; FileNames = Retain (default) or Map (in the GraphFiles section)
; FilePaths (for graphics) = Retain (default) or None (strip off)
To specify different file paths, different names,
or different extensions, when FileNames=Map
:
; types to map, replace extension, old=new for referenced graphics
; specific filenames to replace, old = new, overrides type setting
Note:
When you specify paths in [GraphFiles]
,
use forward slashes for separators.
Table 31FileNames
and FilePaths
values and [GraphFiles]
settings.
Table 31
When FileNames=Map
, Mif2Go uses the settings in [GraphFiles]
to find replacements.
When FileNames=Retain
,
Mif2Go ignores the settings in [GraphFiles]
,
and looks for replacements in one of two places (determined by the FilePaths
setting): the same directory as the original graphics, or the project
directory.
When FilePaths=None
, Mif2Go ignores the path component of the file references
in FrameMaker. Unless you specify FileNames=Map
and a different path in [GraphFiles]
, Mif2Go looks for replacements only
in the project directory.
You can use FilePaths=None
when you are converting on a system different from the system used for
authoring or editing, to avoid replicating the directory structure. This
setting prevents problems with attempted access to drives (such as network
drives) that do not exist on the system used for conversions, but do
exist on the systems used for authoring or editing.
When FilePaths=Retain
,
unless you specify FileNames=Map
and different
paths for both original and replacement files in [GraphFiles]
,
Mif2Go looks for replacement graphics only
in the same directory as the original files.
Avoid specifying original file paths
It is best to use FilePaths=None
,
and put the replacements in the project directory. This is because specifying
original file paths in [GraphFiles]
is problematic;
success depends on exactly matching the paths in FrameMaker, whether they are absolute or relative.