#### 18.2.2.1 Preventing splits that create unwanted files

Suppose each of your FrameMaker chapters begins with a paragraph tagged ChapHead, followed by a Heading1 paragraph. Suppose you use Heading1 as a split point, and the ChapHead paragraph merely provides formatting or decoration on the chapter title page. The output will include an HTML file named for the chapter file; and that non-empty file will be included in any browse sequence.

To eliminate the unwanted paragraphs, you have the following choices:

Assign both Split and Delete

Apply a condition in FrameMaker.

Assign both Split and Delete

Assigning format property Delete to ChapHead would eliminate paragraph content; also assigning format property Split would allow you to use SmartSplit:

[HtmlStyles]

ChapHead = Split Delete

Heading1 = Split

You must set SmartSplit=Yes and assign appropriate level numbers, as described in §18.2.2.2 Preventing splits that leave dangling headings, to get rid of the unwanted file. You will not be able to give the first split file a name different from the FrameMaker chapter file.

Apply a condition in FrameMaker

Instead, you could use conditional text in FrameMaker to mark ChapHead paragraphs for hiding. For example, apply a condition named HeadStuff to each ChapHead paragraph, and in your configuration file specify the following:

[Setup]

SetFrameConditions = Yes

[ConditionsShown]

HeadStuff = No

See §5.4.1 Applying condition Show/Hide settings.

See also:

§18.6 Referencing split and extract files

§21.3.13 Eliminating unwanted paragraphs

| 18.2.2 Managing split points |  | 18.2.2.2 Preventing splits that leave dangling headings |