RE: What to look for in a technical editor

["Bill Swallow" <wswallow -at- nycap -dot- rr -dot- com>]

I am currently functioning as a technical editor, and I couldn't agree more
with Andrew and Bonnie. If you don't know the subject, there is no way you
can do a good editing job. I edit first for technical accuracy, a close
second for technical implementation of templates and pre-press work, and
third for grammar.

IMO, a good tech writer can be trusted to write grammatically correct
documents, can be trusted to get pre-press/publishing/templates implemented
correctly, and can hit the tech stuff very close if not on the bull's-eye.
But, the most difficult to nail down is tech accuracy, the second is
by-the-book formatting and publishing, and the third *should* be grammar.

And, to stop rambling and offer something intelligent...

I'd rather send a doc out the door with a typo in it or a subject/verb
disagreement than with links that don't work or info that's technically
inaccurate.

Bill Swallow
wswallow -at- nycap -dot- rr -dot- com



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

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.