#### 20.3.2.1 Specifying links to include in local TOCs

To specify which subordinate split files to list in a local TOC, you assign a level number to each of the FrameMaker paragraph formats (usually headings) that designate split points in your document. In other words, you assign a level number to each paragraph format to which you have assigned the [HTMLParaStyles]Split property (see §18.2.1 Designating split points):

[LocalTOCLevels]

; If this section is missing, [HelpContentsLevels] is used instead.

; Only formats for which [HTMLParaStyles] Split is set are recognized:

; paraformat = level, from 1 to anything; 0 to exclude from local TOC

For example, if you split at Heading1, Heading2, HeadProc (which is at the same hierarchical level in your document as Heading2), Heading3, and AppxHead1, you could specify the following settings:

[LocalTOCLevels]

Heading1=1

Heading2=2

HeadProc=2

Heading3=3

AppxHead1=0

In this example:

• Each Heading1 split file would have a local TOC consisting of links to all subordinate Heading2 and HeadProc split files.

• Each Heading2 split file and each HeadProc split file that has subordinates would have a local TOC consisting of links to all subordinate Heading3 split files (if any).

• AppxHead1 split files would not have local TOCs.

In the [LocalTOCLevels] section, list only paragraph formats that are also split points (have been assigned the [HTMLParaStyles]Split property), and make sure your level number series starts with 1. Otherwise, you might get unwanted blank topics.

If you omit a [LocalTOCLevels] section, Mif2Go includes instead any split-point paragraph formats listed in [HelpContentsLevels]. Paragraph formats not listed in either section are ignored.

Note: For any of these settings to take effect, you must enable local TOCs; see §20.3.1 Directing Mif2Go to generate local TOCs.

| 20.3.2 Configuring local TOCs |  | 20.3.2.2 Providing HTML code before and after local TOCs |