Re: What to look for in a technical editor

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

On Tue, 20 May 2003 10:27:49 -0700 (PDT), Sean Hower
wrote:

> 
> Me neither. But it's not the fact that an editor will
> insist on a structure or passage that you/I/anyone
> could demonstrate was technically inaccurate. It's
more
> a problem of having to go back through your document
> and undo the changes an editor makes if those changes
> are technically inaccurate. In some cases, this can
> take a lot of time if the changes are subtle enough
but
> still affect accuracy. In the very least it's a waste
> of the writer's time and the worst, it's a waste of
the
> company's money. And before you say "Use track
> changes," it's still still an unpleasant experience
> that could be avoided.
> 

Even *discussing* things that an editor should know are
fine the way they are is a waste of everyone's time.

Bonnie Granat

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

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.