Table of Contents
Advertisement
19
Translating Graphics and
Equations
FrameMaker provides a set of tools for creating graphics or equations. It also provides tools
for importing graphic objects created with another software package into a FrameMaker
document. Markup, on the other hand, does not standardize the representation of either
graphics or equations; each DTD can treat them differently.
In FrameMaker equations are very similar to graphics. Both are placed within anchored
frames, and the anchored frames contain one or more objects-for graphics these are
graphic objects, and for equations they are terms of the equation. In the context of structure
and import/export of markup, an equation is treated as a single graphic object within an
anchored frame. FrameMaker does nothing to represent the equation's terms as any type
of structure. You cannot use rules to describe the internal structure of equations. However,
you can write a structure API client to support a completely different model for equations
(such as MathML).
FrameMaker has a default set of element and attribute definition list declarations for
representing graphics and equations as elements. You can use read/write rules to support
variations of the default representation, whether you start with an EDD or a DTD.
In this chapter
This chapter describes how FrameMaker translates graphics and equations and how you
can change that translation. In the outline below, click a topic to go to its page.
How FrameMaker translates graphics and equations by default:
•
•
Some ways you can change the default translation:
•
•
•
•
•
•
•
Structure Application Developer's Guide
"On export to markup" on page 300
"On import to FrameMaker" on page 307
"Exporting graphic and equation elements" on page 309
"Representing the internal structure of equations" on page 311
page 313
"Specifying the data content notation on export" on page 313
19
297
Advertisement
Table of Contents
