ADOBE FRAMEMAKER 10
MIF Reference
45
<PenWidth 1.0 pt>
<ObColor `Black'>
<DashedPattern
<DashedStyle Solid>
>
# end of DashedPattern
<ShapeRect 1.0" 1.0" 6.5" 9.0">
<TRNext 0>
>
# end of TextRect
>
# end of Page
The ID for the
TextRect
on this body page is 7. Remember this ID number. If there is more than one
TextRect
on the body page, remember the ID of the first one.
3
Locate the text flow associated with the TextRect statement on the first body page and delete it.
Suppose you are working with the previous example. You would search for the statement
<TextRectID 7>
to
locate the text flow. It might look similar to the following:
<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.
4
From your application, generate a MIF file that includes the edited template file.
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 8.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 7
.
5
From your application, generate a text flow that contains the entire document contents.
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 8.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.