PDF fails to generate correctly -- "malformed topic" error

Thanks. the RHStyleMapping.css did the trick.

Your link shows quite an impressive list of known, unremedied bugs for this one crucial RH feature.

Is there a like list for every feature in this malformedWare?

Your software is perfect? Also sometimes the problem is what the author has done, so it's not entirely a one sided problem.

The RHStyleMapping.css is not really meant for this purpose but if it works and gives an output that is acceptable, there is no reason why not. Using the Word Style Mapping template is what was suggested.

Look around the site to find out what else is covered.

See www.grainge.org for RoboHelp and Authoring tips

That is funny or would be if it did not betray an astonishing contempt for user and usability.

Yes "our" software has bugs. It is also given away, not sold, nor are we sanguine about our bugs, particularly in mission critical features, like print output in RoboHelp.

Nor are we Adobe, with 8 years of versioning. I recommended RH for our online documentation in large part precisely because of the "auto" pdf generation, only now to find there is nothing "auto" about it, instead it drowning in a stagnant pool of known bugs.

We are searching for an alternative.

I am sorry but I think you have taken more offence to the comment than was intended. You referred to RoboHelp as "this malformedWare" and I was simply pointing out that all software has bugs. I was also making the point that not all the causes are within Adobe's control.

I would also point out that Adobe have not owned the RoboHelp product for eight years.

I don't engage in comparisons with other tools, just make sure that you thoroughly test and that you are not jumping out of the frying pan...

Most printed documentation is created without issue. What you have seen is an accumulation of information gleaned over many years. Some of the items will not give problems in later versions. Most software will look poor if you document all the possible causes of problems, for most users they will not be an issue.

See www.grainge.org for RoboHelp and Authoring tips

Though it may have been there, I do not recall this problem before Adobe took it over from MacroMedia.

Also, I created these projects with an Adobe FrameMaker to Adobe RH workflow, itself a feature rife with CSS bugs. Working with developers as long as I have, it is laughable and pathetic to hear them blame the users and duck under "beyond our control" excuses. No fail-proof model is expressed in the so-called Help either.

There is no excuse for marketing "malformedWare" where critical features fail. None. Zero. Zip.

Emotional, you bet. The practice is shameless and disgusting, no less for being common. One expects more from Adobe.

If you can, please escalate to Adobe management.

Thanks.

Malformed topics are generally caused by the user or by a third-party conversion (the software, network issues, insufficient resources, overly aggressive anti-virus software, etc.).

Putting the onus squarely on RH is a "malformed" conclusion.

Good luck,

Leon

typical developer attitude. the source of all malformedWare.

Hi all

It's fine to have opinions. But please try to keep things on a civil level. This thread is growing perilously close to being locked by a forum moderator and put on report.

Thanks... Rick

Leon,

Didn't quite get your steps, but took the general idea and ran with it. No idea why, but yes it seems the Prev/Next nav tables were "upsetting" the PDF creation. So far (3 out of 15 projects), a conditional print build without them obviates the "malformed" error and the need for applying/removing the RH mapping CSS.

Thank you.

Afraid that changes nothing vis-a-vis shoddy development and the marketing of "malformedWare." I believe tech writers should unite in riding developers and their corporate masters just as hard as they can.

Sorry, but I'm way too busy to be "riding developers and their corporate masters." In putting together online help, I usually find myself as the "ridee," not the "rider."

I try to save my energy by accomodating my help practices to the HAT, so that I can more efficiently deal with the demands of my developers, my management, my IT, my release engineering, and my software product. There's not really much time to kvetch about the HAT I'm using (which by the way is darn good).

How's that "alternative" search going, by the way?

Good luck,

Leon