47
ADOBE FRAMEMAKER 6.0
Using MIF Statements
Other master page layouts that you’ve defined are not lost when the interpreter reads a MIF file. The user
can still apply these page layouts to individual body pages.
For an example of a MIF file with a first page layout, see the sample file
frstpage.mif
.
Adding headers and footers
Headers and footers are defined in untagged text flows on the master pages of a document. When a
FrameMaker product creates default master pages, it automatically provides untagged text flows for
headers and footers.
If you are importing a document that has headers and footers, you define additional text frames on the
master pages. Link an untagged text flow to each additional text frame on the master page. The untagged
text flow contains the text of the header or footer.
For an example of a MIF file with a footer, see the sample file
footers.mif
. Note that the footer text flow
contains a variable; you can place variables only in untagged text flows on a master page, not in tagged
flows.
Creating markers
A FrameMaker document can contain markers that hold hidden text and mark locations. For example, you
use markers to add index entries, cross-references, and hypertext commands to a document. A
FrameMaker product provides both predefined marker types and markers that you can define as needed.
(For more information about markers and marker types, see page 137.)
Within a FrameMaker document, you insert a marker by choosing the Marker command from the Special
menu. In a MIF file you insert a marker by using a
Marker
statement. The
Marker
statement specifies the
marker type and the marker text.
The following example inserts an index marker:
<Para
<ParaLine
<Marker
<MType 2>
# Index marker
<MText `Hello world'>
# Index entry
> # end of Marker
<String `Hello world'>
> # end of ParaLine
> # end of Para
The
MText
statement contains the complete index entry.
When a FrameMaker product writes a
Marker
statement, the statement includes an
MCurrPage
substatement with the page number on which the marker appears. You do not need to provide an
MCurrPage
statement when you generate a MIF file; this statement is ignored when the MIF interpreter
reads a MIF file.
Содержание FRAMEMAKER 6.0
Страница 1: ...MIF Reference Online Manual FrameMaker 6 0 Adobe ...
Страница 15: ...15 ADOBE FRAMEMAKER 6 0 Introduction ...
Страница 142: ...142 ADOBE FRAMEMAKER 6 0 MIF Document Statements update the text inset when changes are made to the original file ...
Страница 159: ...159 ADOBE FRAMEMAKER 6 0 MIF Book File Statements ...
Страница 232: ...232 ADOBE FRAMEMAKER 6 0 MIF Asian Text Processing Statements ...
Страница 252: ...252 ADOBE FRAMEMAKER 6 0 Examples ...
Страница 268: ...268 ADOBE FRAMEMAKER 6 0 MIF Compatibility ...