Skip to main content
Douglas_Campbell
Inspiring
February 19, 2013
Question

Upgraded from RH9 > RH10, numbered lists from linked FM no longer work

  • February 19, 2013
  • 1 reply
  • 561 views

When we first decided to move from a FM>WebWorks workflow last year, I spent weeks trying to get our numbered lists to map correctly. Many forum posts and much expirimenting resulted in the following solution:

Under mapping options in File/Project Settings/FrameMaker Document/Edit I found our Step and Step1+ styles from FM and mapped them both to a new RH style called Step1. Under Autonumber in this dialogue box I chose Convert autonumber to: Multilevel list. Separately, in the RH style editor, I set up the parameters and styles for both Step1 and the Multilevel List.

This worked perfectly, with one exception: if there were two separate lists on the same page in FM, in RH the autonumbering did not restart. So, instead of 1,2,3 and 1,2,3 in FM, you'd get two lists numbered 1,2,3 and 4,5,6 in RH. It cost us so much to even get this to work, we swallowed the shortcoming for the time being, and submitted a bug to Adobe.

Fastforward to our recent upgrade to RH10. Now when we use the same mapping files as those described above, none of the numbering works. At first, all the numbers were 0. After a little fiddling, but not changing the settings, they are now all 1., as in 1, 1, 1, 1, etc.

This is disasterous. We still have some problems with the mapping that we have decided to work around, but this isn't one that we can live with. Our documentation is all task-based, so everything is numbered.

I've tried more variations than I could write here to resolve it, but nothing allows me to have the same control over it that I had previously achieved. I should mention, I don't want to use the Convert autonumber to text option, because the formatting is so awful, it makes the documentation unusable.

Insights and/or solutions would be very welcome.

Thanks,

Douglas

This topic has been closed for replies.

1 reply

Jeff_Coatsworth
Community Expert
Community Expert
March 6, 2013

If nothing else is working for you, you may end up having to use the "autonumber to text" option and then play around with your CSS to make it look right.

Douglas_Campbell
Inspiring
March 6, 2013

I've resigned myself to this option. But it seems inadequate given what these tools are supposed to be able to do.

Jeff_Coatsworth
Community Expert
Community Expert
March 6, 2013

If you’ve set up simple examples of the issues, I’d log bugs with Adobe and submit them – that would give them something to chew on to figure out why it’s going off the rails.