Skip to main content
Known Participant
April 25, 2006
Question

Print Only One Page

  • April 25, 2006
  • 2 replies
  • 2775 views
Is there a solution for my users to print only one page of a topic? I would like to use a print button for this.
Thanks,
Duke
This topic has been closed for replies.

2 replies

Inspiring
May 1, 2006
Yes, you'll need to update the Word document each time you make a change to the corresponding topic. However, this process shouldn't take too much time. You should consider using the Status field for each topic, which can be set to "In Progress," "Ready for Review," and "Complete." Assuming that each topic is marked "Complete" when you begin making this month's changes, you can:

1. Mark each edited topic "In Progress."
2. Sort by Status in RH's Topics tab to identify all WIPs.
3. Generate printed output that includes only those topics.
4. Reimport the Word document.

As for where to store them - I don't see any harm in generating to the root of the source file. Personal preference, however, would lead me to store the files in separate folders. It really depends on your folder schema, in my opinion.

-Chet
Inspiring
May 1, 2006
Oddly enough, if you generate printed documentation to the default SSL folder and then attempt to link the output to the CHM file, you will NOT be prompted to copy the file to the root project directory, and the link will NOT work. (It didn't work for me, anyway.) So I'd generate to the root directory.

-Chet
Known Participant
May 2, 2006
Deleted
RoboColum_n_
Legend
April 25, 2006
Hi Duke. If you are referring to printing a page of a CHM file there is already an inbuilt facility when the print button or menu item is used. The user is asked whether they wish to print only that topic or all the topics under it in the TOC.
Known Participant
April 25, 2006
I'm actually using RoboHELPHTML X5 WebHelp. Any solution for this?
Known Participant
April 26, 2006
Good morning, Your Grace.

I had a similar problem with long pages (client wanted complete end-to-end procedure in one numbered flow; users wanted one screenful of text at a time). I split the procedures into workable chunks (topic.htm, topic_a.htm, topic_b.htm) with little 'More' links at the bottom of the page.

It was a little more work for me (if I edited a topic and it got longer, I had to redistribute the text into the following topics), but if this is going to be pretty stable, I would try it - because the users LOVED it. Only be sure to test it yourself on the user-typical resolution so that you know that the topics are indeed one page both on the screen and printed.

My .02 USD,
Elisa

Hi Elise,

I understand your solution also would work, but for now I guess I will follow Peter's suggestions since I have inherited topics of over 40 pages in some cases and I just don't have the time to start breaking them up into their own topic sections at this point and still meet my deadline.

Thanks everyone!