Adobe FRAMEMAKER 6.0 Manual page 57

<TextFlow
<Notes
> # end of Notes
<Para
<Unique 45157>
<PgfTag `MyFormat'>
<ParaLine
<TextRectID 7>
<String `A single line of text.'>
>
> # end of Para
> # end of TextFlow
Delete the entire text flow.
From your application, generate a MIF file that includes the edited template file.
5
Suppose the edited MIF file is called mytemplate.mif. Your application would generate the following two
lines at the top of any new MIF file:
<MIFFile 6.00> # Generated by my application
include (mytemplate.mif)
The include statement is similar to a C #include directive. It causes the MIF interpreter to read the contents
of the file named mytemplate.mif. For more information about filenames in MIF, see "Device-independent
pathnames" on page 13.
From your application, generate a text flow that contains the entire document contents.
6
The text flow should use the ID and tag name of the text flow you deleted from the template file; this
associates the new text flow with the first body page in the template.
The entire generated MIF file would look something like this:
<MIFFile 6.00> # Generated by my application
include (mytemplate.mif)
<TextFlow
<TFTag `A'>
<TFAutoConnect Yes>
<TextRectID 7>
<Para
<ParaLine
<String `This is the content of the generated document.'>
>
> # end of Para
> # end of TextFlow
A user can open the generated MIF file to get a fully formatted FrameMaker document.
ADOBE FRAMEMAKER 6.0 57
Using MIF Statements