Skip to main content
Participating Frequently
August 16, 2018
Answered

Losing Page Breaks in FM2015. Suggestions?

  • August 16, 2018
  • 1 reply
  • 493 views

We are losing page breaks during file generation (TOC, List of Figures) or adding of index tags in FrameMaker 2015. Suggestions?

We always place our tags at the end of the header or term, but that doesn't always make a difference. Those are easier to catch than when the breaks are lost during file generation.

This topic has been closed for replies.
Correct answer Bob_Niland

re: We are losing the page breaks in our chapters.

Anything that removes overrides will blow away PB overrides. It's always been my policy to never use the PB command (and avoid overrides generally).

Where I need certain paras to start at page tops, I'll spin off a variant catalog para tag for that purpose, perhaps ending up with:
Heading3
as well as
Heading3.top

Although, in general, I rarely need to do even that, preferring to rely on Keep With Next/Previous and Widow/Orphan attributes to implicitly accomplish the same thing.

1 reply

Bob_Niland
Community Expert
Community Expert
August 16, 2018

How are you implementing page breaks?

The legacy command to do this in FM,
Special > Page Break
now
Insert > Page Break
is actually potentially misleading, as what it does is to set, as an override, a Paragraph Pagination property.

This property is trivially lost if manually applied to generated content, such as in a TOC, LOF or IX.

Participating Frequently
August 16, 2018

We are using the Special > Page Break to add the page breaks.

I know when we regenerate files, any breaks in the TOC, LOF, or IX will be lost. We are losing the page breaks in our chapters. For instance, we like to have an Level 1 heading start at the top of the page, but sometimes will find the page break reverts back to "wherever it fits" instead of "top of next available page" when we generate the TOC at the book level.

Bob_Niland
Community Expert
Bob_NilandCommunity ExpertCorrect answer
Community Expert
August 16, 2018

re: We are losing the page breaks in our chapters.

Anything that removes overrides will blow away PB overrides. It's always been my policy to never use the PB command (and avoid overrides generally).

Where I need certain paras to start at page tops, I'll spin off a variant catalog para tag for that purpose, perhaps ending up with:
Heading3
as well as
Heading3.top

Although, in general, I rarely need to do even that, preferring to rely on Keep With Next/Previous and Widow/Orphan attributes to implicitly accomplish the same thing.