Table of Contents
Advertisement
22
Translating Markers
You use markers in FrameMaker documents to store various kinds of information you don't
want visible to the document's audience. Although there's no analogous concept in markup,
markers frequently correspond to various attributes or elements.
FrameMaker provides a variety of marker types. Two of these marker types have special
default translations.
•
•
In this chapter
This chapter describes the default translation of markers and modifications you can make
to the default behavior. Some of these procedures are relevant when translating in both
directions; others are relevant only in one direction.
How FrameMaker translates markers by default:
•
•
Some ways you can change the default translation:
•
•
•
•
Default translation
Markup has no special representation for markers. FrameMaker allows you to represent
markers either as marker elements or as non-element markers.
Structure Application Developer's Guide
DOC PI markers store information about some processing instructions, and DOC Entity
Reference markers store information about entity references. For information on this use
of markers, see Chapter 17, "Translating Entities and Processing Instructions." You can
change which marker type FrameMaker uses to store this information.
Conditional Text markers indicate conditional text. FrameMaker ignores conditional text
markers on export to markup. For information on the treatment of conditional text on
export, see "Marked sections and conditional text" on page 23.
"On export to markup" on page 336
"On import to FrameMaker" on page 336
"Translating markup elements as FrameMaker marker elements" on page 337
"Writing marker text as element content instead of as an attribute" on page 337
"Using markup attributes and FrameMaker properties to identify markers" on page 338
"Discarding non-element FrameMaker markers" on page 339
22
335
Advertisement
Table of Contents
