Adobe FRAMEMAKER 10 - Page 243

ADOBE FRAMEMAKER 10
MIF Reference
238
Cannot store inset’s facets. The MIF file contains a graphic inset, but the MIF interpreter
can’t store the graphic inset in the document. There might be an
error in the MIF syntax, or there might not be enough temporary
disk space available. In UNIX versions, try to increase the space
available in your home directory or the /usr/tmp directory
and try again. In the Windows versions, try quitting other appli-
cations and closing other open windows; then start
FrameMaker again.
Char out of range: character_value. A character in a Char statement or a character expressed using
\x in a string is out of range.
Condition settings must not change between <XRef> and
<XRefEnd>.
You cannot change a condition tag setting in the middle of a
cross-reference. Make sure the entire cross-reference is
contained in one condition setting.
DashedPattern statement has no DashedSegment state-
ments.
A DashedPattern statement gives DashedStyle a value
of Dashed but has no DashedSegment statements to
define the dashed pattern.
Empty group: ID=n. The group ID specified in a Group statement has no corre-
sponding defined objects with a matching group ID.
Expected comma/identifier/left parenthesis/right paren-
thesis/right quote.
The MIF file contains a syntax error.
Following <TabStop> statements will determine actual
number of tabs.
The PgfNumTabs statement is present in MIF for use by other
programs that read MIF files; it is not used by the MIF interpreter.
When the MIF interpreter reads a MIF file, it counts the number
of TabStop statements to determine the number of tabs stops
in a paragraph.
Frames are nested too deeply (over 10); skipping statement. There are too many nested frames. The maximum nesting depth
is 10.
Graphic frame has an invalid <Angle> attribute. An invalid value is specified by the Angle statement for a
graphic frame.
Insufficient memory! FrameMaker cannot allocate enough memory for one of its
work buffers. In UNIX versions, try to free some swap space and
restart FrameMaker. In the Windows versions, try quitting other
applications and closing other open windows; then start
FrameMaker again.
Invalid opcode: op_code. The MIF file contains a syntax error.
Macro/IncludeFile nesting too deep. The define or include statements specify too many nested levels
of statements.
Missing dimension. A necessary dimension value was not found in a MIF statement.
No name was given for the cross-reference format:
format_definition.
The
XRefName statement is not specified for a cross-reference
format.
No name was given for the variable definition: vari-
able_definition
.
The
VariableName statement is not specified for a variable.
Object ignored; must come before <TextFlow> statements. All object statements must come before the first TextFlow
statement in a MIF file.
Processing opcode
op_code. FrameMaker is currently processing the specified opcode.
Skipped ‘
string’. The MIF file contains a syntax error.
This message Means