Skip to main content
Inspiring
August 6, 2009
Answered

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

  • August 6, 2009
  • 1 reply
  • 2134 views

Here is a link to a screen shot of the output view log together with the topic files indicated as "malformed" therein.

https://rcpt.yousendit.com/723109485/295a6159c17d8386b3308c9404681b90

Just what is meant by this word "malformed." There is nothing apparent to distinguish these topics/files from the others, and Web Help output is unaffected.

Or is this just another RH bug?

I have 15 projects for which PDFs urgently need to be generated.

Thanks.

Steven

This topic has been closed for replies.
Correct answer MergeThis

typical developer attitude. the source of all malformedWare.


First, I am not a developer, only an online help writer since 1990.

Secondly, how are third-party software, network issues, insufficient resources, overly aggressive anti-virus software, etc. under the purview of RoboHelp?

Looking at the files you provided, I suspect that the Previous/Title/Next tables at the very top of these topics, particularly if they were converted from Framemaker, might be at the root of your problem.

Try this:

  1. Assign the Print conditional tag to that entire table, then add a separate Chapter title (title only) with the Online conditional tag.
  2. Add a "NOT Online" conditional build expression to the Print Documentation layout.
  3. Add a "NOT Print" conditional build expression to the WebHelp layout.

Good luck,

Leon

1 reply

Captiv8r
Legend
August 6, 2009
stevenjsAuthor
Inspiring
August 7, 2009

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?

MergeThis
Inspiring
August 12, 2009

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