Duplication of titles in printed documentation

I'm using RoboHelp 7. When I generate the printed
documentation (doc file) the structure of my TOC is ajusted. Yet,
when I have a chapter title and some text introducing the chapter,
in the printed version a subtitle (with the same designation as the
title) is created for that introductory text. I'd like to prevent
this from happening - I don't want any subtitles with the same
designation as titles - I'd like the printed version to have a
title and the text (and only present a subtitle if one exists). I
welcome any ideas that might help me solve this one. Thanks.

Hi Garcia,
If this is the same as I get (where I get a duplicated name
because the name of the book in the TOC and the name of the first
topic in that book are the same)...
I have used 2 methods of getting around this:
1. (I prefer this) I apply the "Online" conditional style to
the header that is being duplicated. I then exclude the Online
content from my word output, resulting in no duplication.
2. I remove all of the books from the print content. The
problem with this is that you end up with a section break after
each topic. ARGH!
Hope this helps,
Chrissy

Similar Messages

Missing topics in printed documentation

I am using RoboHelp V7 and WebHelp as my Primary Layout. My project has approximately 100 topics.
The project is basically an A-Z with various topics saved into 26 folders (A-Z). The printed documentation prints perfectly except that the H1 headings for all the 'A' topics are missing from the resulting Word document.
The table of contents in the Word document is correct, with "A" listed but none of the topics are listed in the TOC. The topics appear in their correction location in the word document except the H1 headings is missing. The heading "A" appears in the correct location in the Word document.
In each topic the H1 is in the header and draws its text from the name of the topic.
All the 'A' topics were created manually and the rest 'B-Z' were imported from an Word Document. This appears to be the only difference between the topics!!
All the topics (A-Z) are connected to the same template and access the same CSS file.
On the final screen of the Print Documentation Wizard (Print Document Appearance - Pninted Documentation) I have tried connecting to different templates from the drop down list under MS Word Template. I have also created my own *.dot file out of a resulting document (i.e. stripping all the text and saving as *.dot). But no luck.
Any thoughts?
Many thanks in anticipation.

The HMTL for the two types of pages looks identical
An 'A' page
<div placeholder id=header style="width: 100%; position: relative;">
<h1><variable name=title x-format=default x-value="Air conditioning">Air conditioning</variable></h1>
</div>
A 'D' page
<div placeholder id=header style="width: 100%; position: relative;">
<h1><variable name=title x-format=default x-value="dress code">dress code</variable></h1>
</div>
The only obvious difference in the HTML for the two types of pages is that the pages imported from Word have the following line in their metadata:
<meta name=OriginalFile content="Orientation Guide - Draft Wording_V2.doc">
And both types of pages are clearly connected to the same style sheets.
Stumped?

Problems with RH 9, CBT, and Printed Documentation

