Print documentation to HTML

I'm trying to print my LabVIEW project documentation in
HTML, using Print Documentation in the File menu. When I
select complete documentation and look at the preview, I
can see the VI hierarchy but after that, when I print it,
VI hierarchy is not printed. Has anyone an advice for me?
I've tried to select custom documentation and check the VI
hierarchy but nothing changes. What can I do?
Thanks in advance and best regards.
Gorka Larrea
[email protected]
* Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is Beautiful

Attached are two vi's. One is language.vi. There is a control on there that has different text for the label and the caption. Now run test.vi and select language.vi. Labview crashes. At least it does for me. If you highlight execution, you will see it crashes when it tries to write the caption to the label. I'm using version 6.1. Thanks for any help.
Attachments:
test.vi ‏54 KB
language.vi ‏22 KB

Similar Messages

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

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!

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

Some images do not print when in printed documentation

I have been encountering this problem for over a year now...
I maintain over 20 projects in RoboHelp HTML. I have numerous
printed document layouts defined. However, in what appears to be
random situations, some of my images do not print. They display
online just fine, but they are not visible in the printed
documentation. Only a blank gap displays where the image should
display. And there is no conditional build tag applied to any of
these images. The reason I think it is random is because, if I
perform the following test, the images print just fine:
- duplicate the printed documentation layout
- remove, from the duplicate copy, all of the pages
surrounding a page that contains an image that does not print
- generate the duplicate copy

I had a similar problem with missing images. I never really
solved it, but it (apparently) went away. One thing which helped
was ensuring that none of my images had filenames containing
spaces.
In addition, selecting Link images rather than Embed can be
useful; missing images are then replaced by a red cross which makes
it easier to locate the problem.
Also, in Word, you should uncheck Tools > Options >
Print > Update Fields (that is for Word 2003).
--- Derek

Printed Documentation Research

I would like to put some proposals to Adobe to let them know
well or otherwise the current workflow for producing a printed
document works for you. Also what do you particularly like or
dislike, things you want to do but cannot.
I would welcome your feedback on that so please email me via
my site.
It would be very much appreciated if your subject line starts
- RH Printed Documentation. Also start your email by indicating
which release you are using (RH6, X5 etc) and whether you are using
RoboHelp HTML or RoboHelp for Word.
Thank you.

I would like to put some proposals to Adobe to let them know
well or otherwise the current workflow for producing a printed
document works for you. Also what do you particularly like or
dislike, things you want to do but cannot.
I would welcome your feedback on that so please email me via
my site.
It would be very much appreciated if your subject line starts
- RH Printed Documentation. Also start your email by indicating
which release you are using (RH6, X5 etc) and whether you are using
RoboHelp HTML or RoboHelp for Word.
Thank you.

Broken bookmark cross references in Printed Documentation

Hi,
I'am using RH 10 to generate a printed documentation output. What i notice is that the book marked cross references are broken in the Printed Documentation output. Other cross references are linking fine, but, the bookmarked cross references do not link to their destination.
I generated a chm file for the project and the bookmarked cross references appear fine there. Is there anything that could be tried to rectify this problem.
Please note that i'am using HTML files as the source files to convert to a Word output.
Thanks,
Rupesh

