TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
(I searched the TECHWR-L archive, the Microsoft site, and the WOPR site, but
didn't find any answers to this problem.)
Some of my users are still requesting printed documentation for our
internally written, internally used, Windows NT applications. As we use
RoboHelp for the Windows online help files, the quickest (albeit not the
prettiest) way for me to generate printed documentation is to use the File >
Generate > Printed Documentation function on RoboHelp. I have to do a bit of
massaging to get the printed document to look acceptable. I then store it in
an electronic document management system, which (among other things)
generates a URL from which users can access the document.
Here's the problem: the URL launches Word Viewer, and in Word Viewer, the
graphics don't display. If the user selects File > Open for Editing from the
Word Viewer menu, the document opens in Word and the graphics look just
fine. But that's a pretty inelegant solution.
In case it matters, the graphics files are screen shots captured with PSP 5
and saved as bitmaps. I did not use the RoboHelp shed editor on any of them,
but just in case, I deleted them and re-inserted them using Word's Insert >
Picture > From File function.