Skip to main content
July 16, 2008
Question

Can't create pdfs

  • July 16, 2008
  • 27 replies
  • 3695 views
Can’t batch or generate either .pdf files singly from RoboHelp 7. Says
“Internal error encountered, Failed to generate Printed Documentation.” This message is not only poorly punctuated, but also not very helpful.

Created Doc (horribly), not the pdf
This topic has been closed for replies.

27 replies

July 21, 2008
removed graphics, tables, images, deleted Orginator tag and nbsp strings, turned off all numbering in Word and saved as body text, yet Output View shows:

"Failed the generate PDF file 'C:\Documents and Settings\colin.flood\My Documents\Technical Writer\Help files\test\Vista and XP\!SSL!\Printed_Documentation\Vista_and_XP_Setup_without_formatting.pdf'...
Failed to save 'Vista_and_XP_Setup_without_formatting.doc'...
Cleaning up temporary files...

Internal error encountered, Failed to generate Printed Documentation."
July 21, 2008
well, that is interesting: nothing happens when I click on Change Conversion Settings on the Adobe PDF menu embedded in Word. I can't seem to find this option by sleceting Adobe PDF from the Print menu either...
July 21, 2008
Created test project with suspect pages. No warning messages, just this:

Failed to save 'Vista_and_XP.doc'...
MergeThis
Inspiring
July 21, 2008
Try this in Word:

1. Select Adobe PDF > Change Conversion Settings.
2. In the Settings tab of the Acrobat PDF Maker window, uncheck the Enable accessibility and reflow with Tagged PDF option in the Application Settings panel.


Good luck,
Leon
July 17, 2008
OK, this is an excellent resource, but the main complaint is still valid: RH should absolutely clean up and import files from the Word processor with 97% of the market! No wonder people are frsutrated - none of this stuff is in the RH Help files.

Though I must blame myself. I imported Word docs into FrameMaker a few years back and they needed to be cleaned up first before importing automatically. Just wish Adobe did a better job of preparing people for this.
July 18, 2008
Removed <meta name=Originator content=ImportDoc>
also <meta name="Originator content"="ImportDoc">

Multifile Find can't find p.Normal24 or any p.Normal or p.N

Warning: style (p.Normal24) is not defined and will be mapped to 'Normal'.
Warning: style (p.Normal44) is not defined and will be mapped to 'Normal'.
Warning: style (p.Normal43) is not defined and will be mapped to 'Normal'.

Is this what is preventing RH from generating a pdf?
MergeThis
Inspiring
July 18, 2008
You expect an HTML-based product by Adobe to "absolutely clean up and import files from" the Microsoft Word product, which produces perhaps the most bloated output of any on the market?

Pretty funny, dude...


Good luck,
Leon
July 17, 2008
BTW, most of the errors during the document or .pdf compile are created by InlineNormal types of text. Even changing it to Normal or removing the tag in the code does not seem to allow proper numbering. The numbering does not show in the Design view. Preview shows the sentence numbered, but it is the wrong numbering. I seem to remember that all text in Word documents should be Body, not Normal, before importing the document.
MergeThis
Inspiring
July 17, 2008
Read this article from Peter Grainge's site about importing Word docs. As you'll see, you have to actually manually Backspace Delete those numbers and bullets before you can go forward. There's other good stuff in there that might point you to fixing oher issues.


Good luck,
Leon
July 17, 2008
same project? No. had no problem with the Primo pdf, it was the Adobe pdf with EPS images.

Here, I created a new project by importing Word doc: no problem with the graphics, some problems with text, TOC, tables, but I can't create the pdf from RH...
MergeThis
Inspiring
July 17, 2008
There's probably some corruption carried over from the original Word doc.

Try creating several Printed Doc layouts (Test1, Test2, etc.) and include portions of topics into each. Once you've narrowed the field down to one layout, break that out into several other layouts until you finally hit the bad topic. Not an easy answer, I know, but it should clear things up eventually.


Good luck,
Leon
MergeThis
Inspiring
July 17, 2008
Is this the same project that was discussed in your previous posting (one in which you were having trouble importing a Primo-generated PDF file with unsupported-by-RH image types)?

It might help us analyze your situation if you told us what format your data was in when you generated the PDF file using the Primo freeware.


Good luck,
Leon