Anchored Table Width in Printed Documentation

Hi all,
I'm working in RoboHelp 8 HTML and am dealing with a new pain point. Recently I created a step by step how to guide on a page within a table. Instructions are in one column and images in an adjacent column. I discovered however that the table widths weren't anchored in printed documentation. I read online that that this was a known bug so I installed the necessary patch (8_0_1.exe). Now, even after the install, I'm still seeing the problem. The generated webhelp looks fine but when I print the page the margins no longer align. Any insight into the issue would be most appreciated.
- Meredith

Before tackling your question, I strongly recommend you apply patch 802. See Opening Projects on my site.
I once investigated a problem where some cells were going off page and others were fine, is that what you are seeing? The answer is in in Print Issues on my site.
When RoboHelp generates printed output, it sends tables to Word as the defined width unless that width is greater than the width between the margins. Then it does the following:
If there are no merged cells, the table is scaled to fit the width between the margins.
If there are merged cells, the table does not get scaled and overruns the margins.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

RH creates a frame around tables when generating printed documentation

Hi,
We import FrameMaker documents into RoboHelp 9 and then we generate printed documentation (Word documents).
In the generated Word documents, all tables appear in a frame or an additional table cell.
This did not happen in RH7.
In RH itself it seems OK.
Is there a hidden setting somewhere that controls this behavior?
Thanks,
Rakefet

I found out that when we import the FM document into RH, RH adds the following lines in the html file:
before the table:
<?rh-align_start align="left" ?>
after the table:
<?rh-align_end ?>
When I manually delete these lines, the tables in the generated Word files are OK.
Is there something I can do in FM or in RH so that these lines are not added?
Thanks,
Rakefet

Controlling table width for printing

Is there a way I can use Dreamweaver, perhaps with CSS, to
add a table to my site that is set to a fixed width of, say 850
pixels but have the text inside the table wrap properly when
printing? I know that fixed width tables beyond about 760 pixels
cause the text to flow off the page when printed from some
browsers, and we usually control this using a percentage to
determine the table width. In this case, though, we'd like to use a
fixed width when the content is viewed on screen, but have the text
wrap when printing before it reaches the right margin of the fixed
width table. Make sense?

Have two stylesheets which control the width of the table.
Make the screen
media stylesheet set its width in pixels and the print media
stylesheet set
it in percents.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Klytus" <[email protected]> wrote in
message
news:e7hh5a$59n$[email protected]..
> Is there a way I can use Dreamweaver, perhaps with CSS,
to add a table to
> my
> site that is set to a fixed width of, say 850 pixels but
have the text
> inside
> the table wrap properly when printing? I know that fixed
width tables
> beyond
> about 760 pixels cause the text to flow off the page
when printed from
> some
> browsers, and we usually control this using a percentage
to determine the
> table
> width. In this case, though, we'd like to use a fixed
width when the
> content is
> viewed on screen, but have the text wrap when printing
before it reaches
> the
> right margin of the fixed width table. Make sense?
>

Tables in RoboHelp's printed documentation

Hi,
I am trying to figure out if I can somehow tag tables in RoboHelp to ensure they are not split into two different pages. I'm working with RoboHelp7. RoboHelp will put a page break between two rows, so I'll have half a table on one page of the pdf output and half on another. Often, the row that's been pushed onto the second page will no longer have an upper border. It looks really odd. Can I instruct RoboHelp to avoid page breaks in tables? If not in RH7, is this possible in RH9?
Thanks,
Louley

Please see the sticky topic Before You Post and always include your version of RoboHelp when you start a thread.
That problem does not occur if you use tables created using the table editor in RoboHelp 8 or 9. If you visit my site there are some Word macros that will process your tables and fix that problem with other tables. You will need to edit them to change the colours and removed changes you don't want but they are commented to help with that process.
There may also be a link with the template you use when you create the printed documentation.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Change column width for print table to report

Hi, want to make the first column in my table to be printed to report wider than the rest, for it contains the part numbers of about 16 chars and the other columns are the data of 4 each. Don't want to make all equally wide for I want to fit as many column as possible over the page. How can I do this?? Thanks for any help. Is there maybe another way to print in a table format?? Madri

