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.
Do you think the commas are confusing? And remember: over here people
often use 'which' when you _can_ use 'that'. And it is taught that way,
and is 'correct'. I just think there's a difference between correct
received usage and absolute clarity. And the correct received usage of
'which' where you can also use 'that' can be unclear, because the reader
isn't sure if the clause is defining or non-defining.
Just to keep this tech-writing relevant, I will always advocate using
'which' only with non-defining clauses becaue it's the only
non-ambiguous way to use it in that type of clause. And tech writing
should never be ambiguous.
-----Original Message-----
From: lyndsey -dot- amott -at- docsymmetry -dot- com
[mailto:lyndsey -dot- amott -at- docsymmetry -dot- com]
Sent: 16 February 2004 16:14
To: Elizabeth O'Shea
Cc: TECHWR-L
Subject: Re: It's what It's
Elizabeth O'Shea writes:
> I
> teach them this mnemonic: if you can put a comma before which and the
> sentence still makes sense, then you should use 'which' instead of
> 'that'.
My mother, a grammar nazi, taught me this mnemonic, which might be
easier to
remember since it doesn't mention confusing commas: "Use 'which' only
when
you can't use 'that'."
~~~~~~~~~~~~~~~~~~~~~
Lyndsey Amott
www.docsymmetry.com
Winnipeg, MB R3G 2J3
