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: Proofreader vs. TE/ TW From:Julie Knoeller <jknoelle -at- CISCO -dot- COM> Date:Fri, 22 May 1998 11:52:52 -0700
>What is the difference between a technical editor and a proofreader?
>And what abilities do you think TWs have that proofreaders do not?
Generally speaking, editorial responsibilities break down as follows:
*proofreading (checking text against an original for errors)
*copyediting (editing grammar, spelling, punctuation, and format--plus
proofreading)
*substantive editing (editing organization, style, transitions, tone,
reader appropriateness, completeness, consistency--plus all of the above)
*technical editing (all of the above plus technical accuracy and consistency)
Proofreading is something the author should be doing before he or she hands
off a doc to an editor though I frequently see docs that have not even had
spellcheck run on them--this is generally unacceptable condition and I
usually hand them right back to the writer. It's not the editor's job to
compensate for sloppiness.
>
>
>
>
>