Hi Madri,
Assuming you are using the Standard Report type with the Report Generation VIs, you can check out this KnowledgeBase entry that discusses how to customize the VI to generate a report with different column widths:
http://digital.ni.com/public.nsf/websearch/7AEC2CC2618D47DF86256D280058BDA5
Hope this helps,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Trouble with table of contents on printed documentation

hello everyone, im pretty new to robohelp and have had no
training what so ever, I am working on an existing project and the
first job i was given struck a problem, I had to add a topic to the
project so i did and i added it to the table of contents but..
now the printed documentation doesnt show it in the document
or in the table of contents can anyone help me, id be ever so
gratefull for a nudge in the right direction so i dont look bad
infront of my boss.
thanks steve

Welcome to the forum.
Common problem. When you first create the printed document,
it takes your TOC as the default layout at THAT time. Thereafter it
is quite independant.
So go to the print layout where you see what looks like the
TOC and you can then add the new topic to the print layout.
Sometimes people think this is a bug but it is by design. Not
everyone wants the print layout to be the same as their TOC.
Take a look at my website. There's a comprehensive topic on
printing from RH.

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!

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.

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

Error when trying to create printed documentation in RH 7

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

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

Problem with computing Font width while printing in Landscape mode

I have an application which prints a table and fills it with some text. I render it on a JComponent using the drawString(theStr, xPos, yPos) and the drawLine(rigtX, topY, rigtX, botY) methods in Graphics2D object. I want to take print-out of the table and also store the image of the table in, say, jpeg format. The print can be in Landscape or Portrait format depending on the size of the JComponent, which the user sets depending on the table size and the font size.
I have a paintTable( ) method which contains all the drawString( ) and drawLine( ) methods. This method is called from the paint( ) method of the JComponent to achieve normal rendering. The same method is called to get a BufferedImage of the Table. The same method is further called from the implementation of print( ) method from the Printable interface.
In the paintTable( ) method, I compute the pixel coordinates of the table grid lines and the texts positions in the tables depending on the font width and height obtained as shown below:
        // Set the Font
        Font theFont = graphics.getFont();
        theFont = theFont.deriveFont((float)TableFontSize); // TableFontSize is an int of value 8,9,10 etc.
        graphics.setFont(theFont);
        // Get the Font Size
        FontRenderContext frc = graphics.getFontRenderContext();
        float width = ((Rectangle2D.Float)theFont.getMaxCharBounds(frc)).width;
        float height = ((Rectangle2D.Float)theFont.getMaxCharBounds(frc)).height;
       System.out.println("FONT WIDTH HEIGHT [" + width + "," + height + "] ");I am getting the following value of width and height when the above print statement is executed with a value of 9 for TableFontSize. FONT WIDTH HEIGHT [18.0,11.3203125]
The problem I face is :
While Printing in Landscape mode the value of the 'width' variable printed as given above is becoming negative. Kindly see the values: FONT WIDTH HEIGHT [-9.37793,11.3203125]. This is happening ONLY DURING PRINTING IN LANDSCAPE MODE. This makes my calculation of table grid line coordinates and text positions completely wrong and the table goes out of place.
Kindly note that, there is no problem during normal rendering and BuffereredImage creation and also while printing in Portrait mode. The problem happens irrespective of Linux or Windows. The value of 'height' is always correct.
Kindly let me know: If the method I use to get the 'width' and 'height' is correct ? Is there any better way which will work fine in all platforms under all circumstances.
Kindly help me to sort out this issue.
Thanks a lot in advance and best regards
-acj123

