Adobe FRAMEMAKER 6.0 Manuel utilisateur

MIFReferenceOnlineManual

FrameMaker

6.0

Adobe

Adobe, the Adobe logo, Acrobat, Acrobat Reader, Adobe Type Manager, ATM, Display PostScript, Distiller, Exchange, Frame,

FrameMaker, FrameViewer, InstantView, and PostScript are trademarks of Adobe Systems Incorporated. Apple, PowerBook,

QuickTime, Mac, Macintosh and Power Macintosh are trademarks of Apple Computer, Inc., registered in the United States and

othercountries.HP-UXisaregisteredtrademarkofHewlett-PackardCompany.Microsoft,MS-DOS,Windows,andWindowsNT

are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.. Sun and

Solarisaretrademarksorregisteredtrademarksof SunMicrosystems,Inc. intheUnitedStatesandothercountries.Unixisaregis-

teredtrademarkandXWindowSystemisatrademarkofTheOpenGroup.Allothertrademarksarepropertyoftheirrespectiveowners.

Contents

Introduction Why use MIF? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Using this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Overview of MIF statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

MIF statement syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Using MIF Statements Working with MIF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Creating a simple MIF file for FrameMaker . . . . . . . . . . . . . . . . . . . . . . . . . 18

Creating and applying character formats . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Creating and formatting tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Specifying page layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Creating cross-references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Creating variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Creating conditional text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Including template files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 55

Setting View Only document options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Applications of MIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Debugging MIF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Other application tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

MIF Document

Statements MIF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

MIFFile statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Control statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Macro statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Conditional text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 71

Paragraph formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Character formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Cross-references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 97

Global document properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 98

Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Graphic objects and graphic frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Text flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Text insets (text imported by reference) . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Publishers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

MIF Book File Statements MIF book file overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

MIF book file identification line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Book statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

MIF Statements for

Structured Documents

and Books

Structural element definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Attribute definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Format rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 165

Format change lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 178

Preference settings for structured documents . . . . . . . . . . . . . . . . . . . . . . 180

Text in structured documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 183

Structured book statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

MIF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

MIF Equation Statements Document statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 189

Math statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 194

MathFullForm statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 195

MIF Asian Text

Processing Statements Asian Character Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Combined Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Kumihan Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Rubi text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Examples Text example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Bar chart example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Pie chart example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Custom dashed lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 239

Table examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Database publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

MIF Messages General form for MIF messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

List of MIF messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 253

MIF Compatibility Changes between version 5.5 and 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Changes between version 5 and 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 258

Changes between versions 4 and 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 260

Changes between versions 3 and 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 264

Facet Formats for

