FM styles not mapped to RH using TechComSuite

Hello,

I had the same issue. The first thing I did before importing my FrameMaker project was apply the fmstyle.css to the default topic in RoboHelp. Next, I edited fmstyles and added all of my styles from FrameMaker that were not listed.

After all styles are listed in fmstyles, I imported my FrameMaker document. During the import, the Style Mappings are really important, I mapped all styles appropriately (I recommend mapping all numbered and bulleted lists to Normal they look a lot better). Also on the RoboHelp Style Mappings window, I would recommend using the Save As button once you have your style mappings correct. I have had RoboHelp crash and loading this back in is a great time saver!

Also, I would recommend installing RoboHelp patch 7.0.2, for me it fixed an issue with Cross-references not working.

I hope this helps,
Amanda

Well, I hate to be a beta tester on a released product that we purchased (go figure), but after two Technical Support phone calls later (neither of which were of any use), I discovered the problem on my own.

Problem #1: Two of my FM styles (Note and Tip) use auto-inserted text upon their selection. For example, when we select Note, the word "Note" automatically appears. We then hit a carriage return to start entering the note text under the Note style using a style aptly named "Note Text." For reasons unknown, unless I manually enter another character or add a space after the word "Note" after selecting the Note style, RH does not recognize the Note style when mapping styles from FM to RH. This problem may be related to Problem #2.

Problem #2: When mapping styles, it appears RoboHelp only lists Framemaker styles that are used in the document, even if the styles exist in the paragraph designer. For example, I may have Heading 6 in my FM paragraph designer, but unless I use it in the document, it will not appear in the list of FM styles to map in RH. I don't know the reasoning behind this decision; perhaps the TechComSuite designers were worried the interface would look cluttered with too many unused styles. Whatever the reasoning, all styles should be listed, regardless of whether or not they are being used in the document.

Problem #3: Technical Support reps at Adobe need to be better prepared to deal with FM to RH integration issues. During each phone call, I was transferred four times. The FM tech transferred me to the RH tech who transferred me back to a FM tech. Since they couldn't solve my problem, they assumed the issue was with the "other" software, which they weren't familiar with.