TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: What to look for in a technical editor From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sun, 18 May 2003 07:09:11 -0400
>The point is that it's very easy for an editor who doesn't understand the product to correct a sentence and change the meaning. What the editor may think is a logically meaningless string of words may be that -- but it may also not be that at all. It may be meaningless to the editor only.
>
Bonnie,
I think we all agree (you, Bill, and I) on that statement. I just didn't think that was what Bill actually _said_. And because he said it in a way that suggested he was disagreeing with me, I took exception to it.
I do not think that having a technical understanding of the content is more important or less important for an editor than the ability to turn non-English into English. I think both are prerequisites, and if I am presented only with candidates who have one ability but not the other I will reject all of them and look for more candidates.
---
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.