Need page break styles without making lots of new styles

[nickatwork]

Hi all,
I have quite a few styles in my stylesheet, multiple mediums etc.
I have been setting page breaks in some of my styles, and at times in the paragraph setting in the topic itself - this isn't perfect and I want to manage it with styles entirely.
Example, I have 3 P styles.
p_main
p_indent
p_note

now rather than making p_main_new_page, p_main_new_column etc etc for each style, meaning 6 new styles, is there any other way I can do this with using styles and without having to make a bunch of new styles etc...
I have set my orphan controls and page-break-inside rules but these dont always work perfectly, so I want to set it in a style so I know it works.

Any ideas?

Thanks,
Nick.

[i-tietz]

Two ideas:
1.
You could insert a paragraph before the one that's supposed to be at the top of the page.
You can set it to width: 1px, height: 1px, float: left and of course apply the relevant page-break-settings to it.

2.
THEORETICALLY browsers can interpret double classes correctly (I don't know for sure), but unfortunately Flare doesn't support that: You would have to open the topic in the text editor and insert the second class there.
For that purpose you could create a so called GENERIC class that you can assign to ANY element, something like .nextpage (please note the dot in front of the name!) The sourcce code would look ike this then:

Code: Select all

<p class="main nextpage">

YES, there's no dot before nextpage!

[techwriter31]

I have "PageBrkBefore" versions of most of my styles (for example, "p.PageBrkBefore"). I think styles are the way to go, but unfortunately means that you will have to add new styles.

Another option if you've got modular topics - in Flare 8, I started using the page break option in the TOC entries themselves, so it's more flexible for our various print outputs, and eliminates the need to modify the header page breaks in the topics themselves. This helps to reduce translation costs, because if the topic isn't modified, it doesn't get sent back to the translation vendor for the next revision.