Table of Contents
Advertisement
21
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
Translating FrameMaker variables as SDATA entities
For SGML, you can translate FrameMaker variables as SDATA entities by using the entity
rule or by manipulating parameter literals. For information on how to do so, see "Translating
entities as FrameMaker variables" on page 259.
Discarding FrameMaker variables
FrameMaker always allows you to insert a variable in a document. To modify this behavior,
you must use an FDK client. If you don't want FrameMaker to export some or all variables
to markup, you can choose to have it discard all variables or particular variables.
To have FrameMaker discard variables, use this rule:
fm variable ["var
", . . ., "var
"] drop;
1
n
Each var
is a variable. If you don't specify var
in the rule, the rule applies to all variables
i
i
not addressed explicitly by entity or other fm variable rules. It is an error if the same
appears in multiple entity or fm variable rules.
var
i
This rule always occurs in a highest-level rule, because it applies to all instances of the
indicated variables. It does not apply to system variable elements.
For information on the rules used in this example, see "writer" on page 467, "fm variable"
on page 402, and "drop" on page 373.
Translating Variables and System Variable Elements
334
Advertisement
Table of Contents
