An update to the problem: It's not limited to Heading 1's. In the course of troubleshooting (I renamed the Heading 1, 2, and 3 paragraph formats), I managed to lose the Heading 2 styles as well. Heading 3's are still there, however.
OK, here's the summary: Adobe doesn't like Microsoft fonts.
I had set Microsoft Sans font for my "Heading n TOC" paragraph styles. Changing JUST the font results in the TOC being generated in Robohelp correctly.
BTW: I can't be the only one who thinks how RH handles TOC generation (by paragraph formatting appearance) is completely wrong, right? I mean, here we have a robust structured authoring environment that is all about structure, structure, structure. And then we use an online help conversion program that basically extrapolates the structure using fonts and indenting-- and does so in a way that's completely opaque to users.
Message was edited by: mortaine_ to be less, um, harsh, in my criticism.
Why don't you do your ToC in FM and then tell RH to use it when in the link/import wizard? Then you wouldn't be dependent on how RH creates T0Cs right?
Jeff: That's exactly what I did. And when Robohelp brought in the TOC from Framemaker, it removed all my Heading 1's (and later, my Heading 2's) and didn't include them in my TOC-- the actual content beneath the Heading 1 was there, but when the online help was generated, the only way to find it was through Search or Index.
No matter what, you're dependent on Robohelp somehow figuring out what your structure is (unless you're going to manually create TOCs in RH, which I'm not going to do-- I do not invest this much time in using the right headings and formats to have to manually create tables of contents for my online help systems) so that it can make the online help TOC.
Oops, sorry, I missed that in your OP.
I suggest thinking of your .book and TOC file slightly differently.
There is no reason not to have one .book that provides you with one set of features (say, for a PDF version) and a second one that provides you with another set of features (say, for on-line help). You can still conditionalize your content to your heart's content, and it will make it a lot easier for you to maintain the different 'look and feel' of the repurposed material. It will also help you take the control you want back from RoboHelp, as you aren't painted into a corner by thinking everything must be done only one way. TCS 'out of the box' does work just as the folks at Adobe are saying it does, but it's up to us to 'think outside the box' to get what we need out of it. Also, it's up to us to use Adobe's feature request and bug reporting systems to keep Adobe moving in the direction that makes the most sense for us end users. While fora like this one are helpful, it's not necessarily as direct a line to the ears that need to hear what we're saying.
I have the exact same problem with RH9/FM10, did you solve your problem?
Thanks in advance.
It looks like it worked when they changed the font that they were using in the FM ToC.