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:18:43 -0400
Gene Kim-Eng <gene -at- genek -dot- com>
>I think where you lost me is at the point where the editor moved the comma
>rather than making a redline or entering a change-
>tracked revision and returning the edits to the writer for
>review/approval. In my (admittedly few and far between) experiences
>with editors, they worked with me in an cooperative relationship rather
>than just rewriting my work without my participation.
I didn't move the comma. I was trying to restate Bill's case as I understood what he wrote (but not, I think, what he meant).
As for working relationships with editors, they vary depending on the situation. Certainly your way is ideal in many circumstances, and I've worked that way (as writer, as editor, and as compositor). In my current gig, however, most of what I edit is ephemeral in nature (Web pages, PowerPoint slides, marketing guff) and the "authors" are people with a point to make but limited or nonexistent writing skills. Yes, sometimes I have to talk with them to find out wtf they meant to say before I can rewrite it, but most of the time I just play the part of gonzo editor and make changes on my own authority. In fact, we have a situation where the roles you describe are reversed, because the document owner reviews my edits and has to negotiate further changes with me, rather than the other way around. That's not the way I would approach technical engineering documents, of course.
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.