All framemaker headings are associated to robohelp heading 1 and it is set to pagination. However, n

[nelleharpo]

All framemaker headings are associated to robohelp heading 1. RH heading 1 is set to pagination. However, not all headings are separate html topics. It seems random, some are separate topics and some are not. In one case when I re-ordered the headings in framemaker that fixed the problem. However, I cannot do that in all cases. Does anyone know why they would not be producing separate html topics?

[Jeff_Coatsworth]

Are you importing or linking? What level of FM & RH? Are you sure that they are all Heading1 paragraphs - not just overrides of other formats that appear to look like Heading1's?

[nelleharpo]

frame 10/RH 9. I have one frame book linked in RH. In frame I have the headings set to different paragraph styles. In RH have assigned all the frame heading styles to heading 1.

[Jeff_Coatsworth]

Ok, but the pagination is based on the FM paragraph, not what you've mapped the paragraph to in RH. If you've said paginate on Heading1, then only those paragraph formats with Heading1 in FM will be split. You either have to select more paragraph formats to paginate on or maybe switch to using a FM marker to indicate to RH where to bust up the FM doc.

[nelleharpo]

Didn't work. 😞 I assigned frame heading 2 to RH heading 2 and set RH heading 2 to paginate. Received same results as when I had frame heading 2 assigned to RH heading 1. Remember, I mentioned this is not consistent throughout. In some cases my frame heading 2's are paginated when assigned to RH heading 1. Any other suggestions? I appreciated the assistance.

[Jeff_Coatsworth]

Post a screen shot (use the camera icon in the web interface) to show us what your Conversion Settings screen is set to. I'm not seeing what you're getting at all. There's no telling what RH style to paginate on, it's only which FM paragraph format to break at.

Secondly, have you looked at your FM docs where it did and didn't break at? Is there something different about places where it didn't paginate?

[nelleharpo]

All the frame headings (except for 5 and 6) are set to paginate and assigned to RH heading 1.

I cannot find any differences in places where it did not paginate. Believe me, I've been looking...:-)

[Jeff_Coatsworth]

So you've verified that the Heading2's in the FM doc are really Heading2 and not something that looks like a Heading2 (i.e. has a local override)?

Just for a test, try creating a new blank project (which should be in your root c:\projects\project_name\ folder, right?) and do an import of the offending FM docs - set your Conversion settings exactly the same as you did for your linked project and see what happens.

[nelleharpo]

100% no overrides. I try to avoid overrides like the plague.

Test results:

New project, linked frame files, imported settings. same result.

New project, linked frame files, set conversions manually on headers ony (did not set any other style conversions), pagination worked.

So, not quite sure this tells me what the problem is, except that it doesn't like something in my conversion settings. I set the headings in the new project the same as they were in the old project.

[Matt-Tech Comm Tools]

Did you try removing everything around that heading and replacing with new content?

I'm thinking that there's something odd in there (marker, manual page break, corruption) that might be causing pain.

Also, did you try saving file to MIF and then opening back into FM? That process (referred to as a MIF wash) may resolve your curious results.

-Matt

@mattrsullivan

[nelleharpo]

Yes. I looked all around. Added new context before and after. deleted. checked for markers, page breaks, etc....nothing.

Tried the MIF wash, no luck. 😞

[nelleharpo]

I just noticed this message from the MIF wash. Does it mean anything to anyone?

MIF: "C:\Documents and Settings\serboji\My Documents\BAMS\MST\Help files\02_MST Procedures\Build Scenario.mif" (5300): Value of Separation out of range (12).

[Jeff_Coatsworth]

Hmm, interesting - any way you can share your source FM files and settings.isf file from RH? It would be interesting to see if I could reproduce what's happening.

[nelleharpo]

Wish I could because I would love the help. However, they contain company proprietary information. Thanks for the offer.

[Matt-Tech Comm Tools]

So it sounds like your .isf is where the problem lies...try moving your current settings out, and starting anew.

If that doesn't work, you might want to burn 1/2 hour and create a new RH project. Since you know that a fresh project was working properly, that may be the best solution.

BTW, haven't seen that MIF wash error mssg. before

-Matt

@mattrsullivan

[nelleharpo]

Starting over was going to be a lot longer than a 1/2 hour, more like a whole day. I think I found the problem, but not sure why it's causing the undesired outcome. A few lines up in the doc I have a style called List1 and List1cont. There is nothing too unique about them except they are numbered L:(A=1) and L:(A+). If I change those lines to a different style (body), then all the headers paginate as desired. So....

Any idea how to get my lists back without messing up the pagination? Is there something wrong with my numbering scheme? Do I need to somehow reset A prior to the Heading?

[Jeff_Coatsworth]

So how are List1 and List1cont mapped? Are you paginating on them? What settings have you got for handling the Autonumbering?

[nelleharpo]

They are mapped to RH style bodylevel1. No pagination and I have selected "Convert Autonumber to HTML List"

[Jeff_Coatsworth]

I'd be tempted to experiment with them by setting them to "Convert Autonumber to Text" and see how that behaves, because, frankly, I've never heard of a FM list format having anything to do with a heading not paginating.

[nelleharpo]

Very interesting. If I set the List styles to Convert Autonumber to Text. The headers paginate. If it is set to Convert Autonumber to HTML the headers do NOT paginate.

[Jeff_Coatsworth]

Well, fire up the bug reporting! https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform