Table of Contents
Advertisement
18
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
For information on writing format rules, see Chapter 10, "Text Format Rules for Containers,
Tables, and Footnotes."
Working with colspecs and spanspecs (CALS only)
You may use a table model that is essentially the CALS table model but you choose to
rename some of the elements, even in the DTD. If you do not use the default names for
the elements that represent colspecs and spanspecs, you need to let the software know
which elements to use.
The rules for identifying colspecs and spanspecs are:
element "gi" is fm colspec;
element "gi" is fm spanspec;
where gi is a generic identifier.
As usual with colspec and spanspec elements, the named markup element does not
become an element in FrameMaker when you use these rules. Rather, its attributes are
used in the creation of the table element.
For more information on these rules, see "element" on page 376, "is fm colspec" on
page HIDDEN, and "is fm spanspec" on page HIDDEN.
Specifying which part of a table a row or cell occurs in
In markup your table may not have elements for rows or particular table parts such as the
heading or body. Instead, the element type of a table row or cell may determine what part
of the table the element goes in. For example, an element named hrow might only be used
for a row in the heading of a table. You might not have a separate element for the heading.
If a table row does not occur inside a specified table part, the software assumes the row
belongs in the table body by default. You can change this behavior using the following rule:
element "gi" {
is fm table row_or_cell element;
fm property row type value is "part";
}
where gi is a generic identifier; row_or_cell is one of the keywords row or cell; and
part is one of Heading, Body, or Footing.
For an example of the use of these rules, see "Omitting explicit representation of table parts"
on page 285.
For more information on these rules, see "element" on page 376, "is fm table part element"
on page 436, and "fm property" on page 399.
Structure Application Developer's Guide
283
Advertisement
Table of Contents
