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: Mixing metaphors? From:Geoff Lane <geoff -at- gjctech -dot- co -dot- uk> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 29 Jan 2010 07:33:24 +0000
On Friday, January 29, 2010, Deborah Hemstreet wrote;
> Wow, a lot of food for thought...
> Well, here is the context:
> However, increased XXX capacity can be a two-edged sword. On one hand,
> it significantly enables lower cost functionality. But on the other
> hand, the increasing complexity and cost of XXX designs has prevented
> many vendors from using, or taking full advantage of, the capabilities
> of XXX.
> MUDDIER and muddier, one hand is good, the other is bad... and if I CUT
> you with a two-edged sword you are more seriously wounded than with a
> single-edged sword...
> The client wants this a INFORMAL and UNTECHNICAL as possible (ARGH)!
---
Just to throw in another wobbly: I'd not heard a of a "two-edged
sword" until this thread. Where I live, it's "double-edged", which is
in the OED with the meaning, "adj. presenting both a danger and an
advantage." So if you leave out the word "sword" you're left with
correct English and a single metaphor, viz:
However, increased XXX capacity can be double-edged. On one hand, it
significantly enables ...
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-