Omni Systems, Inc. Mif2Go User's Guide, Version 55
> 30 Working with templates > 30.7 Applying FrameMaker conversion templates > 30.7.1 Specifying conversion-template settings
To have Mif2Go apply a FrameMaker template to your document,
your configuration file must include values for three template settings:
ApplyTemplateFile
, TemplateFileName
,
and AppliedTemplateFlags
. For example:
; ApplyTemplateFile = No (default) or Yes (save and restore document)
; TemplateFileName = filename.fm (FrameMaker template for export)
TemplateFileName="G:\Omnisys\UG\UGTplHlp.fm"
; AppliedTemplateFlags = 0 (default) or bitfield spec of properties
Unless the template to be applied is in the same
directory as the document you are converting, specify a full absolute
path (not a relative path) for TemplateFileName
.
Enclose the entire path in quotes if the path includes any spaces (and
see §2.1 Naming files, directories, and paths).
FrameMaker uses the value of AppliedTemplateFlags
to determine which items to import. This number is a representation of
the choices you make via Import Formats:
the decimal sum of the values (listed in Table 30AppliedTemplateFlags
would be 1+128+16=145
.
Note:
A value of zero (AppliedTemplateFlags=0
)
means import everything. To import nothing, you must set ApplyTemplateFile=No
.
Table 30
If absolutely necessary, you can also specify the following template option:
; ImportDocProps = No (default) or Yes (include doc props in import)
By default, Mif2Go instructs FrameMaker not to import document properties, which include the following:
Note:
A defect in FrameMaker
can cause numerous document settings to change unexpectedly when you
import document properties, even from the same file. Unless
you have a very good reason to import document properties, use only the
default setting: ImportDocProps=No
.