Info about printed documentation

I'm thinking about buying a printed documentation from the
Adobe online
shop. After looking at the shop I've seen that the new CS4
guides are
available but I'm surprised to see the the price for the CS4
Design Premium
guide is the same as the CS4 Master Collection guide.
I understand that the Master Collection guide should include
more guides for
AfterEffects or Premiere and so it should be more expensive.
I've tryied to look for some information about this printed
guide as number
of pages or some picture. But there's no description in the
online Adobe
shop.
Can somebody that has seen or buyed this guides give me some
additional
information?
Thanks in advance!
Angel

Karen,
I agree with Peter's suggestion.
Also, I see this passage in your first post:
". . . When I generate the Printed Doc from the same files,
mine always comes out fine. . . ."
By the "same" files, do you mean the project files are on a
shared drive? Or did you copy the entire project from one local
drive to another?
Other really basic issues:
When you install a new version of Word you must
uninstal/reinstall RH. Did your colleague get a Word upgrade
recently?
Does your colleague's installation include the RH X5.02
update?
Harvey

Similar Messages

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!

Troubleshooting Printed Documentation

Many print problems can be resolved by referring to these pages:
Printed Documentation on my site is a complete tutorial. Checking your steps against it may identify the problem.
Print Issues covers a lot of the specific problems that have been reported on these forums over the years.
The Troubleshooting Guide has links to the troubleshooting tips for the other RoboHelp forum categories.

Hi,
I just had the very same problem with an iMac I bought yesterday. It made the connection at the time, and worked all day, but on boot-up this morning, no response from mouse or keyboard.
I called AppleCare and, after a lot of testing, was told to get it back to the Apple Store for a hardware evaluation and repair. I called the store and was told it was probably a software problem, and to bring it in. That will happen tomorrow. No rush since I have a wired keyboard that works in the interim.
The key issue appears to be that Bluetooth is not installed. It does not appear in the "About This Mac," nor in the System Preferences, nor is there a sybol in the upper right menu. No one would explain what a user could do about it.
This isn't much info for you, but if I get anything more tomorrow, I'll let you know here.
G5 and iMac (intel) Mac OS X (10.4.5)

Purchased Studio Logic on eBay, no serial number or printed documentation

Hello All,
I recently purchased Logic Studio from a seller on eBay. I was able to install the software just fine. At the time of installation it did not ask for a serial number. However, I recently installed the latest updates and it is now asking me for the serial. My problem is this: there was no printed documentation included in the original packaging.
I have contacted Apple support and basically they told me since I purchased the software from a third party, they can't do anything. I have also tried to contact the seller, but have yet to receive a response.
Does anyone know of a different route I can take to try and recover the original serial number? Or is there a way to obtain a new number? I have the original box with the proof of purchase...if that even means anything.
I've searched the forums and didn't find anything covering this specific situation. I apologize if this topic has already been covered.
Any help/info is much appreciated!
Thanks all, and Merry Christmas!

There are a couple of things that are weird:
1. The Logic installer doesn't request a serial number, if the serial number is already on the system. I assume you had some kind of a previous install.
2. If Logic requires a serial number after a software update, it seems the serial number on the system was no longer valid, e.g. because it ended up on the stolen serial number list.
3. The original box contains a bunch of printed documentation, a booklet about Logic, one about MainStage, and a couple of smaller ones. Also included is a piece of paper that has the serial number on it. I think actuall a couple of times in form of stickers.
Seems like a clear case of contacting the seller. Without the serial number, you don't have a valid license of Logic.

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

List style not visible in printed documentation

Robohelp 8.0.2
Is this a bug??? I opted to use a numbered list style rather than a numbered paragraph style to label procedural steps. The advantage of a list style is that skip numbering would not work properly using the paragraph style. i.e.:
'Steps' Paragraph style with numbering associated:
First step.
          Result of first step.
Second step.            * Bullets and Numbering does not allow me to consistently "Restart numbering at 2" (and HTML this produces is faulty).
'NumberedStep' List style with numbering:
   1. First step.
           Result of first step.
   2. Second step.               * Bullets and Numbering allow me to consistently "Restart numbering at 2."
