Adobe 65030365 - FrameMaker - PC Developer's Manual page 422

26
g e n e r a t e b o o k
gi
j
fname
j
Details
• By default, when reading a markup document into FrameMaker, the software uses the
<?FM book ?> and <?FM document ?> processing instructions to indicate the start
of a book and of its components. The following rule confirms this default behavior:
reader generate book
• Your DTD may be defined so that you can use elements to indicate the start of a book
and its components. When you use the second form of the generate book rule,
FrameMaker creates a book for every markup document you translate. When you use
the third form of the generate book rule, it creates a book only for markup documents
whose DTD specifies the document type you've listed in the rule. If you have a markup
document with a different document type, FrameMaker translates that document as a
single FrameMaker document, even if it contains elements referenced in put element
rules. For example, assume you have this rule:
reader generate book for doctype "manual"
If you translate a markup document whose highest-level element is report, that
document becomes a single FrameMaker document, even if it contains chapter
descendant elements.
•
When it encounters one of the gi
FrameMaker starts a new book component. Since the software does not allow an
element to be broken across files, it places the entire gi
if another element appears that you've said should start a new file. To illustrate, assume
the section element can occur either within or outside of a chapter element and you
have this rule:
reader generate book {
}
When FrameMaker encounters a chapter element, it starts a new file. If it encounters
a section element as a child of that chapter element, it does not start a new file. It
continues with the file started by the chapter element. On the other hand, if the software
encounters a section element outside a chapter element it does start a new file for it.
Read/Write Rules Reference
A generic identifier.
A filename for the book component. FrameMaker adds a counter to
the name (before the suffix if there is one) as needed, to generate a
unique filename. You can use the $(bookname) variable to base the
component's filename on the book filename (excluding any suffix). If
you do not supply this argument, the filename is gi
use processing instructions;
put element "chapter" in file;
put element "chapter" in file;
put element "section" in file;
elements specified in a put element subrule,
j
j
.doc.
j
element in the same file, even
404