Other Application Tools; Where To Go From Here - Adobe FRAMEMAKER 10 User Manual

Here are some additional tips for debugging MIF files:
•
Use the statement to generate comments. To debug a specific section of a MIF file, you can precede the
Verbose
section with the
<Verbose Yes>
• Make sure angle brackets are balanced.
•
Make sure that MIF statement names are capitalized correctly. MIF statement names and keyword values are
case-sensitive.
•
Make sure that string arguments are enclosed in straight single quotation marks. (See
for an example.)
• Make sure ID numbers are unique.
•
Make sure that every table anchor has a corresponding table instance, and that every table instance has an anchor
in the text flow.
•
Make sure that tag names with spaces are enclosed in straight single quotation marks.
• Make sure paired statements are balanced. For example,
• Make sure that right angle bracket (>) and backslash (\) characters in text are preceded by a backslash.
•
Make sure that hexadecimal characters, for example

Other application tools

The Frame Developer's Kit (FDK) provides tools that you can use to write filters and to perform custom document
processing. The FDK includes the Application Program Interface (API), which you can use to create a C application
that can create and save documents, modify documents, and interact with the user. The FDK also includes the Frame
Development Environment (FDE), which allows you to make your FDK clients portable to the platforms that
FrameMaker supports.
MIF files can be used by C applications, text processing utilities, or UNIX shell scripts. You might want to work
directly with MIF files if you are filtering large numbers of files in batch mode. You also might want to work with
MIF files if you are doing simple document processing, such as changing a few tag names, or if you are setting options
for View Only documents.
You can use the FDK and MIF files together; for example, a database publishing application can extract values from
a database and write out the information as a table in a MIF file. An FDK client can then automatically open the MIF
file as a FrameMaker document.

Where to go from here

This chapter has given you a start at working with MIF files. You can use the information in this chapter as guidelines
for working with similar MIF statements. Once you have experimented with basic MIF files, you can learn about
other MIF statements by creating small FrameMaker documents that contain a specific feature and saving these
documents as MIF files. Because FrameMaker writes complete and precise MIF code, it is your ultimate source for
learning about MIF statements.
For more information about document components not described in this chapter, see the MIF statement descrip-
tions in , "MIF Document Statements", , "MIF Book File Statements", and , "MIF Statements for Structured
Documents and Books".
statement and end the section with the
XRef
\xe6
<Verbose No>
and statements must be paired.
XRefEnd
, have a space after them.
ADOBE FRAMEMAKER 10
MIF Reference
statement.
"MIF data items" on page 5
51