### 18.7.1 Using marker s for extract processing

You can use predefined marker types to supply most extract-file properties. Table 18-7 lists the predefined marker types for extracts.

Table 18-7 Predefined marker types for extracts

Marker type | Purpose | Content use | Placement | Ref.
ExtrBottom | Insert HTML code | Last item in extract <body> | Anywhere in the extract* | 18.5.1
ExtrDisable | Turn off extract processing | Ignored | After all or a group of extracts | 18.3.1
ExtrEnable | Turn on extract processing | Ignored | Before all or a group of extracts | 18.3.1
ExtrEnd | End an extract; | Ignored | After end of last paragraph in extract, and before end of following paragraph | 18.3.2
ExtrFinish | Mark last part of extract | Ignored | In the last paragraph of the extract | 18.3.2
ExtrHead | Insert HTML code | Placed in extract <head> | Anywhere in the extract* | 18.5.1
ExtrReplace | Insert HTML code | Replaces extract in parent file | Anywhere in the extract* | 18.7.3
ExtrStart | Begins extract | Ignored | In the first paragraph of the extract; can be used in [Extr*] sections | 18.3.2, 18.5.3
ExtrTop | Insert HTML code | First item in extract <body> | Anywhere in the extract* | 18.5.1
* To avoid maintenance headaches, pick a consistent location, such as at the start of the first paragraph.

You can also use any of the Extr* marker-type names listed in Table 18-7 as properties of other markers; see §29 Working with FrameMaker markers for more information.

Mif2Go processes every marker that has the same name as an [HtmlStyles]Extr* property the same way as that property. Properties assigned via markers take precedence over the same properties assigned via formats; see §18.5.1 Choosing how to insert code in extracts.

| 18.7 Customizing and replacing extracts |  | 18.7.2 Customizing title text for extracts |