18.2.2.3 Preventing splits that leave dangling headings
Suppose you have designated the following criterion for split points:
Now suppose your FrameMaker document has content organized as follows:
And you want split points as follows:
------------------- split here
------------------- split here
That is, you want to suppress a split between the first Heading1 and the first Heading2.
Instead of the first Heading2 you could use a different paragraph format that is not assigned the Split property, such as Heading2First, and add that format to the paragraph catalog. Or, you could use [HelpContentsLevels] to assign level numbers to your heading formats, and set SmartSplit=Yes:
; FM paragraph format name = TOC level (MS or Java)
; SmartSplit = No (default) or Yes (suppress splits in sequences of
; heads which lack text bodies, as long as the [HelpContentsLevels]
; values continue to increase)
You need StartingSplit=No to avoid creating a blank file; see §18.2.2.1 Preventing splits that leave empty files.
The effect of these settings is to suppress splits as long as the heading level number increases for each paragraph in an unbroken sequence of paragraphs. For example, these settings would keep all of the following together:
In other words, SmartSplit prevents splits when both of the following are true:
• the later heading is subordinate to the earlier heading
• there is no body content between headings (but see §18.2.2.4 Keeping headings together when other content intervenes).
Note: It is not a good idea to use SmartSplit in conjunction with trails of links; see §20.2.1 Understanding trails of links.
Note: It is not a good idea to use SmartSplit in conjunction with local TOCs; see §20.3 Including local TOCs.
> 18 Splitting and extracting files > 18.2 Splitting files > 18.2.2 Managing split points > 18.2.2.3 Preventing splits that leave dangling headings