When I upgrade an x5 project in the new RH9, all appears to go fine until I try to generate the Printed Documentation. I was disappointed that the printed documentation STILL requires so much cleanup. Text tagged with the Online condition sometimes displays on some topics, even when Online is excluded from the output. Also, some of the cleanup issues surrounding headings and index entries are still necessary.
The four biggest issues are:
1) If a "book" TOC heading also has content (a topic associated with it), a double-heading appears in the printed output. You have to manually remove all these extra headings in the cleanup process.
2) All index entries appear in the paragraph BEFORE the actual heading they mark, instead of after the heading, resulting in the Index not being correct (if a heading appears at the top of the page, the Index points to the previous page where the index entry resides, instead of the correct page). I have to manually go through the entire document and move each index entry to the paragraph AFTER the heading it marks.
3) Robohelp ignores the exclusion of Online conditions on some random topics. There is a workaround to "trick" Robohelp, but it takes *a lot* of time to do. To "trick" Robohelp, I had to generate a printed manual and make a list of all topics that "slipped" through. And, then edit each topic where the online condition was ignored, by adding an extra, empty paragraph to the end of each topic that had:
·         a single paragraph of text (aside from header and footer info)
·         ends with bulleted list (and no extra paragraph marker following)
·         ends with a table (and no extra paragraph marker following)
·         ends with a figure (and no extra paragraph marker following)
·         ends with see also\How do I\misc button text (and no extra paragraph marker before the seealso/how do I listings)
4) I noticed that when I opened a topic for the first time in Robohelp, the Online condition sometimes gets applied to incorrectly tagged text (it wasn't tagged this way in the x5 content). This requires me opening each topic in the upgraded project, and checking each topic to make sure the online condition is applied correctly in each one (a very tedious process, especiallly if you have a doc set of over 1 mil words!).
Expected results:
Printed doc does not contain double headings. Index entries appear after headings. Conditional text behaves as it is supposed to behave (and if you tell Robohelp to exclude the ONLINE condition, it does it for ALL topics).
Does anyone have any suggestions/recommendations for this? Yes, I have the latest build. We held off on upgrading to previous releases of Robohelp because of the Printed Manual problem too (it seems like each version created more clean up work). :-( I logged a bug on the Adobe forum.Any and all suggestions appreciated. Thanks!

Mr. Grainge,
Thank you so much for your thoughtful answers back! I appreciate you taking time out to write such a thorough reply. I hope Adobe appreciates you! You're number one in follow ups!
Unfortunately, your answers did not solve my problems. But, you did give me some ideas on where the problems could be occurring. So, thank you!! Before I begin: In answer to your question, yes I *am* using the supplied Style Mapping template (I never had luck with the custom one myself). Also, I am going to hold off on replying to 1) and 2), but I'd like to share my answer on 3) and 4), which is really just what I need to get Printed Documentation working in Robohelp 9 the same way it worked in x5.
A little history: I have a set of about 50 help projects that span many versions of our company's product, and multiple versions of Robohelp (some even go back to the 90s!). They even include some help projects that were originally in Frame/WebWorks but were later ported to Robohelp. There's a lot of history to them.
Investigating the Problem: When I opened an x5 project in RH 9, I noticed that some of the timestamps on the .htm files didn't match the rest of the files. It turned out, that these very same files that were the ones giving me problems with the Conditional text! That's when your thoughts about the mapping came to mind...As I said, my project spanned mutiple versions of Robohelp. I wondered if some of the coding on the .htm page was being parsed incorrectly on upgrade, and if if that was the reason why RH couldn't update the pages (which explain the unchanged timestamps). In other words, I wondered if Robohelp was mapping the styles correctly on import. So, I compared these unupgraded .htm files with ones that did upgrade, to see if there was something on the code page that could be causing the problem.
Solution to Fix 3) and 4) above:
I'm going to list out everything that I did below, however, not everything on this list applies to everyone. But, hopefully it will help you, if you ever run into this scenario yourself, and it might give you some ideas on how to get your HTML files working. So, before upgrading, here is what I did:
I opened my old CSS in a text editor and removed all the Robohelp autogenerated comments.
In Homesite, I did a bunch of Search and Replaces on a copy of the older x5 project. I looked for code that may have been generated in an earlier version of RH,and for unusual structures in the meta and style declaration area that could be causing conflicts. Here is a list of my search and replaces below:
Search for:

Replace With:
nothing
Search for:

Replace With:
nothing
Search for:

Replace With:
nothing
Search for:
<p> </p>
Replace With:
nothing
Search for:
<p> </p>
Replace With:
nothing
Search for:
<html>
<head>
Replace With:
<html>



<head>
Search for:

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

<link href="MyHelp.css" rel="stylesheet" type="text/css">

<script language="javaScript" type="text/javascript" src="MyHelp.js"></script>
<script language="javascript" src="eHlpDhtm.js"></script>
</head>

<body TABINDEX=1>
Replace With:

<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=generator content="RoboHELP by eHelp Corporation - www.ehelp.com">
<meta name=generator-major-version content=0.1>
<meta name=generator-minor-version content=1>
<meta name=filetype content=kadov>
<meta name=filetype-version content=1>
<meta name=page-count content=1>
<meta name=layout-height content=597>
<meta name=layout-width content=662>

<link href="MyHelp.css" rel="stylesheet" type="text/css">

<script language=javaScript
type="text/javascript"
src="MyHelp.js"></script>
<script language=javascript
src="eHlpDhtm.js"></script>
</head>