Now I see the consequences of my decision: My 'NumberedStep' style is not included in the styles dropdown. Inconvenient, but not itself the end of the world.
The real problem is this: Printed Documents are not consistent with the style defined in 'NumberedStep'.
The font is larger than it should be, and indents are all over the place:
This is the selection I made on Generate Printed Document:
On first review, all the styles in my source translated easily to Word, but the style for NumberedStep text was not. That text is now 'Normal'.
I've hunted high and low to solve this issue, so a direct reply is appreciated.

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

Need deeper info about RPC paradigm

Having scoured the Web for info about RPC, I find the same few discussions repeated widely, but certain things left unexplored. I therefore have particular questions that remain unanswered.
1) RPC server behavior appears predicated around "connect-call-disconnect, connect-call-disconnect, ..." behavior on the part of the RPC client; that is, a connect-and-disconnect around every remote procedure call. I, on the other hand, need my clients to implement "connect-wait-call-wait-call-wait-call-...-disconnect" behavior; that is, to connect, REMAIN connected for an extended period of time across multiple procedure calls, and disconnect only when the client is ready to terminate all use of the server. It appears that svc_run() supports this, but I want to avoid surprises; is there any restriction on this usage of svc_run()? Can this paradigm be supported by appropriate use of the RPC library routines available for replacing svc_run() with my own code?
2) The only "documentation" I have been able to find about how to write actual RPC programs dates back to 1992 and does not come from Sun. Virtually all of the routines appearing in its example programs are designated "obsolete" or "for backward compatibility" in their manpages on Solaris 8. Can you recommend/point to an instructional text that describes RPC programming as it would be done with "today's" interface?
3) Probably the largest single obstacle to my organization's possible use of RPC in "real," critical applications, is RPC's continuing C-specificity. We write all our applications in C++, and mostly object-oriented C++ at that -- whereas RPC appears not to have advanced beyond the "C with global variables" architecture (with one possible exception, following). Code generated by RPCGEN (without the -C switch, I admit; I haven't gotten that far in my trial-and-error experiments, yet) requires extensive hand-editing in order to compile C++ code that uses it, or link successfully with compiled C++ code. This obstacle is severe enough to potentially render RPC an unacceptable solution for us.
The possible exception I mentioned is that I found a webpage that discussed something called 'rpcc,' which appeared to be an object-oriented, C++ implementation of RPC. The page said this was available "on Sun machines," but I don't find it on MY Sun machines. Other searches do not turn up other references. Such a thing would be a godsend if it existed, and it would seem not to be so difficult for Sun's professional developers to create. So does it exist? If so, how can I get my hands on it?
4) Different sources contradict each other as to the "semantics" of an RPC procedure call. Sun's ONC manual says flat-out that Sun RPC provides only "at least once" semantics -- but then, the manual takes the approach that one is using RPC in a "transport-independent" manner. Other references discuss the issue at greater length (hint, hint) and imply that any RPC implementation can provide "exactly once" semantics, providing that one specifically force it to use "a reliable transport such as TCP." It is not clear how much to infer, or disregard, in Sun's simple statement. I need to know FOR SURE whether Sun RPC can be made, forced, tricked, etc. into providing "exactly once" semantics. If so, is "use of TCP" sufficient? Or are other tricks needed? Please outline the necessary steps that might be needed in addition to using TCP.
5) (Related to 4. Sun documentation contains language to the effect that Sun RPC provides "at least once" semantics because providing "exactly once" semantics "would be too difficult." However, a graduate student (at Syracuse U if I recall correctly) posts a research paper in which he describes an RPC facility, developed from scratch, that provides "exactly once" semantics. Apparently it's not THAT difficult, after all. The fact that it's "too difficult" for Sun does not exactly flatter the company. They may want to revisit this, and provide yet another RPC interface (in C++ while they're at it). I won't even charge a finder's fee. ;-) )
Thanks in advance,
Chris

I agree fully.
None of the example code applies to todays
"real-world" applications. Im trying to implement
multithreaded RPC on Solaris using rpcgen's -N
"NewStyle", -A "Auto multithreaded" and -C "ANSI C"
options but none of the examples anywhere show how to
do this. Is their a better technology that everyone
is using now that does a similar thing?I have an example that might help. It's a multi-threaded
NIS server that's been running in production for several
years. There are a few tricks in the source that might help.
You can download the source with anonymous FTP at
ftp.cc.umanitoba.ca. Look in the `src' directory for
midas.tar.Z.

More Info about ProRes

Hi, I am still trying to learn enough about this topic to feel good about it, so for any of you who've helped me on on this I appreciate it, and I'm still working on it, so bear with me...
So, the time has come to do some capturing. I have some Beta SP tapes that I'm going to capture. I've been asked to capture them ProRes 422, which is the codec we're editing in. I'm trying to find out more just because I want to make sure this is the most efficient way to do this.
The white paper says HD files that compare in size to uncompressed SD. I realize this is a reference to how ProRes treats HD material, so what is its effect on SD? Are there pros and cons to capturing the Beta stuff in Apple ProRes vs. capturing uncompressed SD? My biggest questions are:
1: Between these three things (ProRes 422, ProRes 422 HQ, and Uncompressed 10 bit SD) what are my end file sizes going to be? Is there a storage benefit to any of these, and if so what's the best option?
2. Is there a better choice? I've heard a lot of people tell me that ProRes is unnecessary for SD stuff, but again, I don't know enough to say otherwise and I've been asked to do it this way, but I've also been asked to find out the advantages to one versus the other here first before we actually rent a deck and start capturing.
3. Just in general, since I'm obviously floundering on getting a good grasp on the use of ProRes for my particular project, anyone who maybe knows of a good place for me to read up/listen up on ProRes and its uses, especially in regards to SD, I'd greatly appreciate any advice.
Sorry to keep asking what seems like the same question worded differently, but this time I'm trying to produce a clear comparison so the big guy can make a decision. Thanks a lot!
Austin

There's a few aspects to this - and such several "correct" answers.
First, what exactly will you be doing? Are you just editing or will there be vfx/color grading etc? If it is the latter, and you're in SD, I'd personally go with uncompressed 10-bit. The files will be large, but it will be worth it if you do a lot of processing.
ProRes files will be much smaller, and still look very good, but may not hold up as well to heavy processing.
Not sure what you mean with #2... what other codec(s) are you looking at. Saying it is "unnecessary for SD" is an interesting comment - depends on what you want to do with the footage.
Some info about ProRes (and uncompressed) bitrates:
http://www.appleinsider.com/articles/07/04/18/acloser_look_at_apples_new_prores_422_videoformat.html
http://www.apple.com/finalcutstudio/finalcutpro/apple-prores.html
http://sportsvideo.org/main/blog/2009/08/11/apple-final-cut-prores-lowers-bitrat e/
http://documentation.apple.com/en/finalcutpro/professionalformatsandworkflows/in dex.html#chapter=10%26section=1%26tasks=true

Where can I find Info about the Integration on SAP?

Hi,
I´m looking for Info about:
-Integration of SAP Backend (R/3, BW, CRM)
-Integration with Legacy or 3rd party Apps
I´m just finding pieces of info and not a document.
Do you know if there are SAP Guidelines or whitepapers on this issues?
I really Apreciate the Help!
Kind Regards,
Gerardo

Hi Gerardo,
welcome to the SDN Forums first. For R/3 to CRM connectivity I would suggest that you read the Doucuments coming <a href="http://help.sap.com/bp_crmv340/CRM_DE/html/opport.htm">SAP Best Practices for Customer Relationship Management - V3.40</a> in the Building Blocks:
B01: CRM Generation
C71: CRM Connectivity
B09: CRM Replication
You find a documentation about the Integaration of R/3 and CRM.
Regards
Gregor

Need info about GN_INVOICE_CREATE

Hi experts!
I need to create Credit / Debit memo invoices in my Z program, so I decided to use GN_INVOICE_CREATE for this, but can not find info about parametres of this FM....
could anyone explaine how to use this FM or maybe someone has a peace of sample code of using this FM?
Helpful answers and advices will be rewarded.
Here is this FM:
CALL FUNCTION 'GN_INVOICE_CREATE'
EXPORTING
    DELIVERY_DATE           =
    INVOICE_DATE              =
    INVOICE_TYPE              =
    PRICING_DATE              =
    VBSK_I                          =
    WITH_POSTING              =
    CALLER_TYPE               =
    I_WITHOUT_REFRESH    =
    ID_NO_ENQUEUE           =
    ID_KVORG                      =
    ID_NO_DIALOG                =
    ID_NEW_CANCELLATION =
IMPORTING
    VBSK_E                           =
TABLES
    XKOMFK                           =
    XKOMFKGN                      =
    XKOMFKKO                      =
XKOMFKTX                         =
    XKOMV                             =
    XTHEAD                            =
    XVBFS                              =
    XVBPA                              =
    XVBRK                              =
    XVBRP                              =
    XVBSS                              =
XKOMFKZM                         =
SUCCESS_DOC_OUT          =          .

Hi Mindaugas,
check BAPIinvoice in SE37, e, here u cannt directly make use of GN_invoice_create, Bcos here u dont have condition records data.
so search in SE37 or Tcode BAPI , here u can get FMs along with Documentations.
Regards
Peram

RoboHelp 10: Problems generating Printed Documentation

Environment
Windows 7 Enterprise, Service Pack 1, 64-bit operating system
Office Professional Plus 2010 Versions 14.0.7106.5001 (64-bit)
RoboHelp 10: 10.0.0.287
Visual Studio 2010 Professional. I open RoboHelp from within Source Control (have been doing it for two years).
Problem
Sometime after moving to RoboHelp 10, and even after successfully generating Printed Documentation output, I encountered a major problem generating Printed Documentation from RoboHelp: “Internal error encountered. Failed to generated Printed Documentation”. The error occurred when I tried to generate Printed Doc using my default TOC, which looks something like this:
Topic A
Topic B
Book 1
Book 2
Book 3
Topic C
Topic D
Based on an old Peter Grainge reply to someone about a similar problem, I removed all but the first topic from the Chapter Layout pane and generated the Help. Everything was fine until I got to the topics after Book 3. At that point everything started to fail again. When I removed Topics C, D, etc. from the Chapter Layout pane, the output was built successfully.
I tried moving Topics C, D, etc. to the top of the Chapter Layout pane, and got the same error. I tried creating a new folder and put Topics C, D, etc. into that folder. Failure after failure.
As an experiment, I removed all the Topics C, D, etc from the Chapter Layout pane, but then added them to the Print Document Section Layout pane (not where I want them). The Printed Documentation built successfully.
During attempts to build with Topics C, D, etc. in the Chapter Layout pane, I kept getting a Word error: Word is trying to recover your information. After that there was always a failure.
Selecting PDF as the output did not work when the Topic C, D, etc. files were at the bottom of the Chapter Layout pane.
I create a new TOC and a new Printed Documentation SSL. Failed to generate.
As a matter of reference, I've been generating Printed Documentation from the same TOC for more than a year and so cannot figure out what has changed in RoboHelp or Word to cause this grief .
Has anyone experienced anything like this?
Carol

Dear Peter,
Thanks for following up. Last Friday I finished extensive testing on my own and working with RoboHelp Support. Here's what I sent to Support this morning.
If after reading this screed, you think it worthwhile for me to get a copy from Source Control for you to look at, I will do so. Thanks for offering to look at it.
Environment
Windows 7 Enterprise Service Pack 1, 8.00 GB RAM, 64-bit OS
Microsoft Office Professional Plus 2010 Version 14.0.7106.5003 64-bit--Note: We repaired my current version of Word, in case that was the problem, but did not reinstall Office--we do not think that the Word version is the problem because we generated successfully with other TOCs and when generating individual documents.
RoboHelp 10.0.1.292. Upgraded from RoboHelp 9 in May 2013. Replaced hard drive in September 2013 and reinstalled RoboHelp.
Visual Studio 2010 Professional 10.0.40219.1 SP1Rel (I open the project from Source Control and check files out to a folder on my desktop.)
Issue
Printed Documentation failed multiple times with the default Table of Contents, which contains all the topics in the project. TOC specs are as follows:
Properties: .docx, desktop location, no conditions, embedded images, “Generate a single document”, “Retain hyperlinks”.
330 files, 12 top-level books, 15 second-level books, 7 third-level books, 6 fourth-level books, and 8 fifth-level books
Results
Generation to Printed Documentation does NOT fail for other, module-specific TOCs, nor to WebHelp Pro SSLs for the same sets of topics. In addition, and perhaps more important, generation to Printed Documentation does NOT fail with “Generate Individual Documents” selected, or when there are approximately fewer than 259 files in the TOC.
Did not fail consistently based on any particular topic.
Did not fail consistently based on location of any particular topic in the TOC.
Failed when I created new TOCs based on ‘working’ TOCs. For example, copied a module-specific TOC and then added topics to it from the default (superset) TOC. I did this in case the original default TOC was corrupted.
Failed when I create a new TOC with the same folder/file structure from scratch.
Failed when I created a new TOC with a flat file structure from scratch.
Failed when I retrieved an older TOC from the last release of the product.
Failed when I created new SSLs each time. I did this in case the SSLs had got corrupted.
Failed when I did not open the project from Source Control (removed project from Source Control and worked locally).
Began to see failure when there were more than about 258-263 files in the TOC. For example, successfully generated Printed Documentation with 262 files in the TOC. Added one topic and the generation failed. Removed that topic and added several others, one at a time. Consistently failed. To test this, I created a TOC with all the files in a flat structure, generated a report for the TOC, printed it, and counted the number of files. I then began deleting files and regenerating the Printed Document to try to identify the number of files in the TOC when the generation failed. Successfully generated up to about 258 files and then it began failing. (Occasional successes at 260 and 261, but that may be because I didn’t always consistently remove the Glossary and Index from the Chapter Layout pane.)
Other Comments
(I know that we should generally post non-RH issues to other forums, but in this case I wanted to include all potentially related issues in this posting.)
The first time you generate any type of output, the “Critical error of Source Control Provider. Please restart IDE.” Message appears. This message appears behind RoboHelp. As a result, if the RoboHelp window is maximized, you think that RoboHelp is hung. Forcing a close of RoboHelp leaves the partially generated Word document in an unstable state. When you re-open RoboHelp and try to generate the output again, RoboHelp says that the output is in use. Unfortunately, there is no way to ‘free’ the Word document and you have to restart the computer. In addition, when the dialog box is hidden, even using Alt+Tab to find the dialog box is complicated because you can’t grab it and click OK until RoboHelp completes its processing. The workaround is to reduce the size of the application window so that you can see the dialog box and try to quickly grab it and click OK. That said, as soon as processing is complete you can grab the dialog box and click OK; at that point RoboHelp displays its own error message about the success or failure of the output generation. It is not clear whether the RoboHelp API or Source Control puts up this error message, but it’s definitely a problem until you happen upon the workaround.
RoboHelp does not check SSLs even when I right-click the SSL in the Single Source Layouts pane, click Check In, select the XML and SSL files, and leave “Keep checked out” deselected. The red check mark remains next to the SSL name. In addition, even when I Check In All files before closing the project, the next time I open the project RoboHelp displays a series of Check In dialog boxes requiring me to check them in again.
When RoboHelp hangs during a Printed Documentation failure and the Version Control setting is to check in all files when closing a project (which I’ve now deselected to avoid this problem), Ctrl+Alt+Del indicates that you cannot shut down the program because RoboHelp is waiting for a response. Yes, RoboHelp was waiting for me to check in some files (because of the Version Control setting), but hid the Check In Source Files dialog box behind the application. This usually left a Word document in limbo, forcing me to restart the computer.
At one point RoboHelp stopped saving changes to an SSL after I made changes and clicked Save and Generate. Each time I reopened the SSL, I had to select .docx, etc. all over again.
Carol

Printed documentation - word

I try to valide RoboHelp HTML with a trial X5 version.
1) The tools "printed documentation " send this error "Cannot
find Microsoft Word installed on your system"
2) The installeur was funded word 2000 perfectelly
3) The path in registry was OK.
4) RoboHelp Word find word and use word without problem
I suppose it exist a solution
Thanks

Hi, JMD - welcome to the forums.
This problem has happened to lots of people, and there are a
number of possible causes.
Click
here for a link to Peter Grainge's site that has some of them
listed.
The most common solution appears to be a) uninstall RoboHelp,
b) uninstall Word, c) reinstall Word, d) reinstall RoboHelp.
There's something about the order of these steps that seems to
work. Remember that you must install RoboHelp using your login ID
with admin privileges.
For some users, they had to uninstall/reinstall all of
Microsoft Office, not just Word.
I understand how frustrating it is when RoboHelp uses Word
just fine until it comes time to actually produce a Word document -
nothing about these program interactions is easy or obvious. All I
can say is that sometimes the fix works.
Good luck,
Elisa

Info about printed documentation

Similar Messages

Maybe you are looking for