
ADOBE FRAMEMAKER 10
MIF Reference
105
•
Math equations
•
Groups
•
Imported graphic images, such as xwd, TIFF, bitmap images, or vector images
In a MIF file, graphic objects are defined by
Object
and
Frame
statements.
Object
refers to any MIF statement that
describes an object, such as
Arc
,
TextLine
, or
TextRect
. Generally, these objects are created and manipulated by
using the Tools palette in a FrameMaker document. This section describes general information that pertains to all
graphic objects, and then lists the MIF statements for graphic objects in alphabetic order.
Object positioning
Each
Page
statement has nested within it
Object
and
Frame
statements. If a graphic frame contains objects and other
graphic frames, the graphic frames and objects are listed in the order that they are drawn (object in back first).
For
Object
and
Frame
statements, the interpreter keeps track of the current page and current graphic frame. When
the interpreter encounters a
Frame
statement, it assumes the graphic frame is on the current page. Similarly, when
the interpreter encounters an object statement, it assumes the object is in the current graphic frame or page.
When you open a MIF file as a FrameMaker document, the default current page is page 1, and the default current
frame is the
page frame
for page 1. A page frame is an invisible frame that “contains” objects or graphic frames placed
directly on a page. The page frame is not described by any MIF statement. When you import a MIF file into an
existing FrameMaker document, the default current page is the first page visible when the Import command is
invoked; the current frame is the currently selected frame on that page. If there is no currently selected frame, the
current frame is the page frame for that page.
Generic object statements
All object descriptions consist of the object type, generic object statements containing information that is common
to all objects, and statements containing information that is specific to that type of object. This section describes the
generic object statements.
Syntax
<ID
ID>
Object ID number
<GroupID
ID>
ID of parent group object
<Unique
ID>
ID, persistent across sessions, assigned when FrameMaker generates a MIF file; used
by the FDK client and should not be used by filters
<Pen
integer>
Pen pattern for lines and edges (see
“Values for Pen and Fill statements” on
page 107
)
<Fill
integer>
Fill pattern for objects (see
“Values for Pen and Fill statements” on page 107
)
<PenWidth
dimension
>
Line and edge thickness
<ObColor
tagstring
>
Applies color from Color Catalog (see page 80)
<ObTint
percentage
>
Applies a tint to the object color; 100% is equivalent to the pure object color and 0%
is equivalent to no color at all
<Separation
integer
>
Applies color; no longer used, but written out by FrameMaker for backward-
compatibility (see
“Color statements” on page 249
)
<Overprint
boolean
>
Yes
turns on overprinting for the graphic object.
No
turns on knockout. If this
statement is not present, then the overprint setting from the object’s color is
assumed.