<body TABINDEX=1>
Search for:
<a class=toplinks href="#top"> Top</a>
…or…
<a class=toplinks href="#top">Top</a>
Replace With:
<a class=toplinks
href="#top">Top</a>
Search for:
<h3 id=SeeAlsoTitle
class=SeeAlsoTitle
style="x-condition: Online;">See Also</h3>
<div id=seeAlso
Replace With:
<h3 id=SeeAlsoTitle
class=SeeAlsoTitle
style="x-condition: Online;">See Also</h3>
<div id=seeAlso
After I did these all these search and replaces in the copy of the x5 version of the project, I opened the project again in RH 9 and upgraded it. After the upgrade, I checked the timestamps on the .htm files to make sure they all changed. They did! It worked! Everything upgraded properly this time... I tested the Printed Manual output and no conditional text slipped through this time. Yay!
In Summary:
This is what I learned if you are having problems with Conditional text and Printed Manuals in an upgraded RH project:
Always make backups of your older projects before you upgrade anything. I know this is elementary, but I thought it was worth reminding.
Check the timestamps of the files after you upgrade the project. If there are a group of files with timestamps that aren't similar to the rest of the files, chances are Robohelp was having trouble converting those files.
Try looking at the HTML code in those files and see if anything looks out of the ordinary. Some examples are above.
If you have already ported the RH project and it's too late to go back, go look at the file timestamps anyhow. For all the older files, try opening each one in Robohelp and add a space or something (to force RH to change it), and save it. I didn't have the time to verify this, but it seemed on most instances: when I forced RH to save the file manually, it updated correctly and the problem with the conditional text went away. (This option takes longer, especially if you have to do each page individually, but it's worth a try, IMHO.)
Aside from the initial Printed Manual woes, which are resolved, the upgrade process from RH 9 really was seamless! Best I have ever seen! Everything just works! Awesome is a word that comes to mind.
Printed Documentation output does work on upgrade, but in my opinion is: it is no better than it was before, in previous versions.
I wish there were more fixes to the Printed Manual output. When you have a product help system that spans multiple versions, contains over 2.5 million words, and 10,000+ topics, having a lot of cleanup on the production end is costly. What use to take a person on my team less than a day to generate 50+ PDFs in FrameMaker, takes 4-5 weeks man-time in RH. I will outline my opinions in my next reply to this thread.
Thanks again, Mr. Grainge!

Why is the text in the printed documentation centered?

Hello,
When I generated print documentation (.DOC and .PDF), all of
the text was centered. Also, it repeated the document twice (a 12
page document is now 24, for example). Why is this happening? How
can I fix it?
Jennifer

CENTERING
In the last page of the wizard, did you select Use Project
Styles or a Word template? Try using the Style Mapping template
just to see if it fixes the problem.
DUPLICATION
Are you sure the pages are not duplicated in the print
layout?
Are topics linked to books in your TOC?

RH10 - Printed Documentation Issues.

Hi!
I'm new to RH10. I've started a new Technical Authoring role having taken 6 years out of the role... In my previous roles I've walked into the company and the styles and templeate were already set up and I just got on with the authoring part of the role. However, this time I'm starting from scratch, so am requiring some help.
I've used Robohelp in the past and decided this was the software to go along with. However, it's quite a bit different to how I remember it!
Currently I am using a trial of Robohelp 10. I have created a test project and managed to generate a Microsoft HTML Help file. I'm now trying to generate this into a printed document. Issues I'm having are:
Firstly I seem to have a line of text which is set as Conditional Build Tag of Online only showing in my printed document. There are other Onliine only bits that are not showing, but this particular line I just cannot seem to remove from the printed document. Any suggestions on how to deal with this? I have removed the conditional tag and re added it.
The company's brand is to use Tahoma font. However, I'm finding that when I print the document it comes out in grey, even though I've set the font colour to be automatic. I've even tried to swap this to being black, but I still seem to get grey print. Is this down to the font type I'm using or could there be an issue with the generation?
I've set my Heading 1 style to be centred for the title page and still it prints out left alligned. Am I missing something with the style?
Finally, each of my topics are coming out printed on a new page, even though I have not selected the 'Start each topic on new page' check box when setting up the generation options. Can you point me in the right direction to adjust this please.
I'm sure that mose of these are user error and probably down to my rusty authoring. But hoping that help on these will help me to move forward and loosen up the rustyness!!!
I look forward to hearing from you soon.

Online Conditional Build Tag: You may want to check what Conditional Build Tag expression is being used in the Printed Documentation single source layout? This controls the content that is included. However be aware that content in a topic (or a topic itself) can have more than one tag assigned to it. I think this will be a case of going back to the topics that have the online tag and doing some investigation. You can easily identify the topics with a CBT by right clicking on a tag in the Conditional Build Tag pod and selecting Properties.
This could be down to the Word styles you are using in the template and how they are mapped to the RH Styles. Check out the following link for an excellent tutorial on producing printed documentation. http://www.grainge.org/pages/authoring/printing/printing.htm
See point 2.
Again this is style related. It sounds like you have a Word style mapped with the pagination option selected. See point 2.

TOC in Printed Documentation

How do I specify the location of the TOC in the printed
documentation? I would like it to appear after the title page, but
it always shows up before it.

That's right. The title page that is created by the printed
documentation is a default start page which you have little control
over. If you have imported a word document that already contains a
title page this will not appear before the TOC because RH does not
recognise it as such. Those of us who create printed docs usually
do as you describe. We create a generic title page that is stored
in a separate word file. Then we generate the output and copy the
title page into it. You'll need to remove the title page from the
printed documentation process though or else you'll end up with two
of them! Hope this helps.

TOC Layout in Printed Documentation

Morning chaps,
Currently the Printed Documentation is chucking out a TOC that shows the Books, Topics and the Headings in the Topics. I was wondering if there is any way of formatting it so that it only generates Books and Topics?
Luke.

Rats. Sorry it didn't work.
You could do what I always did with Word docs - I didn't let RoboHelp create a TOC for me at all. Instead, I generated the printed doc based on the RH TOC (to get everything in the correct order) and used the Insert > Index and Tables > TOC in Word to specify just the heading styles I wanted to include. (This presupposes that you use a different style for subheadings within topics.)
I got really tired of doing this, so I built a little Word template with a title page, TOC page (where I inserted a TOC field as described), and a blank section at the end. I pasted my RH print output in, then just hit Update Field for the TOC. It was surprisingly quick, although it may be more steps than your workflow allows. Hey, this dates back to before you could create PDFs from Word!
It would be a really nice feature to be able to exclude subheadings from the TOC. Maybe the best course of action is a feature request.
PS - I'll be getting RH8 pretty soon, and I'll take a look at TOC generation then. Maybe they have solved this already! (And I hear that RH8's online help is a huge improvement over RH7's - you're not the only frustrated customer!)

Printed Documentation displays each topic twice

Click Printed Documentation.
Click Next to access the TOC setup
On the right panel, each topic is listed twice. In the final document, RH is adding a heading to a topic and then duplicating the same topic without the RH heading.
If there is a way to prevent RH from inserting these headings, I think this duplication would be resolved.

That's what I was getting at earlier in the conversation but I don't think that is the cause here.
It use to be that if a topic was linked to a book and then the author added the topic because it could not be seen in the print layout, the topic would be in the printed document twice. In the print layout you had to remove the topic and rely on it coming from the book, which it did. In the print layout you would not see the topic whereas you are seeing it twice.
In Rh10 there is a change (may have been in 9). In the print layout if there is a book with a linked topic, that now shows in the print layout. Rh has put the linked topic in the layout so that you can now see it. However, it is only there once.
I am wondering if maybe you had books with links and had put the topic below not realising, then on upgrade you would see your manually added topic plus the one Rh has moved from the book to the print layout? Can you look at an old document to see if the topic was there twice?
Beyond that I don't know what could have caused it but all seems well now.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Win 8 64 bit - RH 10 - Printed documentations

Hi,I worked with RH 8 on a Win 7 32 bit and Word 2007 PC before. All went well.Now I bought a Win 8 64 bit PC with Office 2010 and I downloaded the RH 10 trial version to be able to create a printed documentation in Word or PDF . Both is not possible. What shall I do to make it run? Michael

Try deselecting PDF just while fixing this problem.
Are you using your own title page or the supplied default?
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Customizing header and footer in the printed documentation

Hi,
I'm using a trial version of RoboHelp 2007 and Word 2003.
I have two question about customizing the header and footer
of the printed documentation.
In the printed documentation the footer repeat at the bottom
of each page and contain page numbers, which appear left-justified
on even-numbered pages and right-justified on odd-numbered pages.
How can I customize the footer, that pages numbers appear
always right-justified?
In the printed documentation the header repeat at the top of
each page and are blank on the first page of sections. The name of
the manual appears on even-numbered pages, left-justified. The name
of the root chapter appears on odd-numbered pages, right-justified.
How can I customize the header, that
on every page the name of the root chapter and the name oft
the manual appears? Furhermore I want to include a picture in the
header. How can I realise this?

You can't from RH. See the article on my site.
Images in the header are tricky. If you use the setting that
I think enables that, you will also get the images in the TOC. Try
putting a two cell table and putting the heading in one and the
image in another.

Unable to Generate Printed Documentation in PDF Format

This past week I started having a consistent error when attempting to generate a Printed Documentation layout. This error reads "Internal error encountered, Failed to generate Printed Documentation." Prior Printed Documentation builds on this same project completed fine. Nothing was done to the Help project between the times when this worked and when it no longer was able to create Printed Documentation.
I receive this error even if I generate an entirely new "blank project" build, and then attempt to create a Printed Documentation build from this new blank project. Researching this error, I see this has been a reoccuring problem with this product for some time. The few threads that list the problem as having been "fixed" provide resolution steps that have not worked in my case. Right now I am waiting for our IT Helpdesk people to re-install the Suite. Hopefully this will resolve this problem.
Additional information on this problem - PDF Printed Documentation is failing - the HTML build works fine. If I select just a .DOC Printed Documentation output, this also works correctly. The resulting Word document looks good, although hyperlinks do not work within this Word document. I have reloaded Office 2003 as a troubleshooting effort, but this has nbot resulted in any change in symptoms.
The entire error text is enclosed below, although several other people have also done this in past entries. The few lines that read "Warning, and then report a style issue is NOT the problem here. As stated earlier, when I do this same Printed Documentation build on an entirely new "blank project" it does not work, and the Output text in that case does not contain any such "Warnings" about Styles.
Error text below:
Starting to build Printed Documentation...
Printed Documentation processor 8.0.1.204
Building C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.doc ...
Preparing to create Printed Documentation...
Clearing output folder...
Preparing files for Print Document...
Copying files...
Updating files...
Finished preparing in 2 seconds.
Preparing environment...
Printed Document Generator Environment: Word 11.0.8313, OS 5.1.2600, RAM 2048 M Bytes
Building Printed Documentation 'Printed Documentation'...
Building Single Document 'Printed_Documentation.doc'...
Building 'RF-7800V-HH About this Help'...
Building 'Table of Contents'...
Preparing to build chapters...
Building 'RF-7800V-HH Help and Support'...
Processing 'RF-7800V-HH Welcome'...
Building 'RF-7800V-HH RSP Help'...
Processing 'RF-7800V-HH Station Information'...
Building 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Anc. Connector Mode'...
Processing 'RF-7800V-HH No-Sync Beeps'...
Processing 'RF-7800V-HH Power Management'...
Processing 'RF-7800V-HH Retransmit'...
Processing 'RF-7800V-HH USB Mode'...
Processing 'RF-7800V-HH Broadcast Gateway'...
Processing 'RF-7800V-HH IP Routing'...
Processing 'RF-7800V-HH Voice Settings'...
Processing 'RF-7800V-HH Time and Date Settings'...
Processing 'RF-7800V-HH Position Reporting'...
Processing 'RF-7800V-HH User Interfaces'...
Processing 'RF-7800V-HH Net Switches'...
Processing 'RF-7800V-HH Ethernet Interface'...
Building 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Radio Passwords'...
Processing 'RF-7800V-HH GPS'...
Processing 'RF-7800V-HH Locksets'...
Building 'RF-7800V-HH Network Types'...
Processing 'RF-7800V-HH Network Types'...
Building 'RF-7800V-HH Fixed Frequency LOS'...
Processing 'General Information - Fixed Frequency LOS'...
Processing 'RF-7800V-HH FF Network Information'...
Processing 'RF-7800V-HH FF Preset'...
Processing 'RF-7800V-HH FF General'...
Processing 'RF-7800V-HH FF Comsec'...
Processing 'RF-7800V-HH FF Data-Voice'...
Processing 'RF-7800V-HH FF Squelch'...
Processing 'RF-7800V-HH FF Advanced'...
Warning: style (p.Heading7) is not defined and will be mapped to 'Normal'.
Building 'RF-7800V-HH Quicklook'...
Processing 'General Information - Quicklook'...
Processing 'Hopset Creation - Quicklook'...
Processing 'RF-7800V-HH QL Network Information'...
Processing 'RF-7800V-HH QL Preset'...
Processing 'RF-7800V-HH QL General'...
Processing 'RF-7800V-HH QL Comsec'...
Processing 'RF-7800V-HH QL Data-Voice'...
Processing 'RF-7800V-HH QL Advanced'...
Building 'RF-7800V-HH Sample Plans'...
Processing 'General Information - Sample Plans'...
Processing 'Simple Fixed and Quicklook Nets'...
Processing 'Single Fixed and Quicklook Nets'...
Processing 'RF-7800V-HH Manage Keys'...
Processing 'RF-7800V-HH Program Radio'...
Building 'RF-7800V-HH Tech Support'...
Processing 'RF-7800V-HH Technical Support'...
Processing 'RF-7800V-HH Radio Firmware Compatibility'...
Building 'FAQs'...
Processing 'RF-7800V-HH FAQ Index'...
Processing 'FAQ 01'...
Warning: style (span.strong) is not defined and will be removed.
Warning: style (p.para) is not defined and will be mapped to 'Normal'.
Processing 'FAQ 02'...
Processing 'FAQ 03'...
Processing 'FAQ 04'...
Processing 'FAQ 05'...
Processing 'RF-7800V-HH Glossary'...
Warning: style (p.FM_CellRowHead) is not defined and will be mapped to 'Normal'.
Warning: style (span.Glossary) is not defined and will be removed.
Warning: style (p.FM_CellBodyLeft) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_GLOSSARY) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_Para) is not defined and will be mapped to 'Normal'.
Completed building chapters...
Building 'Index'...
Updating list paragraphs...
Updating images...
Updating page numbers...
Updating page headers...
Updating Table of Contents...
Updating Index...
Saving 'Printed_Documentation.doc'...
Generating 'Printed_Documentation.pdf'...
Failed the generate PDF file 'C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.pdf'...
Failed to save 'Printed_Documentation.doc'...
Cleaning up temporary files...
I am pretty sure nobody will have any fix suggestions that work to solve this problem, but I am making this entry for historical purposes. I will add an entry stating whether the Suite reload resolves this issue.
Thanks,
Tim C @ Harris

