17.8 Overriding DocBook settings with markers

You might need to insert markers in your FrameMaker document to override configuration settings for particular DocBook elements. Mif2Go provides predefined marker types for this purpose, listed in Table 17-2. Most of these marker types are intended to provide ways to cope with unusual situations. If you have a consistent template, and use normal FrameMaker cross references and hypertext links, for the most part you can get by with just configuration settings.

Table 17-2 Predefined marker types for DocBook

marker type	Content	Ref.
DocBookAlias	Alternate name for FrameMaker format for the current block	17.4.2.5
DocBookAttribute	Attributes other than ID of a non-<xref> block element or parent	17.4.5.1
DocBookCloseAfter	Ancestor elements to be closed just after current block element ends	17.5.8.2
DocBookCloseBefore	Ancestor elements to be closed just before current block element starts	17.5.8.1
DocBookCode	XML code to be inserted at the marker location
DocBookElemID	ID attribute for the current block element	17.4.4.4
DocBookEndElem	Tag name for an inline element, to place at the end of the span	17.4.3.3
DocBookFirst	Ancestor elements under which the current block element must be first	17.5.6
DocBookLevel	Level where the current block element should appear in the DocBook file	17.5.11
DocBookOpenAfter	Elements to be opened just after current block element ends	17.5.9.2
DocBookOpenBefore	Enclosing elements to be opened just before current block element starts	17.5.9.1
DocBookParent	Required ancestors for the current block element	17.5.2
DocBookParentID	ID of the interpolated parent of the current block element	17.4.4.4
DocBookStartElem	Tag name for an inline element, to place at the start of the span	17.4.3.3
DocBookTag	Element name mapping for the current block (not inline) element	17.4.2.4

17.7.3 Omitting size attributes from images for DocBook

18 Splitting and extracting files