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: Dos and don'ts for R & D From:"Bergen, Jane" <janeb -at- ANSWERSOFT -dot- COM> Date:Tue, 24 Feb 1998 08:55:29 -0600
Well, if anyone DOES have a checklist like this, please post it to the
GROUP (or copy me, too, please). My engineers and QA staff have asked
for this kind of thing but I have simply not had the time (I'm the lone
writer here).
Thanks,
Jane Bergen
P.S. Steve Williams, check your email settings. I'm seeing a "=20=" at
the end of each line. Thanks.
Jane Bergen, Technical Writer,
AnswerSoft, Inc. Richardson, TX
(972) 997-8355
janeb -at- answersoft -dot- com
On Tuesday, February 24, 1998 1:14 AM, Steve Williams
[SMTP:steve -dot- williams -at- ASCOMTATECO -dot- SE] wrote:
> I'd like to put together a list of "Dos and Don'ts" to be used by our
R&D =20=
> =20
> people
> when checking the factual content of technical documents. It seems
that =20
> they all have different ideas on what has to be checked and how
suggested =20=
> =20
> changes should be indicated in the document.
>
> Before embarking on such an enterprise I thought it best to check with
=20
> you people in case someone has some pointers. Perhaps someone has
already =20=
> =20
> done something like this.
>
> TIA
>
> /Steve Williams =20
>
>
>
> Send commands to listserv -at- listserv -dot- okstate -dot- edu (e.g., SIGNOFF
TECHWR-L)
> Search archives at: http://listserv.okstate.edu/archives/techwr-l.html,
