Have you read about / played with deepcontentsplitting? Ideally you don't
want to change this setting from its default, it's pretty complex and had a
lot of bugs associated with it early on. (I can't remember when it settled
down.) Also, I have this vague recollection it might interact with another
setting ... anyhow, until someone shows up with something more specific,
that's where I'd start looking.
On Wed, Jan 25, 2012 at 12:30 PM, Joseph Migliore
<->wrote:
> Adepters,
>
>
>
> Having a table entry and page overrun issue using a FOSI on Arbortext 5.2
> with Print Composer. Our customer requires that table entries be contained
> on a page and not be allowed to span across page boundries. By placing a
> keeps on the entries in the fosi, the entries will (correctly) not span
> across pages. However, we are having a serious side effect. When the entry
> (that would have spanned the page boundry) begins on the following page, it
> overruns the text on that page. In other words, it appears the text from
> the entry element is layed on top of the existing text on the page.
>
>
>
> Any suggestions?
>
