Adobe FRAMEMAKER 10 - Page 171

ADOBE FRAMEMAKER 10
MIF Reference
166
Usage
FrameMaker writes out the tagstring value in an ElementEnd statement for use by filters. Your application does
not need to supply the
tagstring value when it writes MIF files.
If the interpreter reads unbalanced ElementBegin and ElementEnd statements, it ignores superfluous element ends
and closes all open elements at the end of a
TextFlow statement. If the interpreter reads a flow that does not have an
element enclosing all of the flow’s contents, it creates a highest-level element with the tag
NoName. ElementBegin
and
ElementEnd statements are nested within ParaLine and BookElements statements. The following example
shows how FrameMaker writes an UnorderedList element:
<Para
<PgfTag `Bullet'>
# The autonumber contains a bullet and a tab.
<PgfNumString `• \t'>
<ParaLine
# Note that the ElementBegin statement is nested inside both
# the Para and ParaLine statements.
<ElementBegin
<ETag `UnorderedList'>
<Collapsed No >
<ENamespacePrefix string >
The prefix that identifies the namespace
<ENamespacePath string >
The system path or URI to the DTD or schema that defines the namespace
…
Additional pairs of prefix and path statements as needed
>
End of Namespace statement
<AttributeDisplay keyword >
Default attribute display setting for element
keyword can be one of:
AllAttributes: display all attributes
ReqAndSpec: display required and specified attributes
None: don’t display attributes
<Atributes
Element’s attributes
<Attribute
Attribute’s name and values
<AttrName string >
Attribute name
<AttrValue string >
Attribute value
<AttrValue string >
Attribute value if attribute allows more than one value
…
>
End of Attribute statement
<Attribute…>
Additional statements as needed
…
>
End of Attributes statement
<UserString string >
A string in which clients can store private data — can be up to 1023 char-
acters in length
>
End of ElementBegin statement
<ElementEnd tagstring >
End of specified element