If I select ONLY the Word DOC Output format in the Printed Documentation
setup, the output is created without an error (output text below). Links do work within
this Word document (a symptom change since installing patch 8.0.2).
When I use this Word document to create a PDF (using the Adobe PDF
printer driver) a PDF is successfully created, however no bookmarks are
created in the bookmarks panel and none of the links in this PDF work
(although they are created looking like they will work, i.e., blue
underlined text).
Regards,
Tim
------------- Output Text --------------------------
Starting to build Printed Documentation...
Printed Documentation processor 8.0.1.204
Building C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.doc ...
Preparing to create Printed Documentation...
Clearing output folder...
Preparing files for Print Document...
Copying files...
Updating files...
Finished preparing in 3 seconds.
Preparing environment...
Printed Document Generator Environment: Word 11.0.8313, OS 5.1.2600, RAM 2048 M Bytes
Building Printed Documentation 'Printed Documentation'...
Building Single Document 'Printed_Documentation.doc'...
Building 'RF-7800V-HH About this Help'...
Building 'Table of Contents'...
Preparing to build chapters...
Building 'RF-7800V-HH Help and Support'...
Processing 'RF-7800V-HH Welcome'...
Building 'RF-7800V-HH RSP Help'...
Processing 'RF-7800V-HH Station Information'...
Building 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Anc. Connector Mode'...
Processing 'RF-7800V-HH No-Sync Beeps'...
Processing 'RF-7800V-HH Power Management'...
Processing 'RF-7800V-HH Retransmit'...
Processing 'RF-7800V-HH USB Mode'...
Processing 'RF-7800V-HH Broadcast Gateway'...
Processing 'RF-7800V-HH IP Routing'...
Processing 'RF-7800V-HH Voice Settings'...
Processing 'RF-7800V-HH Time and Date Settings'...
Processing 'RF-7800V-HH Position Reporting'...
Processing 'RF-7800V-HH User Interfaces'...
Processing 'RF-7800V-HH Net Switches'...
Processing 'RF-7800V-HH Ethernet Interface'...
Building 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Radio Passwords'...
Processing 'RF-7800V-HH GPS'...
Processing 'RF-7800V-HH Locksets'...
Building 'RF-7800V-HH Network Types'...
Processing 'RF-7800V-HH Network Types'...
Building 'RF-7800V-HH Fixed Frequency LOS'...
Processing 'General Information - Fixed Frequency LOS'...
Processing 'RF-7800V-HH FF Network Information'...
Processing 'RF-7800V-HH FF Preset'...
Processing 'RF-7800V-HH FF General'...
Processing 'RF-7800V-HH FF Comsec'...
Processing 'RF-7800V-HH FF Data-Voice'...
Processing 'RF-7800V-HH FF Squelch'...
Processing 'RF-7800V-HH FF Advanced'...
Warning: style (p.Heading7) is not defined and will be mapped to 'Normal'.
Building 'RF-7800V-HH Quicklook'...
Processing 'General Information - Quicklook'...
Processing 'Hopset Creation - Quicklook'...
Processing 'RF-7800V-HH QL Network Information'...
Processing 'RF-7800V-HH QL Preset'...
Processing 'RF-7800V-HH QL General'...
Processing 'RF-7800V-HH QL Comsec'...
Processing 'RF-7800V-HH QL Data-Voice'...
Processing 'RF-7800V-HH QL Advanced'...
Building 'RF-7800V-HH Sample Plans'...
Processing 'General Information - Sample Plans'...
Processing 'Simple Fixed and Quicklook Nets'...
Processing 'Single Fixed and Quicklook Nets'...
Processing 'RF-7800V-HH Manage Keys'...
Processing 'RF-7800V-HH Program Radio'...
Building 'RF-7800V-HH Tech Support'...
Processing 'RF-7800V-HH Technical Support'...
Processing 'RF-7800V-HH Radio Firmware Compatibility'...
Building 'FAQs'...
Processing 'RF-7800V-HH FAQ Index'...
Processing 'FAQ 01'...
Warning: style (span.strong) is not defined and will be removed.
Warning: style (p.para) is not defined and will be mapped to 'Normal'.
Processing 'FAQ 02'...
Processing 'FAQ 03'...
Processing 'FAQ 04'...
Processing 'FAQ 05'...
Building 'RF-7800V-HH Glossary'...
Warning: style (p.FM_CellRowHead) is not defined and will be mapped to 'Normal'.
Warning: style (span.Glossary) is not defined and will be removed.
Warning: style (p.FM_CellBodyLeft) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_GLOSSARY) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_Para) is not defined and will be mapped to 'Normal'.
Completed building chapters...
Building 'Index'...
Updating list paragraphs...
Updating images...
Updating page numbers...
Updating page headers...
Updating Table of Contents...
Updating Index...
Saving 'Printed_Documentation.doc'...
Completed building Printed Documentation...
Preparing output directory...
Cleaning up temporary files...
Finished Printed Documentation generation in 5 minutes 36 seconds.
Building Printed Documentation complete.

