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:FW: wording for training materials From:"Anita Lewis" <anital -at- threerivers-cams -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 25 Oct 2002 16:06:39 -0500
See my comments inserted below:
Anita Lewis
Customer Training and Support
Three Rivers Systems, Inc.
St. Louis, MO
Questions:
>1. I expect that a writer, whether a junior or a senior, should be able to
>make all the editing changes marked on a document without missing several.
>Is this really too much to expect?
No, I don't think this is too much to expect. On a 500 page doc, I had to make corrections, and to keep track of them I placed a check mark in a different color than the editor's marks and then dated and initialed each page completed. After I finished, I went back through to make sure all edits had been addressed.
For those of you who have an editor (or are the editor), how many
>editing passes typically occur? Does the editor typically perform a final
>pass on each doc before it is published? Is the editor expected to sign
>off on each doc before it is published?
As the editor, I used standard proof marks and wrote comments if something was unclear. I typically only edited so things adhered to the style guide, or, in extreme cases of garbled text, I'd mark it as rewrite phrase. Depending on the writer, I sometimes offered a suggested correction, but I always noted it as that, a suggestion. I've had a couple of writers argue their point or inquire why something was changed. I just worked it out as best I could, and sometimes things got changed, and sometimes things didn't. I'd make two or three passes depending on the time I had and who else was looking at it. The writer had the final pass, unless there were some weird circumstances involved.
>4. Others have stated that writers who deliberately ignore changes
>requested by the editor should be reprimanded. (Note: this action has been
>recommended when the editor is the manager, or when it is clearly
>understood that the editor has final say.) How is this typically handled
>in your group? Does the editor/manager pull the writer aside and say "hey,
>Joe, you need to start making those editorial changes"? Is the writer's
>work then carefully monitored for the next few projects? How *do* you
>handle this without crossing the line into dictatorship?
I'd let the manager handle situations like this. I was not in a managerial position (nor will I ever be). I'd let the manager know what the situation was and washed my hands of it from that point. As the person being edited, if I was unclear or had argument, I'd communicate that to the editor, but I usually accepted their decision as final. Let people do their jobs was my theory.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Buy ComponentOne Doc-To-Help 6.0, the most powerful SINGLE SOURCE HELP
AUTHORING TOOL for MS Word. SAVE $100 on the full version and $50 on the
upgrade. Offer ends 10/31/2002 (code: DTH102250). http://www.componentone.com/d2hlist1002
All-new RoboHelp X3 is now shipping! Get single sourcing, print-quality
documentation, conditional text and much more, in the most monumental
release ever. Save $100! Order online at 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.