15.3.4.1 Assigning bookmap roles to FrameMaker files
To indicate the role and (if relevant) subrole that each file in your FrameMaker book should play in the <bookmap>:
; filename without .ext = role, one of Chapter (default), Part,
; Appendix, Front, Back, None (omit from map), or a *Seg directive.
Assign these roles to FrameMaker files as follows:
Divider for logical groups of chapters, either explicit or implicit |
||
The role (and subroles, if any) assigned to a FrameMaker file determine which element or elements are included in the bookmap for the DITA topic or topics generated from that file.
If you do not list in [DITABookmapFiles] a particular file in your FrameMaker book, Mif2Go includes that file in the bookmap based on file type (authored vs. generated) and on the position of the file relative to files that are listed. A non-generated file that occurs after the TOC (if any) becomes a <chapter> element.
Omitting all files from the list
If you do not list any files, the bookmap contains one entry for each FrameMaker file, with a <frontmatter> element for the FrameMaker TOC and a <backmatter> element for the FrameMaker IX. References to any other generated files appear in <frontmatter> or <backmatter> as <booklist> elements, based on their location in the FrameMaker book. All non-generated files become <chapter> elements, except for any preceding the TOC (such as a cover page), which become <topicref> elements in <frontmatter>.
Omitting a file from the bookmap
When filename=None, the file listed is not included in the bookmap.
> 15 Configuring DITA maps > 15.3 Constructing a DITA bookmap > 15.3.4 Mapping FrameMaker files to bookmap components > 15.3.4.1 Assigning bookmap roles to FrameMaker files
