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.
One should consider that the client is familiar enough with the intended
audience to know what idioms are appropriate. Both these metaphors have
been around for a *very* long time, but I've never seen them used in a
technical document or even in a marketing context.
Patty B's #2 suggestion captures the essence of what your client wants
to say, but on the other hand........*ahem*.....it's not what they have
asked for. As Patty also suggested, using metaphors in tech docs
frequently puts both the writer and the reader on thin ice without a
paddle, so try not to rock the vote.
I'm quite surprised that many of the folks on this list have not heard
this expression before and that some view it negatively. The techwirler
gang tend to be more literate. This may be good reason to double-check
with your client to ensure that all of the intended audience will
understand what they are reading. "Two-edged sword" and the
"double-edged" derivative, originate from a bible passage. The modern
version of this expression is, "cuts both ways." Maybe, in this
post-Christian era, the link to this metaphor is breaking down which
gives another reason to double-check with the client. If both the idioms
have to stay, the associated text must be *very* clear in case a reader
has never read the Bible (two-edged sword) or seen a production of
Fiddler on the Roof (...but then on the other hand.....).
-Darren
-----Original Message-----
From:
techwr-l-bounces+darren -dot- butler -dot- ctr=robins -dot- af -dot- mil -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+darren -dot- butler -dot- ctr=robins -dot- af -dot- mil -at- lists -dot- techwr-l -dot-
com] On Behalf Of Blount, Patricia A
Sent: Friday, January 29, 2010 9:21 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Mixing metaphors?
To Deborah,
I would rewrite the passage in several different manners and allow your
client to choose. In this case, the double-edged vs. two-edged sword
debate is meaningless to me - I'm not familiar with the expression. My
reaction to it is negative and I wonder, would the client want their
product to be perceived negatively?
I think that's one of the problems with metaphors, idioms, etc. How can
we be sure the audience understands it? If our charge as technical
communicators is to produce understandable information, I'd drop the
whole metaphor in favor of clear writing.
Examples:
1 Increased XXX capacity enables significantly lower cost functionality
(and I am not sure what actually means), but it also increases
complexity.
2 Consider the trade-offs when deciding to increase XXX capacity; as
capacity increases, cost is lowered but complexity is increased.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as
Darren -dot- Butler -dot- ctr -at- robins -dot- af -dot- mil -dot-
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