I have extracted the relevent code and made a stand alone program.
The complete code is enclosed; including that for printing.
Kindly go through the same and help me to solve this problem.
Thanks again and regards
-acj123
import java.awt.*;
import java.util.*;
import java.awt.geom.*;
import java.awt.event.*;
import java.awt.print.*;
import java.awt.print.PrinterJob;
import java.awt.font.FontRenderContext;
import java.awt.image.BufferedImage;
import javax.swing.*;
import javax.print.attribute.*;
import javax.print.attribute.standard.*;
public class MyCanvas extends JComponent implements Printable, ActionListener
    int TableFontSize = 9;
    private Graphics2D graphics;
    public MyCanvas(JFrame frame)
        frame.getContentPane().setLayout(new BorderLayout());
        frame.getContentPane().add(this, BorderLayout.CENTER);
        frame.setJMenuBar(createMenuBar());
    public JMenuBar createMenuBar()
        JMenuBar menubar = new JMenuBar();
        JButton printButton = new JButton("Print");
        menubar.add(printButton);
        printButton.addActionListener(this);
        JButton imageButton = new JButton("Image");
        menubar.add(imageButton);
        imageButton.addActionListener(this);
        JButton drawButton = new JButton("Draw");
        menubar.add(drawButton);
        drawButton.addActionListener(this);
        JButton closeButton = new JButton("Close");
        menubar.add(closeButton);
        closeButton.addActionListener(this);
        return menubar;
    public void actionPerformed(ActionEvent evt)
        String source = evt.getActionCommand();
        if (source.equals("Close"))
            System.exit(0);
        if (source.equals("Image"))
            getImage();
            return;
        if (source.equals("Print"))
            printCanvas();
            return;
        if (source.equals("Draw"))
            repaint();
            return;
    public BufferedImage getImage()
        Dimension dim = getSize();
        BufferedImage image = (BufferedImage)createImage(dim.width, dim.height);
        this.graphics = (Graphics2D)image.createGraphics();
        System.out.print("\nImage ");
        paintCanvas();
        return image;
    public void paint(Graphics graph)
        this.graphics = (Graphics2D)graph;
        System.out.print("\nDraw ");
        paintCanvas();
    public void paintCanvas()
        // Set the Font
        Font theFont = graphics.getFont();
        theFont = theFont.deriveFont((float)TableFontSize);
        graphics.setFont(theFont);
        // Get the Font Size
        FontRenderContext frc = graphics.getFontRenderContext();
        float width = ((Rectangle2D.Float)theFont.getMaxCharBounds(frc)).width;
        float height= ((Rectangle2D.Float)theFont.getMaxCharBounds(frc)).height;
        System.out.print("FONT WIDTH HEIGHT [" + width + ", " + height + "] ");
        System.out.print(" SIZE "+ super.getWidth() +", "+ super.getHeight());
    public int print(Graphics graph, PageFormat pageFormat, int pageIndex)
        throws PrinterException
        if (pageIndex > 0) return Printable.NO_SUCH_PAGE;
        this.graphics = (Graphics2D)graph;
        graphics.translate(0,0);
        paintCanvas();
        return Printable.PAGE_EXISTS;
     * Interface method for Printing the Canvas on Paper
    public void printCanvas()
        PrinterJob printJob = PrinterJob.getPrinterJob();
        printJob.setPrintable(this);
        PrintRequestAttributeSet attr = new HashPrintRequestAttributeSet();
        if (super.getWidth() < super.getHeight())
            System.out.print("\nPrint PORTRAIT ");
            attr.add(OrientationRequested.PORTRAIT);
        else
            System.out.print("\nPrint LANDSCAPE ");
            attr.add(OrientationRequested.LANDSCAPE);
        Dimension dim = getSize();
        attr.add(new MediaPrintableArea(1, 1, dim.width, dim.height,
                                              MediaPrintableArea.MM));
        attr.add(new JobName("MyCanvas", Locale.ENGLISH));
        attr.add(new RequestingUserName("acj123", Locale.ENGLISH));
        if (printJob.printDialog(attr))
            try
                printJob.print(attr);
            catch(PrinterException ex)
                ex.printStackTrace();
    public static void main(String[] arg)
        JFrame frame = new JFrame("MyFrame");
        MyCanvas canvas = new MyCanvas(frame);
        frame.setSize(800, 600);
        frame.setVisible(true);
}

TOC Layout in Printed Documentation

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

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

Tables without borders print with borders

I have had trouble getting right-aligned graphics to print
when I print my documentation. So I am inserting the graphics into
tables, which eliminates that problem. My new problem is that,
although I have configured the tables to have no cell borders and
no table borders, they print with a thin border anyway.

If you are defining the borders and shading in the Table
Properties, you might want to consider also using the regular
Borders and Shading menu option. They seem to both apply, and I've
found it more reliable to set the "normal" borders than specific
table borders.
Hope that helps.

Anchored Table Width in Printed Documentation

Similar Messages

Maybe you are looking for