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: stopping photocopying, take II From:Rowena Hart <rhart -at- XCERT -dot- COM> Date:Wed, 27 Jan 1999 10:28:10 -0800
Scott,
Controlling photocopying may not apply to you, but it is
a serious security issue for some organizations who
deal with extremely sensitive proprietary technology,
military secrets, or financial information.
There are a great number of people on the list who are
interested in this subject, and I've never seen it discussed
before. It's important to remember that a lot of people
need a three or four days to respond to messages -- they
may be behind on their digest reading, or too busy to
respond the first day a thread is discussed. Give it time
and this thread will die a natural death. In the meantime,
learn to use the delete key.
-----Original Message-----
From: Scott Havens <SHavens -at- ELCOTEL -dot- COM>
To: <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Wednesday, January 27, 1999 10:10 AM
Subject: Re: stopping photocopying, take II
>I can't believe this thread has gone on so long. Just about every
>suggestion I've read would cause serious impairment for those who were
>intended to READ the books in the first place, so I think somebody's
>suggestion that we try to CONTROL our documentation instead of making it
>"uncopiable" is a much better idea.
>
>Or maybe we should just make all our manuals from some extremely
>unstable material, so that the light from the copy machine would cause
>them to explode and burn. Just another helpful (if not constructive)
>suggestion...
>
>SRH
>
>
>From ??? -at- ??? Sun Jan 00 00:00:00 0000==
>