Re: What to look for in a technical editor

["Bonnie Granat" <bgranat -at- editors-writers -dot- info>]

From: "Mark Baker" <mbaker -at- ca -dot- stilo -dot- com>

:
: Bonnie Granat wrote:
:
: > Nor could I more strongly disagree. Without knowledge of the product, an
: > editor can absolutely *ruin* documentation and cause much time to
: > be wasted
: > while the writers and developers deal with the mess an ignorant editor
: > creates.
:
: No editor should be able to ruin documentation, because no editor should
: ever be allowed to touch the documentation source. The editor's role is to
: provide feedback to the writer. The writer, and only the writer, should ever
: be allowed to touch the source. If you want to give editor's power, give
: them sign-off rights, but never never never let anybody other then the
: writer touch the text.
:


When I said "ruin" I was talking not about making changes in the source, but
raising grammatical issues that change meaning or introducing errors when
giving feedback to writers and wasting time. A poor choice of words on my
part. Documentation is not "ruined" by wasting time.


___________________________________
Bonnie Granat
Granat Editorial Services
http://www.editors-writers.info




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

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.