Unable to generate printed documentation

I am running RoboHelp 9 HTML using Microsoft Word 2010 on a Windows 7 machine.
Whenever I try to generate printed documentation using a single source layout that is set up for generating either a .docx file or a .doc file the program hangs up after printing the output message "Processing Topics". This occurs with the simple "Test" sample provided by Adobe that contains only one topic as well as with a more complicated project.
I read some posts that said things about anti-virus software that may affect RoboHelp. On my system the security department at my company has control of that, so I am not really sure what anti-virus software I have. When I look in my "All Programs" list under the "Start" menu, I do not see any anti-virus software programs except something called "System Center 2012 Endpoint Protection". I believe this is the anti-virus software that the security department uses, and there is an icon for it in my System Tray. Has anyone ever heard of issues involving that software and RoboHelp?
Meanwhile any other insights any of you may have into this problem would be greatly appreciated.

Are you generating to a local drive or a network drive? If the latter, try the former.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Footer image not resizing in printed documentation

RH11
Does anyone know why an image inserted into a footer master page is not automatically resizing to the width of the printed page when applied to a print layout and output to Word? If you insert an image into the body of a topic or a master page and generate printed documentation, the image automatically resizes.
I'm trying to insert a high-res footer image (300 dpi) into my footer so that it appears on every page, but at the moment it's being embedded at full-size.
Thanks
Jonathan

