Re: What to look for in a technical editor

["Richard G. Combs" <richard -dot- combs -at- voyanttech -dot- com>]

Martin Smith wrote:

> One of my favorite examples of Andrew's point is that of an editor who
> insisted on "correcting" all of the spelling errors in a source code
> listing. The alleged spelling errors were not in the comments. The editor
> couldn't understand why the source code wasn't written in plain English.

I love it! Did he "fix" all the capitalization errors, too? And what about
the underscores? <ROTFL>

Richard


------
Richard G. Combs
Senior Technical Writer
Voyant Technologies, Inc.
richardDOTcombs AT voyanttechDOTcom
303-223-5111
------
rgcombs AT freeDASHmarketDOTnet
303-777-0436
------







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

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.