Graphics Facets for imported graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Basic facet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Graphic insets(UNIX versions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

General rules for reading and writing facets . . . . . . . . . . . . . . . . . . . . . . . 278

EPSI Facet Format Specification of an EPSI facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Example of an EPSI facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

FrameImage Facet

Format Specification of a FrameImage facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Specification of FrameImage data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Differences between monochrome and color . . . . . . . . . . . . . . . . . . . . . . . 285

Sample unencoded FrameImage facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Sample encoded FrameImage facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

FrameVector Facet

Format Specification of a FrameVector facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Specification of FrameVector data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Sample FrameVector facet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Introduction

MIF (Maker Interchange Format) is a group of ASCII statements that create an easily parsed, readable text

file of all the text, graphics, formatting, and layout constructs that most FrameMaker®products (with the

exception of FrameReader®) understand. Because MIF is an alternative representation of a FrameMaker

document, it allows FrameMaker products and other applications to exchange information while

preserving graphics, document content, and format.

Why use MIF?

YoucanuseMIFfilestoallow FrameMakerproductsandother applicationstoexchangeinformation.For

example, you can write programs to convert graphics and text into MIF and then import the MIF file into

a FrameMaker product with the graphics and text intact. You can also save a FrameMaker document or

bookfileasaMIFfileandthenwriteaprogramtoconverttheMIFfiletoanotherformat.Theseconversion

programs are called filters; filters allow you to convert FrameMaker document files into foreign files (files

in another word processing or desktop publishing format), and foreign files into FrameMaker document

files.

You can use MIF files with database publishing applications, which allow you to capture changing data

from databases and format the data into high-quality documents containing both text and graphics infor-

mation.You use the databasetoenter, manipulate, sort,and select data.You usea FrameMakerproduct to

format the resulting data. You use MIF files as the data interchange format between the database and the

FrameMaker product.

You can also use MIF files to do the following:

•Share documents with earlier versions of FrameMaker products

•Perform custom document processing

•Set options for online documents in View Only format

These tasks are described in “Applications of MIF” on page 60. Youcan use other FrameMaker products to

perform some of these tasks. See “Other application tools” on page 64.

Using this manual

This manual:

•Describes the layout of MIF files.

•Provides a complete description of each MIF statement and its syntax.

•Provides examples of how to use MIF statements.

•Includes MIF statements for version 5.5 of the following FrameMaker products: FrameMaker®,

FrameViewer®, FrameMaker+SGML™.

7ADOBE FRAMEMAKER 6.0

Introduction

YourFrameMakerproductmaynotincludeallofthefeaturesdescribedinthismanual.Forexample,some

statements appear in all MIF files but are only applicable for structured documents created with

FrameMaker+SGML. Contact your FrameMaker local customer service representative for information

about other FrameMaker products.

To get the most from this manual you should be familiar with your FrameMaker product. For information

about a FrameMakerproduct and itsfeatures, see the documentation for your product. In addition, if you

are using MIF as an interchange format between a FrameMaker product and another application, you

should be familiar with thetools needed to create and manipulate the other application, such as a

programming language or database query language.

This chapterprovidesbasicinformationaboutworkingwithMIFfiles, including opening andsavingMIF

files in yourFrameMakerproduct.Itgoesontoprovidedetailed informationabout theMIFlanguage and

its syntax.

For an introduction to writing MIF files, read , “Using MIF Statements.” You can then use the statement

index, subject index, and table of contents to locate more specific information about a particular MIF

statement.

For a description of a MIF statement, use the table of contents or statement indexto locate the statement.

For a description of the differences between the MIF statements for this version of your FrameMaker

product and earlier versions, see , “MIF Compatibility.”Style conventions

This manual uses different fonts to represent different types of information.

•What you type is shown in

•MIF statement names, pathnames, and filenames are also shown in

•Placeholders (such as MIF data) are shown in

text like this.

For example, the statement description for is shown as:

You replace tagstring with the tag of a paragraph format.

This manual also uses the term FrameMaker, (as inFrameMaker product,FrameMaker document, or

FrameMaker session) to refer to anyof the FrameMaker, FrameMaker+SGML, and FrameViewer products.

Overview of MIF statements

When you are learning about MIF statements, you may find it useful to understand how FrameMaker

products represent documents.

8ADOBE FRAMEMAKER 6.0

Introduction

How MIF statements represent documents

FrameMaker products represent document components asobjects. Different types of objects represent

different components in a FrameMaker document. For example, a paragraph is considered an object; a

paragraph format is considered a formatting object. The graphic objects that you createby using the Tools

palette are yet another type of object.

Each object has properties that represent its characteristics. For example, a paragraph has properties that

representitsleftindent,thespaceabove it,anditsdefaultfont.Arectangle has propertiesthatrepresentits

width, height, and position on the page.

When a FrameMaker product creates a MIF file, it writes an ASCII statement for each object in the

document or book. The statement includes substatements for the object’s properties.

For example,supposeadocument(withnotextframe)containsarectanglethatis2 incheswideand1 inch

high.Therectangleislocated3inches from theleftside ofthepageand1.5 inchesfromthetop. MIFrepre-

sents this rectangle with the following statement:

<Rectangle # Type of graphic object

<ShapeRect 3.0" 1.5" 2.0" 1.0"> # Position and size: left offset,

# top offset, width, and height

A FrameMaker product also treats each document as an object and stores document preferences as

properties of thedocument. For example, adocument’spagesizeandpagenumberingstyle aredocument

properties.

FrameMaker documents have default objects

A FrameMaker document always has a certain set of default objects, formats, and preferences, even when

you create a new document. When you create a MIF file, you usually provide the objects and properties

that your document needs. However, if you don’t provide all the objects and properties required in a

FrameMaker document, the MIF interpreter fills in a set of default objects and document formats.

The MIF interpreter normally provides the following default objects:

•Predefined paragraph formats for body text, headers, and table cells

•Predefined character formats

•A right master page for single-sided documents and left and right master pages for double-sided

documents

•A reference page

•Predefined table formats

•Predefined cross-reference formats

•Default pen and fill values and dash patterns for graphics

•Default colors

•Default document preferences, such as ruler settings

•Default condition tags

9ADOBE FRAMEMAKER 6.0

Introduction

AlthoughyoucanrelyontheMIFinterpretertoprovidedefaults,theexactpropertiesandobjectsprovided

may vary dependingon your FrameMaker product’s configuration. The MIF interpreter uses default

objectsandpropertiesthatarespecifiedinsetupfilesandintemplates.InUNIX®versions,thesetemplates

are and .You can modify these defaultobjects and document formats by creatingyour own version of or

or by modifying your setup files.

For more information about modifying the default templates and setup files, see the online manual

Customizing FrameMaker Products for UNIX versions of FrameMaker products. For the Macintosh and

Windows®versions, see the chapter on templates in your user manual.

Current state and inheritance

A FrameMaker product has a MIF interpreter that reads and parses MIF files. When you open or import a

MIF file, the interpreter reads the MIF statements and creates a FrameMaker document that contains the

objects described in the MIF file.

WhentheinterpreterreadsaMIF file,itkeeps trackofthecurrentstateofcertainobjects.Iftheinterpreter

reads an object with properties that are not fully specified, it applies the current state to that object. When

an object acquires the current state, it inherits the properties stored in that state.

Forexample,ifthelinewidthissetto1pointforagraphicobject,theinterpretercontinuestousea1-point

linewidthforgraphicobjectsuntilanewvalueisspecifiedintheMIFfile.Similarly,iftheMIFfilespecifies

a format for a paragraph, the interpreter uses the same format until a new format is specified in the file.

The MIF interpreter keeps track of the following document objects and properties:

•Units

•Condition tag properties

•Paragraph format properties

•Character format properties

•Page properties

•Graphic frame properties

•Text frame properties

•Fill pattern

•Pen pattern

•Line width

•Line cap

•Line style (dash or solid)

•Color

•Text line alignment and character format

Because the interpreter also provides default objects for a document, the current state of an object may be

determined by a default object. For example, if a document does not provide any paragraph formats, the

interpreter applies a set of default paragraph properties to the first paragraph. Subsequent paragraphs use

the same properties unless otherwise specified.

10ADOBE FRAMEMAKER 6.0

Introduction

How a FrameMaker product identifies MIF files

A MIF file must be identified by a or statement at the beginning of the file; otherwise a FrameMaker

product simply reads the fileas a text file. All other statements are optional; that is,a valid MIF file can

contain only the statement. Other document objects can be added as needed; a FrameMakerproduct

provides a set of default objects if a MIF file does not supply them.

MIF statement syntax

The statement descriptions in this manual use the following conventions to describe syntax:

tokendatawhere token represents one of the MIF statement names (such as ) listed in the MIF statement

descriptions later in this manual, and data represents one or more numbers, a string, a token, or

nested statements. Markup statements are always delimited by angle brackets (<>); macro statements

are not. For the syntax of macro statements, see “Macro statements” on page 70.

A token is an indivisible group of characters that identify a reserved word in a MIF statement. Tokens in

MIF are case-sensitive. A token cannot contain white space characters, such as spaces, tabs, or newlines.

For example, the following MIF statement is invalid because the token contains white space characters:

When the MIF interpreter finds white space characters that aren’t part of the text of the document (as in

the example MIF statement, ), it interprets the white space as tokendelimiters. Whenparsing the example

statement, the MIF interpreter ignores the white space characters between the left angle bracket (<) and

thefirstcharacterofthetoken,.Afterreadingthetoken,theMIFinterpreterchecksitsvalidity.Ifthetoken

is valid, the interpreter reads and parses the data portion of the statement. If the token is not valid, the

interpreter ignores all text up to the corresponding right angle bracket (>), including any nested substate-

ments. The interpreter then scans the file for the next left angle bracket that marks the beginning of the

next MIF statement.

Allstatements,aswellasalldataportionsofastatement,areoptional.Ifyoudonotprovideadataportion,

the MIF interpreter assigns a default value to the statement.

Statement hierarchy

Some MIF statementscan contain otherstatements.The containedstatementsarecalled substatements. In

this manual, substatements are usually shown indented within the containing statements as follows:

<Document

The indentation is not required in a MIF file, although it may make the file easier for you

to read.

A MIF main statement appears at the top level of a file.A main statement cannot be nested within other

statements. Some substatements can only appear within certain main statements.

Thestatementdescriptionsinthismanualindicatethevalidlocationsfor asubstatementbyincludingitin

allofthevalidmainstatements.Mainstatementsareidentifiedinthestatementdescription;forthecorrect

order of main statements, see “MIF file layout”on page 66.

Table des matières

Autres manuels Adobe Logiciel

Adobe

Adobe 26001648 - Illustrator CS3 Manuel utilisateur

Adobe

Adobe AFTER EFFECTS CS3 Manuel utilisateur

Adobe

Adobe 38040334 - Dreamweaver CS3 Manuel utilisateur

Adobe

Adobe 65018518 - Flash CS4 Professional Mode d’emploi

Adobe

Adobe KEY008 Guide de référence

Adobe

Adobe FLASH PLAYER 10 Manuel utilisateur

Adobe

Adobe 65009333 - InCopy CS4 - PC Mode d’emploi

Adobe

Adobe 29180248 - Photoshop Elements 5.0 Manuel utilisateur

Adobe

Adobe 38039336 - Flash CS3 Professional Manuel de référence

Adobe

Adobe PREMIERE 5 Manuel utilisateur

Adobe

Adobe PAGEMAKER 6.5 - Guide d'installation

Adobe

Adobe 13101332 - Photoshop - Mac Manuel utilisateur

Adobe

Adobe 25510629 - After Effects CS3 Professional Manuel utilisateur

Adobe

Adobe CAPTIVATE 5 Guide de référence

Adobe

Adobe PHOTOSHOP CS2 Manuel utilisateur

Adobe

Adobe 65019371 Guide de référence rapide

Adobe

Adobe 65029940 - Captivate - PC Mode d’emploi

Adobe

Adobe 22020737 - Acrobat Pro - PC Fiche technique

Adobe

Adobe 65015459 - Contribute CS4 Manuel utilisateur

Adobe

Adobe 65015459 - Contribute CS4 Manuel utilisateur

Adobe

Adobe GOLIVE CS2 Manuel utilisateur

Adobe

Adobe ILLUSTRATOR 10 Instructions d'installation et d'utilisation

Adobe

Adobe 38000511 - Macromedia Flash Basic Manuel utilisateur

Adobe

Adobe 65036570 - Director - PC Manuel utilisateur

Manuels Logiciel populaires d'autres marques

COMPRO

COMPRO COMPROFM Manuel utilisateur

Muratec

Muratec OFFICEBRIDGE ONLINE Manuel utilisateur

Oracle

Oracle Contact Center Anywhere 8.1 Manuel utilisateur

Avaya

Avaya NULL One-X for RIM Blackberry Manuel utilisateur

HP ProLiant BL420c Manuel utilisateur

PS Audio

PS Audio PowerPlay Manuel du propriétaire

Brady

Brady LOCKOUT PRO 3.0 Manuel de service

Avaya

Avaya Interaction Center Manuel utilisateur

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Manuel

Novell

Novell GROUPWISE 8 - INTERNET AGENT Manuel utilisateur

Oracle

Oracle Application 9i Manuel utilisateur

Acer

Acer RDM Manuel utilisateur

Canon

Canon Vixia HF21 Manuel utilisateur

Canon

Canon ZR950 Manuel utilisateur

Samsung

Samsung Auto Backup Manuel utilisateur

Polycom

Polycom Vortex EF2201 Instructions d'installation et d'utilisation

Brocade Communications Systems

Brocade Communications Systems Brocade 8/12c Manuel utilisateur

Novell

Novell SP2 - S Mode d’emploi