In This Chapter - Adobe 65030365 - FrameMaker - PC Developer's Manual

17
Translating Entities and Processing
Instructions
Entities in markup serve a variety of functions in markup documents. These functions can
be represented in widely different ways in FrameMaker. FrameMaker does not have a single
construct that corresponds with entities in markup. For information on common uses of
entities, see "Entities" on page 17.
Processing instructions (PIs) in markup provide a mechanism for invoking system-specific
actions from within an XML or SGML document. These actions can be almost anything. By
default, FrameMaker interprets a small number of processing instructions. It stores others
in the document as markers-you can write an FDK client to process them at any time in
the authoring cycle. You can also use a structure API client to trap processing instructions
and perform specific actions as the parser encounters them.

In this chapter

This chapter discusses the default translations used by FrameMaker for processing
instructions and for entities of various kinds. The chapter also provides general information
on how you can modify these translations. Subsequent chapters discuss further
modifications appropriate to translating particular FrameMaker constructs such as variables
or books. For information on the processing instructions used for conditional text, see
Chapter 23, "Translating Conditional Text."; for those used for books and book components,
see Chapter 24, "Processing Multiple Files as Books." In the outline below, click a topic to
go to its page.
How FrameMaker translates entities and processing instructions by default:
•
•
Some ways you can change the default translation:
•
•
•
•
•
•
•
Structure Application Developer's Guide
"On export to markup" on page 248
"On import to FrameMaker" on page 251
"Specifying the location of entity declarations" on page 258
"Renaming entities that become variables" on page 258
"Translating entity references on import and export" on page 258
"Translating entities as FrameMaker variables" on page 259
"Translating SDATA entities as special characters in FrameMaker" on page 260
"Translating SDATA entities as FrameMaker text insets" on page 262
"Translating SDATA entities as FrameMaker reference elements" on page 263
17
247