|
|
Re: "Which" and "that"Posted by R. Berg on May 10, 2001 In Reply to: "Which" and "that," which one when? posted by Massimo Mazzucco on May 10, 2001
: This is probably too basic a question for English-speaking people, but I do have this problem quite often (not being one of them). There is a rule, and most native speakers get it wrong anyway when writing. "Which" for nonrestrictive clauses and "that" for restrictive clauses. That doesn't help much, because you always have to stop and think which kind of clause you have. Sometimes in my schooling, nonrestrictive clauses were called nondefining clauses, and restrictive cl's were called defining cl's. A restrictive clause is one that restricts, or limits, the meaning of the word(s) it modifies. A nonrestrictive clause does not limit the meaning of what it modifies. If lifting the clause out of the sentence leaves intact the meaning of what remains, you have a nondefining clause. A nonrestrictive clause should have a comma at each end. A restrictive clause shouldn't have a comma at either end unless something else about the sentence requires a comma there. There are some exceptions. 1. With a nonrestrictive clause, if there are too many "thats" around, use "which" instead of "that" to avoid a jingly jangle. 2. With two correlative clauses (they modify the same word), use "which" instead of "that." 3. Use "which" if the clause is so far from what it modifies that people would get lost looking for its referent. The usual mistake of writers is to use "which" when "that" is correct, not the other way around. I think they do that because "which" is associated with writing more than with speech and consequently has acquired an air of formality or correctness. "Which" occurs more often in writing, but not because it's a better word than "that"; it's because the kinds of clauses that properly take "which" are rare in speech.
|