There's no easy way to do this. RH doesn't include any
sequence that will convert to a cross-reference in Word, and
inserting multiple cross-references in Word isn't as easy as
executing a find-and-replace command. The best workaround I've
found so far is this:
1. In your RH doc, include a reference that is easily
distinguished from other text. For example, "For information on
Project Beta, see page BETA."
2. Generate the Word document.
3. Find the first instance of "BETA."
4. Insert a cross-reference to the page number of the Beta
heading.
5. Toggle the field code.
6. Copy the field.
7. Find the next instance of your special text ("BETA" in
this example).
8. Paste the field reference.
9. Repeat this process until you're finished.
Unfortunately, the field code references change each time you
generate the document. Equally unfortunately, Word won't recognize
regular braces and text as a field code reference - you have to use
the Ctrl+F9 sequence to generate them manually. So you can't just
generate the document, insert the first cross-reference, and then
replace "BETA" with {PAGEREF _Ref### \h} across your entire
document - it won't work. Instead, you must visit each reference
and paste the field code sequence manually.
If someone else can improve on this process, I'm sure a lot
of people would be happy. If not, it's the easiest workaround I've
seen here, so you might find it useful.

How to export In-line Javascript to printed documentation?

Hi Folks,
I am working in Robohelp 8 HTML, and have created these wonderful javascript include files that allow me to generate numbered and bulleted list instructions and insert them into my help guide pages.
Basically, the instructions are the same and repeated throughout guide. What changes are the field names and numbering sequence.
Ah, you say, why not use snippets for this? I do use them when the block of information is identical and needs repeating.
Well, my cleverness ended when I started to generate printed documentation and discovered that my in-line javascript inserts and my include files are ignored in the export process.
Examples:
In my HTML Robohelp document, I include a javascript file that contains my procedures and functions. Then in the HTML document, I insert the call, surrounded by all the necessary <script> wrappers:
document.write(how_to_get_to("Manufacturing,Reports",","));
This produces something like this on the webpage:
Steps
   1. Open the main menu.
   2. Click the Manufacturing folder to expand it.
   3. Double-click the Reports menu item to open the window.
When generated to printed documentation, it is just missing.
Questions:
1. Anyone else having the same problem?
2. Any creative suggestions on how to generate printed documentation.
I already know I can print from the web page.
Thanks!!

Hi Peter,
Ok, well that worked.
I created a snippet with the <OL></OL> tags, and then stripped out these tags when I saved the snippet. No space before or after.
Then when you insert the snippet in your ordered list, you have to go to the HTML side, and remove the closing </OL> tag before the snippet, and the opening <OL> tag that robohelp inserts after the snippet.
So, when you insert it looks like this:
<li class="p-BodyText"><p class="BodyText">Optional.  Press the
<span style="font-weight: bold;">Warehouse Search</span> button to
filter the report for a specific warehouse, or leave the field empty
to include all warehouses.  </p></li>
</OL>
<?rh-placeholder type="snippet" ref="FLD-Location From To" ?>
<?rh-placeholder type="snippet" ref="FLD-Account Group From To" ?>
<?rh-placeholder type="snippet" ref="FLD-Account From To" ?>
<?rh-placeholder type="snippet" ref="FLD-Item From To" ?>
<OL Type="1">
<li class="p-BodyText"><p class="BodyText">Leave the <span style="font-weight: bold;">Material
Code</span> field empty.</p></li>
And you change it to look like this:
<li class="p-BodyText"><p class="BodyText">Optional.  Press the
<span style="font-weight: bold;">Warehouse Search</span> button to
filter the report for a specific warehouse, or leave the field empty
to include all warehouses.  </p></li>
<?rh-placeholder type="snippet" ref="FLD-Location From To" ?>
<?rh-placeholder type="snippet" ref="FLD-Account Group From To" ?>
<?rh-placeholder type="snippet" ref="FLD-Account From To" ?>
<?rh-placeholder type="snippet" ref="FLD-Item From To" ?>
<li class="p-BodyText"><p class="BodyText">Leave the <span style="font-weight: bold;">Material
Code</span> field empty.</p></li>
This does translate to the printed page. A bit more overhead than I would like. But better than managing the same content in a hundred different files.
Thanks for the brainstorm.
Marilyn.

Print VI To HTML Change in behaviour of format form LV 7.1.1 to = 8.0.1

I detected a change in the behaviour ot the Print VI To HTML Invoke node when using the Custom format and going from LV 7.1.1 to LV8.x.
In LV 7.1.1 I get a horizontal line and a header before each section, e. g
Horizontal Line
Connector Pane
In LV 8.x this is missing. The format Complete will inlcude the horizontal line and the header but I don't need the Block diagram section of the VI. The Custom format allows me to do that.
I will treat this as a bug since I have to create a workaround VI to delete the Block diagram section from the HTML file and delete the graphics file from the disc.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Hi Waldemar,
Thanks for the feedback. I have filed this documentation error with R&D under CAR #135411. This was changed between LabVIEW 7.1.1 and LabVIEW 8.0 but it does not appear that it was documented anywhere.
Rishee B.
Applications Engineer
National Instruments

Resizing images in printed documentation

I have Robohelp 10. Is there a way to resize all images to 80% when creating a word and pdf document. If I create an image style to 80%, it is ignored when creating printed documentation but works for online HTML help.

Hi there
From what I'm reading, it would seem that you are using CSS to present images at 80%, no?
If that's the case, it would seem you want your images presented at 80% of original size regardless of whether they are presented on the screen or whether you are creating printed output. And if that's the case, I'll ask the obvious question.
Why don't you simply scale them to 80% before inserting them into the project? Wouldn't that solve the issue and eliminate any need to create a CSS rule to scale the image?
Additionally, by scaling in the browser you are likely causing horrible loss of quality. And causing the page to take longer to load because the larger image is being loaded when the page is viewed.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

RoboHelp/RoboPDF freezes when trying to generate PDF printed documentation

Hi,
I am using RoboHelp HTML X5.0.2 build 801 with Win2k and Word
2000. Whenever I try to generate printed documentation in PDF
format RoboHelp freezes and doesn't respond until I kill the
program. I also tried first generating the printed documentation in
MS Word .doc format and then tried to generate the PDF from within
Word. RoboPDF kicks in this time and freezes along with MS Word.
Any ideas why this is happening?

It works on anything we throw at it. You could try the
supplied sample projects.
Have you tried creating a document directly in Word and
creating a PDF from that?
Where is you normal template stored? Locally?
Take a look at Snippet 33 on my site. You should be getting
an error message if that is the problem but it might be worth
checking the path anyway.
Click
here.
If that does not fix it, email me offline.

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.

Order of Index and Glossary in Printed Documentation

In my RoboHelp HTML project, I'm adding an Index and Glossary to the Printed Documentation section layout. I want both files below the Chapter Layout icon. They both will go no further than the first icon above the TOC. The down arrow is grayed out.
Someone else had this problem, and the answer was to click the last icon in the Section layout and then add the files. This did not work for me.
Any ideas?
Thanks in advance.

I had the same problem with RH8.
What corrected it for me was to delete the TOC, click the + button, add the Index (it magically appeared where it was supposed to be, at the end), then click the + button again to add the TOC back in. (I don't have a Glossary in my section layout)

Print documentation to HTML

Similar Messages

Maybe you are looking for