Table of Contents
Advertisement
10
W r i t i n g c o n t e x t - d e p e n d e n t f o r m a t r u l e s
For example, suppose you want to apply a formatting change to an Item when it appears
inside a nested List element (a List inside a List). If you put the context specifications
for the Item in the following order, FrameMaker would never apply the second clause
because an Item in a nested List also matches the first specification:
List
List < List
You get the effect you want by reversing the clauses.
Level rules
When defining the nesting depth of an element within levels of another element, you may
find it easier to use a level rule rather than a normal context rule. In a level rule, you name
the ancestor to the current element and then in each clause count the number of times the
ancestor appears above the current element.
For example, suppose you're describing the nesting depth of a Head in Section elements.
This is how you would define it using a normal context rule:
Element (Container): Head
General rule: <TEXT>
Text format rules
This is the same specification using a level rule instead:
Text format rules
Note that in context rules you need to go from the lowest level to the highest, but in level
rules the order of clauses is arbitrary so you can go from highest to lowest if you prefer. In
Text Format Rules for Containers, Tables, and Footnotes
1. If context is: Section < Section < Section
Default font properties
Font size: 12
Else, if context is: Section < Section
Default font properties
Font size: 14
Else, if context is: Section
Default font properties
Font size: 18
1. Count ancestors named: Section
If level is: 1
Default font properties
Font size: 18
If level is: 2
Default font properties
Font size: 14
If level is: 3
Default font properties
Font size: 12
138
Advertisement
Table of Contents