Firstly, your better off using liststyles than paragraph list styles, I screwed around a long time before I had to set everything to liststyles rather than paragraph ones. So dont worry about that.
The first issue, of not seeing the style - it is there, if you open the Styles tab on screen (click in a topic to get the cursor, then Format > Styles), not just the dropdown like youve shown youll see a list of all your styles, almost, it will show paragraph styles, click the drop-down and select All available styles, this will display your list styles as well!
Im not sure about the style settings, I have the same text setting applied in my list style as I use for my 'normal' text. Though I think you can select the text in a list and apply a paragraph style to it....i just tried and it worked, but to be on the safe side you might want to set the text formatting in the list style css too..
mine looks like this
li.NumberList {
    font-family: Helvetica, sans-serif;
    font-size: 10pt;
    color: #524C45;
    list-style: decimal;
    margin-bottom: 6pt;
    margin-top: 6pt;
As for printed formats not indenting lists, this is an issue. So far I have found no way around it because you cannot map a list styles in RH to a list style in Word. This has also created errors for line spacing and indents - and I found the indents are severly messed up when using list styles in snippets. Everytime I create printed documentation I have to manually fix it, a pain but it doesnt take too long....you could use macros etc to speed it all up for you.
Submit a Wish Form.
Hope it helps.
Nick

Images not in printed documentation

When generating printed documentation from RH7 (selecting
embed images, MS Word doc, etc.), the images do not show up in the
results. All I see are the {bmc <file name>.bmp} references.
I know this worked in version 5 and I read the release update for
7.0.1 (which I installed) that indicates it was fixed; but no joy.
BTW, I have tried this with a new test document, re-booted the
computer, etc.
What is going on here?

A point of interest with this problem. I have noticed that,
with this installation, when I highlight a true code image in my
Word project file (indicated by {bmc <file name>.bmp} ) then
click the "New Help Image" button (or use Ctrl-G) the image view on
the General tab (Insert Help Image Window) is vacant. This is
interesting, in that, as I recall in RH5 it would show the graphic
that was selected. For some reason this installation is not making
the connection back to the inserted image. I'm thinking this is the
root of the problem. Now, the question is: How do I correct it?
Also, you will note that I previously indicated "this
installation". This is due to my experimenting with an installation
on a different computer (it never having any prior version of a RH
installation) and the Printed Documentation feature works - sort
of. The issue I see on that computer is at the end of the process
RH7 shuts down. It doesn't lock up, it literally closes before the
final step where the pop up dialog box indicating the process
completed, and provides the view file button, is shown. However, I
can find the word document it created an view it - interesting
behavior.

Error when trying to create printed documentation in RH 7

Hello,
I've created a WebHelp project in RH 7 that I'm trying to
make a PDF for, as well. An error always appears when trying to
generate printed documentation, even if only the PDF option or the
Word option is selected. RH 7 processes and builds each of the
pages, index, images, etc. It gets to the very end on the status
bar and an error appears that it failed to generate the PDF.
In the output view, I see that it successfully processed
everything until the end when it says (the last four lines are the
error):
Updating Table of Contents...
Updating Index...
Saving 'GVE_Help_.doc'...
Generating 'GVE_Help_.pdf'...
Failed the generate PDF file '(The path is written here but
has been removed for this post)'...
Failed to save 'GVE_Help_.doc'...
Cleaning up temporary files...
Internal error encountered, Failed to generate Printed
Documentation.
Is there any way to get the Printed Documentation to work
properly in RH 7? I receive the same error for any of the WebHelp
projects I've opened in RH 7. I'm using Windows XP and have Word
2003 on my PC if that helps. I believe, but not too sure, RoboPDF
is still on my PC. May this have something to do with it?
Thanks so much, in advance, for any feedback and help.

Try generating just to Word and then creating the PDF from
there. There is a known problem which affects some users but not
others. Cause not known.

Duplication of titles in printed documentation

Similar Messages

Maybe you are looking for