#### 27.8.1 Using PI markers for extract processing

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

Table 27-7 Predefined PI marker types for extracts

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

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

Previous Topic: 27.8 Customizing and replacing extracts

Next Topic: 27.8.2 Customizing title text for extracts

Parent Topic: 27.8 Customizing and replacing extracts

Sibling Topics:

27.8.2 Customizing title text for extracts

27.8.3 Replacing extracts with links in the parent file

27.8.4 Specifying extracts: an example

Table of Contents • Index