Table of Contents
Advertisement
14
C a s e c o n v e n t i o n s
A single subrule can appear at the end of a rule without the enclosing braces. For example:
element "list" {
attribute "indent" drop;
}
is equivalent to
element "list" attribute "indent" drop;
Null rules, consisting simply of a semicolon, can appear wherever a rule is allowed.
Case conventions
For keywords of the read/write rules syntax, case is not significant. For example, the
following are equivalent for rules in a structure application:
fm version is "7.1";
FM Version is "7.1";
To improve readability, this manual sometimes uses mixed case for keywords.
The case of FrameMaker element tags and other FrameMaker names is always significant.
Thus, the following rules are not equivalent:
fm element "Default Element" drop;
fm element "default element" drop;
The significance of the case of SGML names is dependent on the NAMECASE parameter of
the SGML declaration. For XML the case is always significant, and your rules must match
the case used in the XML markup. For more information, see "Naming elements and
attributes" on page 231.
Strings and constants
You use strings to specify FrameMaker element tags, generic identifiers in markup, attribute
names, attribute values, entity names, notation names, and so on.
String syntax
Strings are enclosed in matching straight or directional double quotation marks. Strings
cannot extend across more than one paragraph.
To incorporate special characters into strings, use the following conventions:
•
\x followed by one or two hexadecimal digits is interpreted as a hexadecimal character
code.
•
\0 (backslash zero) followed by one or two octal digits is interpreted as an octal
character code.
Read/Write Rules and Their Syntax
212
Advertisement
Table of Contents
