Re: What to look for in a technical editor

Subject: Re: What to look for in a technical editor
From: "Michael West" <mbwest -at- bigpond -dot- net -dot- au>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 21 May 2003 08:08:31 +1000


> In my one really bad experience with
> an editor [ ... ] who kept demanding
> an endless series of pedantic style
> changes, [ ... ] had he been capable of doing more
> technical reviews I might have been ...[etc]

It has long been standard practice in technical publishing
to distinguish between content edits and style edits, and
to use different specialists to perform the two functions.

I am aware that some publishing organizations
are oblivious to, or choose to ignore, this standard
practice, and it certainly shows up in their publications,
But it is really the only way to run a technical publishing
operation. Expecting subject-matter experts to be
intelligent and capable style editors, or expecting style
experts to have detailed technical knowledge of an
emerging technology, usually ends in unsatisfactory
outcomes for the consumer and, somewhat less
importantly, frustrating working conditions for writers.

When it works best for everyone is when there is the
added, unexpected benefit of having a content editor
exhibit a facility for clear, concise language, or of having a
style editor develop an easy familiarity with technical
detail. These things do happen -- but to *expect* them is
to set up both writers and readers for disappointment.

--
Michael West
Melbourne, Australia


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Robohelp X3, from eHelp, lets you quickly and easily create
professional Help systems for all your Windows and Web-based
applications, including Net.

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.

Order RoboHelp today: http://www.ehelp.com/techwr-l

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



References:
RE: Re: What to look for in a technical editor: From: GeneK

Previous by Author: Re: List of Figures (LOF) and List of Tables (LOT) in Software User Guides
Next by Author: Re: What to look for in a technical editor
Previous by Thread: RE: Re: What to look for in a technical editor
Next by Thread: RE: Re: What to look for in a technical editor


What this post helpful? Share it with friends and colleagues:


Sponsored Ads