Table of Contents
Advertisement
Example of graphic inset file
The following example is the external graphic inset file generated by the fmbitmap program, which is
shipped with the UNIX version of the FDK.
The graphic inset file is named /tmp/default.fi. The application-specific facet for this graphic inset (the file
generated by the fmbitmap program) is stored in a remote facet in the file /tmp/default.
Note that although the fmbitmap program writes out the ImportObFile statement, this statement is
obsolete and is only used with older versions of FrameMaker products. When defining a function to write
a graphic inset file, use the ImportObFileDI statement and specify a device-independent pathname. For
more information on device-independent pathnames, see "Device-independent pathnames" on page 13.
<MIFFile 6.00> # Generated by fmbitmap
<ImportObject
<ImportObFile /tmp/default.fi>
<ImportObEditor fmbitmap>
=BitmapFile.facet
&%v
&/tmp/default
=Data.facet
&%i
&64
&64
&-1
&-1
=FrameImage
&%v
&\x
& ...
&\x
=EndInset
>
To see more examples of the graphic inset format, you can import a graphic into a FrameMaker document
(import by copying) and save the FrameMaker document as a MIF file.
General rules for reading and writing facets
To write a facet, you need to modify the existing function in your application for writing data. The function
must write the facet name and data type lines and insert an ampersand at the beginning of each line of facet
data. If necessary, convert data lines to the appropriate facet data format. Unsigned bytes should follow the
conventions described in "Unsigned bytes" on page 271, and metric data should follow the conventions
described in "Metric data" on page 272.
When writing the facet data, your application can use as many lines as necessary. Each line should be short
enough to read with a text editor, in case you need to debug the graphic inset file. There are no counts,
offsets, or facet size limits.
ADOBE FRAMEMAKER 6.0
278
Facet Formats for Graphics
Advertisement
Table of Contents
