Table of Contents
Advertisement
17
M o d i f i c a t i o n s t o t h e d e f a u l t t r a n s l a t i o n
Facilitating entry of special characters that translate as entities
XML: The XML specification allows UNICODE in XML. This section is for SGML,
only.
Your end users do not need to know the details of the entity names or definitions used to
represent special characters within a FrameMaker document. They can simply insert any
special character into the document and have FrameMaker automatically translate the
characters back and forth to the corresponding entity references.
However, you may want to provide a special interface for inserting these characters. You
can create a hypertext palette for this purpose.
You build a hypertext palette for inserting special characters with whatever layout you want.
Below each active region representing a special character within the palette, you store a
hypertext command to have FrameMaker insert the appropriate entity. This hypertext
command has the following form:
message FmDispatcher insert entity ename
where ename is the entity name. When your end user clicks on a particular character within
the palette, the hypertext message is sent to FrameMaker requesting the insertion of an
entity with the given name. FrameMaker determines what to insert on the basis of current
read/write rules and the entity declaration. This could result in inserting, for example, a
special character, an SDATA variable, or a text inset.
Note that FrameMaker can insert the document objects you specify for these entities,
whether or not there is a matching entity declared in the DTD. You should be sure to declare
a matching entity for each document object. Without an entity declaration, on export the
software cannot convert the object into a DOC Entity Reference.
For more on creating hypertext documents, see the information about hypertext documents
in the FrameMaker User Guide.
Creating book components from general entities
You can break large documents across multiple files and manage those files with a single
document containing general entity references in markup, and with a book file in
FrameMaker. For information on this use of general entities, see Chapter 24, "Processing
Multiple Files as Books."
Discarding unknown processing instructions
By default, FrameMaker imports processing instructions it does not understand as markers
of type DOC PI. (In previous versions of FrameMaker, these were Type 11 markers.) You
can choose to have it discard these processing instructions instead. To do so, use the
following highest-level rule:
processing instruction drop;
Translating Entities and Processing Instructions
268
Advertisement
Table of Contents
