Adobe FRAMEMAKER 10 - MIF Statement Syntax

ADOBE FRAMEMAKER 10
MIF Reference
4
• Page properties
• Graphic frame properties
• Text frame properties
• Fill pattern
• Pen pattern
• Line width
• Line cap
• Line style (dash or solid)
• Color
• Text line alignment and character format
Because the interpreter also provides default objects for a document, the current state of an object may be deter-
mined by a default object. For example, if a document does not provide any paragraph formats, the interpreter
applies a set of default paragraph properties to the first paragraph. Subsequent paragraphs use the same properties
unless otherwise specified.
How FrameMaker identifies MIF files
A MIF file must be identified by a MIFFile or Book statement at the beginning of the file; otherwise FrameMaker
simply reads the file as a text file. All other statements are optional; that is, a valid MIF file can contain only the
MIFFile statement. Other document objects can be added as needed; FrameMaker provides a set of default objects
if a MIF file does not supply them.
MIF statement syntax
The statement descriptions in this manual use the following conventions to describe syntax:
< token data >
token data where token represents one of the MIF statement names (such as Pgf) listed in the MIF statement
descriptions later in this manual, and
data represents one or more numbers, a string, a token, or nested statements.
Markup statements are always delimited by angle brackets (<>); macro statements are not. For the syntax of macro
statements, see “Macro statements” on page 56.
A token is an indivisible group of characters that identify a reserved word in a MIF statement. Tokens in MIF are
case-sensitive. A token cannot contain white space characters, such as spaces, tabs, or newlines. For example, the
following MIF statement is invalid because the token contains white space characters:
<Un its Uin>
When the MIF interpreter finds white space characters that aren’t part of the text of the document (as in the example
MIF statement,
< Units Uin >), it interprets the white space as token delimiters. When parsing the example
statement, the MIF interpreter ignores the white space characters between the left angle bracket (<) and the first
character of the token,
Units. After reading the token, the MIF interpreter checks its validity. If the token is valid,
the interpreter reads and parses the data portion of the statement. If the token is not valid, the interpreter ignores all
text up to the corresponding right angle bracket (>), including any nested substatements. The interpreter then scans
the file for the next left angle bracket that marks the beginning of the next MIF statement.
All statements, as well as all data portions of a statement, are optional. If you do not provide a data portion, the MIF
interpreter assigns a default value to the statement.