Mif Compatibility; Changes Between Version 5.5 And 6.0 - Adobe FRAMEMAKER 6.0 Manual

Mif reference
Table of Contents

Advertisement

257

MIF Compatibility

MIF files are compatible across versions. However, some MIF statements have changed in version 5.5 of the
FrameMaker products. This appendix lists the MIF statements that are new or have changed in version 5.5
and describes how these statements are treated when an earlier version reads a MIF 5.5 file. The appendix
also lists changes between versions 5 and 4, and between versions 4 and 3 of the FrameMaker products.
MIF statements are listed by feature.
In general, when previous versions of FrameMaker products read new MIF statements, the new MIF state-
ments are stripped out and ignored. For example, if version 4 of FrameMaker reads a new 6.0 MIF
statement in a 6.0 MIF file, FrameMaker ignores the statement.

Changes between version 5.5 and 6.0

This section describes changes to MIF syntax between versions 5.5 and 6.0 of FrameMaker products.
Saving documents and books as PDF
FrameMaker documents now store information to support Structured PDF. DPDFStructure is a new
statement added to Document that specifies whether or not the document contains structure information
to use when saving as PDF. PgfPDFStructureLevel has been added to the Pgf statement to assign a
structure level to paragraph formats.
Books and documents can also include arbitrary fields of Document Info information. Documents use the
PDFDocInfo statement, and books use PDFBookInfo.
To improve handling of bookmarks hypertext links within and across PDF files, FrameMaker products
now store reference data within documents. PgfReferenced identifies each paragraph that is marked as a
named destination; ElementReferenced similarly identified structure elements. If you like, you can specify
that the Save As PDF function creates a named destination for every paragraph in the document; this is
done via FP_PDFDestsMarked within the Document statement.
Books
Version 6.0 of FrameMaker products has brought significant change to books. The book window now can
display the filename of each book component, or a text snippet from the component's document. In MIF,
BDisplayText determines which type of information to display.
A book can also be view-only; MIF now includes BViewOnly, BViewOnlyWinBorders, BViewOnlyWin-
MenuBar, BViewOnlyPopup, and BViewOnlyNoOp statements to express whether a book is view-only,
and how it should appear.

Advertisement

Table of Contents
loading

Table of Contents