RE: Re: What to look for in a technical editor

Subject: RE: Re: What to look for in a technical editor
From: MList -at- chrysalis-its -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 20 May 2003 15:34:27 -0400

What I look for in *any* editor is that they be good... for me.

If I get (few or many) tight, clear, well-considered edits that
leave my document in better shape than when I submitted it, then
that's a good editor.

There are fewer editors than writers.

The chances of finding an editor who already knows your industry
are much smaller than even the chances of finding a ready-trained
writer. So, as long as the ability and willingness are there,
you should probably resign yourself to doing a bit of training
and negotiation with your new editor.

Consider yourself lucky.
I'd LOVE to have an editor.
I'd LOVE to have even a budget to send my stuff out to a
freelancer, for a well-trained set of "fresh eyes" to have a go.



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:

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 for more resources and info.

Previous by Author: RE: RE: Re: How to handle when the scope changes?
Next by Author: RE: Requesting feedback for a user guide - good or bad idea?
Previous by Thread: 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