Table of Contents
Advertisement
19
D e f a u l t t r a n s l a t i o n
If FrameMaker exports the single facet of a graphic element, the software exports the file
in the indicated format and uses the facet name as the notation name. In all other cases,
the software exports the file in CGM format and its notation name is CGM.
For example, assume you have an instance of the Graph graphic element that contains
graphics you created with FrameMaker's graphics tools. By default, the software creates the
following markup entity for it:
<!ENTITY graph1 SYSTEM "graph1.cgm" NDATA cgm>
Also, the entity attribute of the graphic element has a value of graph1 to correspond
with the above entity.
On import to FrameMaker
In the absence of read/write rules, FrameMaker cannot identify the elements and attributes
of a markup document that correspond to a graphic or equation. Therefore, it translates
them as container elements in the EDD. You must supply rules and perhaps a structure API
client to reflect the appropriate structure.
If your DTD uses the default graphic and equation declarations described in the preceding
sections, the only rule you need is one to identify the element as a graphic or equation. If
you do so, the attributes translate automatically. The translation occurs either if you started
by creating your DTD from an EDD or if you started with an existing DTD without
declarations for graphics or equations and added the default declarations. For a description
of these declarations, see "Text of default graphics and equations declarations" on
page 300.
Your markup document can use either the entity attribute or (for SGML) the file
attribute to specify a graphic or equation. If a single element has specified values for both
attributes, the software uses the value of the entity attribute, ignoring the value of the
file attribute. FrameMaker accepts the name of any external data entity as a value for
entity, regardless of whether the entity is declared to be CDATA, SDATA, or NDATA.
Importing graphic entities
If the graphic element in markup uses the entity attribute to identify the graphic file, then
the actual graphic file must be identified in an entity declaration. FrameMaker will read the
markup, importing the graphic file by reference into an anchored frame. If the entity
declaration is not in the main DTD, then it should be in the document's internal DTD subset.
In that case, FrameMaker saves information about the entity declaration on the Entity
Declarations reference page of the resulting document.
The software saves the entity name with the imported graphic inset. The software uses the
entity name, plus the information on the Entity Declarations reference page, to recreate
entity declarations when exporting to markup. For graphic entities the software can use the
same graphic file for import and export under most circumstances. For information about
exporting entity declarations, see "Exporting entity declarations" on page 305. For
Structure Application Developer's Guide
307
Advertisement
Table of Contents
