RE: What to look for in a technical editor

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

I couldn't agree more. NO REVIEWER should be working in source. We use
Acrobat as a review mechanism, and generate a report of comments at the end.
Works brilliantly!

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


::: -----Original Message-----
::: No editor should be able to ruin documentation, because no 
::: editor should
::: ever be allowed to touch the documentation source. 



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

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.