Pagination Problems - Keep With: Next Pgf/Previou Pgf & Widow/Orphan Lines

Forum|Forum|15 years ago
March 1, 2011
2 replies
3748 views

I'm using FM 9.0p237 on a PC running Windows 7 Ultimate 32-bit.

Recently I needed to introduce special formatting for page breaks into a 200+ page document. I used the settings in the Pagination section ofthe Paragraph Designer, both the "Keep With: Next/Previous Pgf" and "Widow/Orphan Lines" settings. In my initial tests they seemed to work fine. However, now that I'm actually implementing changes in real documentation with them, they are extremely buggy.

Neither tool effects the changes it should.

In the case "Widow/Orphan Lines," when I change the number in the dialogue box, it does change the placement of the paragraphs to which they are applied, but not using the specified number.

The problem with "Keep With: Next/Previous Pgf" is more troubling. Firstly, I don't see that these settings take effect at all when applied. Secondly, once the tick boxes have been checked, I am unable to remove the checks/settings. I untick them and try to apply the new settings, but the ticks reappear every time.

This is an extreme problem. I'm using FM in a corporate environment and am on a tight deadline to deliver this documentation with a parallel software release. Any help is appreciated.

Douglas

This topic has been closed for replies.

Bob_Niland

Community Expert

Assuming this isn't a bug in FM9, keep an eye on the Pagination attributes of paragraphs just ahead and behind the ones that are misbehaving.

If the Keep With ticks are in conflict, or the resulting kept object won't fit on a page, the results can be non-intuitive.

Douglas_CampbellAuthor

Inspiring

I understand what you're saying about the Pagination attributes of the paragraphs before and after the one I'm trying to change. I think what you're describing might be the issue. I'm testing this out on the same element in structured FM, it is a simple paragraph. Assuming this is the issue, I thought that maybe making the change and then trying to apply it globally in commands before using just "Apply" localally might allow for a workaround, but it did not. Do you have to use the Apply button before using Commands/Global Update Options?

This makes more sense now, too, because I had similar issues when testing this out in a short document and at that time I had to erase all the elements and reauthor them to get the changes to take effect. That was an acceptable workaround when I was tinkering, but I'm trying to implement these changes in 200 pages of professional IT documentation. Does that mean I'll have to reauthor everywhere I want such changes?

Bob_Niland

Community Expert

I thought that maybe making the change and then trying to apply it globally in commands before using just "Apply" localally might allow for a workaround, but it did not. Do you have to use the Apply button before using Commands/Global Update Options?

I'm not following. [UpdateAll] is its own button in 7.1, and not in the Commands: pull-down.

Keep in mind that although I have FM9 available, I work in 7.1 unstructured.

______

And I've never seen [UpdateAll] fail to work.

Jeff_Coatsworth

Community Expert

I'd update to the latest p version for FM9 (p255) first & then see if you are still having issues.

Douglas_CampbellAuthor

Inspiring

I patched up to p255, but the problem remains.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded