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.
Re: using a slogan on a resume (really copyeditors)
Subject:Re: using a slogan on a resume (really copyeditors) From:Paul DuBois <paul -at- kitebird -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 17 Jan 2003 11:50:23 -0600
On Fri, Jan 17, 2003 at 09:53:02AM -0700, Peter Swisher wrote:
> I used to work at a larger company that had all kinds of publication
> support: 2 copyeditors, schedulers, layout artists, templates, style
> guides and so forth. It was a great experience, but I spent a lot of
> time arguing with the copyeditors. The line you draw really depends on
> the audience and how you can most efficiently help them complete their
> task.
>
> My current company has no copyeditors and their published documentation
> shows it. I have found 3 out of 6 brochures that had blatant errors:
> the types you commonly find in instant messages or e-mails. When I find
> grammatical errors, something is obviously wrong! I am hoping to
> convince them to outsource a copyediting service.
My experience with copyeditors is that they improve my writing in
some ways, but they have to be watched closely. :-)
Copyeditors are helpful to me in the sense that they know more grammar
than I do (which is none; I no speaka The Good English). The grammatical
changes they make in most cases thus are an improvement on the original
writing.
Problems comes about when copyeditors start changing things such as
voice or tone. If I'm using conversational tone with a lot of you's and
I's, and the copyeditor starts making the writing more formal, then
it begins to no longer sound like me. In such cases, I've had to ask
the copyeditor to revert such changes, or, if necessary, ask a higher-level
editor to step in and instruct the copyeditor to do so. But it's rarely
been necessary to get into a fight about it. The editors I've worked
with generally have been pretty accommodating if you can make the case
why you don't like certain changes.
I find it instructive to compare my original files with the submitted
files after the copyeditor has been through them. This helps me to see
just where changes were made and learn from them. For example, if a
particular type of change gets made many places in an earlier chapter,
that's a change that I incorporate into my writing so that the copyeditor
need not find and make as many corrections in later chapters.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
---
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.