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: Honestly -- when an SME completely REWRITES your text ... GEEZ!
Subject:RE: Honestly -- when an SME completely REWRITES your text ... GEEZ! From:"Downing, David" <DavidDowning -at- users -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 23 Oct 2008 08:40:32 -0500
I thought everyone might be interest to know how I handled this and how
it turned out. I tried to revise the test to use the best parts of what
he gave me and what I had already. Then I sent it to him with the email
below -- which I've snipped a little to remove some material that might
be considered proprietary. He ended up approving the revision with no
further changes. I can't say we all lived happily ever after, because
this is the real world, but this particular incident turned out well.
Here's the email I sent him. Not the one rather interesting
slepp-checker blooper where I picked the wrong word from the list of
corrections. The word I wanted was "verbatim." I'm wondering if he took
any weird alternative meaning from what I actually said.
Here's what I cam up with as the revised text for the [snip] Table.
This is a kind of hybrid of what you sent me and what was there. Your
text included some I important points I missed, such as [snip]. However,
I couldn't use it verboten because it wasn't in line with our department
style. Furthermore, I thought some points were better placed in an
introductory section, rather than in the discussion of the fields. I
also felt that in some places where you referred to the [snip] code, the
reference should really be to the table entry, since we're talking about
the actually [snip] data, not just the code. I also had some passages I
really want to keep from my original. This has created some redundancy,
but I figured it would ultimately be up to our editor how to resolve
this.
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-