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.
Subject:Re: Converting HELP files to RTF files From:rjl -at- BOSTECH -dot- COM Date:Fri, 22 Mar 1996 16:55:46 EST
At 10:31 PM 3/19/96 GMT, Charles Good wrote:
>It's bad enough that the standard help engine
>allows you to copy text (which you can paste into a notepad window).
Then Sue Gallagher said:
>And I'm not sure why you think this is a bad thing. I have often
>taken advantage of this capability, and even automated it for my
>users by including a Copy macro attached to a button. It's great
>for including sample text -- batch files, code snipettes, etc.
It's a sticky issue at our company, and some others. In fact, it was
brought up at our department meeting just today. We're shipping our docs
in online form only, on a CD-ROM. Customers are starting to ask us "Saaaay,
do you mind if we cut-n-paste your procedures into our own internal
documents?" We're not too keen on that, and plan to start including some
limited license language.
My boss also pointed out that our customrs could copy files,
delete some text, and they've then got nicely designed templates in
Information Mapping (TM) layout. At our expense.
Rick Lippincott
Boston Technology
Wakefield, MA
rjl -at- bostech -dot- com
