You are currently browsing the category archive for the ‘formality and tone’ category.
If you believe the grammar doomsayers, the English subjunctive is dying out. But if this is the end of the grammatical world, I feel fine — and I say that even though I often mark the subjunctive myself.
The most talked about use of the subjunctive is in counterfactuals:
(1) Even if I were available, I’d still skip his party.
For many people, marking the subjunctive here is not required; either they never mark it, using the past indicative form was instead, or they (like me) sometimes mark it with were, and sometimes leave it unmarked with was. For this latter group, the choice often depends on the formality of the setting. I’m calling this “not marking” the subjunctive, rather than “not using” it, because it seems less like people making a choice between two moods for the verb and more like a choice between two orthographic/phonemic forms for it.
It’s similar to the alternation for many people (incl. me) of marking or not marking who(m) in the accusative case, discussed by Arnold Zwicky here and here, and Stan Carey here. That said, I believe that (at least some) people who never use were in (1) do not have a grammatical rule saying that counterfactuals trigger the past subjunctive, and I’m not worried about that either.
This blitheness about the subjunctive does not go unmourned. I recently found myself being Twitter-followed by someone whose account just corrects people who fail to use the subjunctive in sentences like (1).* And Philip Corbett, associate managing editor for standards at the New York Times, annually rants about people failing to mark the subjunctive. Consider one of Corbett’s calls to man the ramparts, which he begins by quoting, in its entirety, a 90-year-old letter complaining that the subjunctive must be saved from impending destruction.** Corbett continues:
“[...] despite my repeated efforts to rally support for [the subjunctive] the crisis has only grown. For those few still unaware of the stakes, here is a reminder from The Times’s stylebook”
What are the stakes? What would we lose without the subjunctive? Corbett cites sentences such as these:
The mayor wishes the commissioner were retiring this year.
If the commissioner were rich, she could retire.
If the bill were going to pass, Secretary Kuzu would know by now.
If these were the stakes, I’d ditch the subjunctive. Corbett points out that in each of these we’re referring to a counterfactual condition, which should trigger the subjunctive. But note that using the indicative/unmarked was doesn’t make that any less clear. There is nothing to be gained from using the subjunctive in these cases but a sense of superiority and formality. (Not that I’m against either of those.)
But here’s the weird thing: all this defense of the subjunctive, all these worries — they’re all only about the past subjunctive. And the past subjunctive is weird, because it’s only marked on be, and it’s just a matter of using were for singular as well as plural. For everyone worrying that this is some crucial distinction, please note these sentences where it is insouciantly the same as teh indicative form:
(2a) The mayor wishes the commissioners retired last year.
(2b) If the commissioner wanted to, she could retire.
(2c) If the bills were going to pass, Sec. Kuzu would know by now.
If anything, the loss of past subjunctive were strikes me as regularization of English, the loss of the last remaining vestige of what was once a regular and widespread marking system. Losing the past subjunctive makes English more sensible. I don’t see that as a bad thing.
And anyway, the subjunctive probably isn’t going to disappear, not even the past subjunctive. The past subjunctive is, to my knowledge, necessarily marked in Subject-Auxiliary Inversion constructions:
(3) Were/*Was I a betting man, I’d say the subjunctive survives.
A quick look at Google Books N-grams makes it look like were subjunctive marking has been relatively constant over the last 40 years in written American English, so maybe this is all just a tempest in a teacup.
Plus all of this worry about the subjunctive ignores that the present subjunctive is going strong.*** I’ve written about sentences where the present subjunctive changes the meaning (though I wrote with a dimmer view of the subjunctive’s long-term prospects), and Mike Pope supplied an excellent example:
(4a) I insist that he be there.
(4b) I insist that he is there.
In cases where marking the subjunctive is important, it’s sticking around. In cases where it isn’t important, and the subjunctive follows a strange paradigm, identical to the indicative for all but one verb, it may be disappearing. This is no crisis.
Summary: People who write “if I was” instead of “if I were” aren’t necessarily pallbearers of the English subjunctive. It may be regularization of the last remaining irregular part of the past subjunctive, with the present subjunctive remaining unscathed. And if the past subjunctive disappears, there will be, as far as I can tell, no loss to English. Go ahead and use it if you want (I often do), but to worry that other people aren’t is wrinkling your brow for nothing.
*: I do respect the tweeter’s restraint in seemingly only correcting people who’re already talking about grammar.
**: That this destruction has been impending for 90 years has somehow not convinced the ranters that their panic may be misplaced. Also, Corbett keeps titling his posts “Subjunctivitis”, which I think sounds great, but not in the same way he probably does. -itis usually means an unwelcome inflammation of the root word, and I can’t help but see all this as an unhelpful inflammation of passions over the subjunctive.
***: In fact, and I think this is pretty cool, (Master!) Jonathon Owen directed me to a classmate’s corpus work suggesting that for at least some verbs, marked subjunctive usage is increasing.
If someone were to lend me a time machine and ask me to go back and figure out exactly what first set me down my road to dedicated descriptivism, I would first ask them if perhaps there wasn’t a better use for this marvelous contraption. But if they persisted, the coordinates I’d start with would be my elementary school days. I suspect it was some time around then that I first asked for permission to do something and was met with one of the archetypal prescriptions.
“Can I go to the bathroom?”, I surely must have asked, and just as surely a teacher must have answered, “I don’t know, can you?”
The irritation that I felt at this correction was so severe that even though I can’t remember when this happened, nor who did it to me, I still can call to mind the way it made me seethe. It was clear to me that the pedant was wrong, but I couldn’t figure out quite how to explain it. So, at the risk of sounding like I’m trying to settle a two-decade-old grudge, let’s look at whether it makes sense to correct this. I say that the answer is no — or at the very least, that one oughtn’t to correct it so snootily.
Let’s examine the “error” that the authority figure is correcting. Can, we are told, addresses the ability to do something, whereas may addresses permission. Mom said I can count to ten means that dear ol’ Mum believes in my ability to count to ten, although she may not want me to do so; Mom said I may count to ten means that Mum is allowing me to do so, although she need not believe that I am able to.*
At any given time, there are a lot of things that one is capable of doing (can do) and a lot of things that one is permitted to do (may do), and a few things that fall into both categories. The prescriptivist idea is that there is a fairly clear distinction between the two categories, though, and so it is important to distinguish them.
Except, well, it’s not so important after all; can and may were tightly intertwined in early English, and were never fully separated. The OED lists an obsolete usage [II.4a] of may as meaning “be able; can”. This is first attested in Old English, and continues through to at least 1645. Furthermore, may meaning “expressing objective possibility” [II.5] is attested from Old English to the present day (although it is noted as being rare now). Examples of these are given in (1) and (2). So we see that may does not always address the issue of permission, that may has encroached upon can‘s territory at times in the past and continues to do so to this day.
(1) No man may separate me from thee. 
(2) Youth clubs may be found in all districts of the city. 
As for can, there’s no historical evidence I found of it referring to permission in the distant past. Back then, may was apparently the dominant one, stealing usages from can. The OED gives a first citation for can meaning “to be allowed to” in 1879, by Alfred, Lord Tennyson, and does call the usage colloquial, at least on the British side of the pond. But still, we’ve got it attested 130 years ago by a former Poet Laureate of the UK. That’s a pretty good lineage for the permission usage.
Furthermore, I think (at least in contemporary American English) that the may I usage is old-fashioned to the point of sounding stilted or even affected outside of highly formal contexts. Just to back up my intuition, here’s the Google Books N-grams chart comparing May I go and Can I go:
You can see there’s a changeover in the mid-1960s, when the usage levels of May I finish plunging and Can I starts rocketing away. As you well know, this sort of fairly sudden change in relative frequency tends to generate a backlash against the newly-prominent form as a sign of linguistic apocalypse, so there’s no real surprise that people would loudly oppose permissive Can I. As always, the loud opposition to it is one of the surest signs that it’s passed a point of no return. By my youth, Can I was ensconced as the question of choice, and nowadays, I doubt many of our kids are getting being corrected on it — though it remains prominent enough in our zeitgeist to function as a set-up for a range of uninspired jokes.
So historically, what can we say of can and may and permission and ability? We’ve seen something of a historical switch. In the distant past, may could indicate either permission or ability, while can was restricted to ability. Over time, may‘s domain has receded, and can‘s has expanded. In modern usage, can has taken on permission senses as well as its existing ability senses. May, on the other hand, has become largely restricted to the permission sense, although there are some “possibility”-type usages that still touch on ability, especially when speaking of the future:
(3) We may see you at Breckenridge then.
The can expansion is a bit recent in historical terms, but that still means it’s been acceptable for over a hundred years — judging by the Tennyson citation — and commonplace for the last fifty or so. The recency explains the lingering resentment at permissive can, but it doesn’t justify it. Permissive can is here to stay, and there’s no reason to oppose it.**
*: Not to telegraph my argument, but even here I find Mom said I can count to sound more like a statement of permission than ability.
**: I have some thoughts on whether it’s really even possible to draw a clear line between permission and ability — in essence addressing the question of whether the smearing together of can and may is an accident or inevitability. I’ll try to put them together at some point & link to them, but given my history of failing to follow through with follow-up posts, I’m not going to leave it as only a possibility, not a promise.
All right, it’s time for the second grammar review section; last week’s looked at contractions and their homophones, and today I’ll look at who and whom.
The simplest advice I can give about using whom is not to. Contemporary English doesn’t require whom in any situation other than exceedingly formal writing. Just use who all the time.
Before you think that I’m just some lazy linguistic anarchist for suggesting this, let me point out that I am only agreeing with John McIntyre, former president of the American Copy Editors Society and an editor at the Baltimore Sun, who writes:
“There is a problem that even educated writers have with figuring out whether a subordinate clause should begin with who or whom. If you have that difficulty, you can, except in the most formal circumstances, just use who.”
But perhaps you have a reason to use whom, whether because you need to write very formally, or because you have a stodgy teacher/superior who insists upon its use, or because you’re just good old-fashioned curious about the niceties of English grammar. In that case, here’s my advice on how it’s used.
In short, who and whom are the same word with different case markings. Who is in the nominative (or subjective) case, and whom is in the accusative (or objective) case. That’s the only difference — not that one is more formal than the other or anything like that.*
So knowing how to use whom is simply a matter of knowing when each case should be marked. Unfortunately, English rarely marks case, so it’s not something that we, as native English speakers, are used to thinking about. In fact, aside from who(m), the only other sort of case marking in English is on personal pronouns, and even then only on a few of them.** I and me, for instance, are nominative and accusative versions of each other, as are he and him, she and her, we and us, and they and them.
The first guideline, then, is to use whom wherever it replaces an accusative pronoun (me, him, her, us, them). So:
(1a) Who saw you? (She saw me.)
(1b) Whom did you see? (I saw her.)
(1c) Whom did you give the gift to? (I gave it to her.)
Your intuitions with personal pronouns’ cases are probably pretty accurate, so when you can rephrase the sentence, you’ll do well. The trouble is that you can’t always easily replace who(m) with a personal pronoun. For instance:
(2a) The fellow who(m) I saw at the bus stop
(2b) I don’t care who(m) did it.
(2c) Who(m)ever the werewolf stalks is in trouble.
Since there’s no question to answer here, you need to get a bit cleverer and look at the syntactic structure of the sentence. In these examples, who(m) is filling for a missing noun phrase somewhere in the sentence; linguists refer to the missing noun phrase as a “gap”, and who(m) as its “filler”. Even though the filler is usually in a different position from the gap, structurally the filler and gap are linked. Whatever case would be assigned to the gap manifests itself on the filler.
When the gap is an object, whom is appropriate. (2a) can use whom, because it’s filling a gap in the object of the verb saw.
When the gap is a subject, whom is inappropriate. (2b) can’t use whom, because the gap is the subject of the verb did.
(2c) gets tricky, because we seem to have two conflicting case assignments. Who(m)ever is the object of stalks, so you’d expect accusative case, but it also looks like the subject of is, so what do we do? In general, only the closest case assignment matters, and case doesn’t trickle down within a phrase. Since the subject of is is actually the whole phrase who(m)ever the werewolf stalks, not just who(m)ever, its case assignment doesn’t manifest. Only the assignment within the smaller phrase who(m)ever the werewolf stalks matters, and that’s accusative case from stalks. Thus whomever is appropriate here.
This is a bit subtle, and I don’t think I’ve done a great job of explaining it. (A newspaper columnist and I got into a fight about such a case assignment three years ago, and we still haven’t settled it.) This is the sort of situation where you’re probably best to just go with who; even if you have spent the time to prove to yourself that whom is correct, there’s a pretty good chance that someone else will insist that you’re hypercorrecting.
Summary: In contemporary American English, whom is necessary only in certain situations within very formal writing, so you can get by just fine without using it. If you choose to use it, remember that it is not the formal variant of who but rather the accusative-case variant of who. If who is replacing a subject of a sentence, it should never be whom. Whom is reserved for objects of verbs and objects of prepositions.
The Back-to-School Reviews so far:
I: Confusing contractions (your, you’re and the lot) [09/04/12]
II: Who and whom [09/10/12]
*: Whom seems more formal because it’s mostly used in formal writing. In informal writing, who is the form for both nominative and accusative cases.
**: Technically speaking, the apostrophe-s on possessives is a way of marking genitive case, but that’s a topic for another time.
We’re all Rolling Stones fans here, right? I mean, we’re all here on a grammar blog, so I don’t think I’m jumping to too wild a conclusion to assume that we’re almost all oldsters, whether in actual age or personality. So let’s talk about the classic “Get Off of My Cloud”:
As it turns out, the Stones weren’t terribly fond of this song; they felt it was a rushed follow-up to the runaway success of “Satisfaction”. But some grammar peevers dislike it for an unrelated reason:
“‘Off of’ is no way to talk. It IS really, really bad English.”
Hatred of off of is widespread. It pops up commonly in peeve lists. Some professional grammar commentators share this complaint: the quote above is from Patricia O’Conner of Grammarphobia*, and Grammar Girl tersely dismisses it with “You jump off the pier, not off OF the pier”.
So what’s supposedly wrong with off of? The main problem seems to be that the of is unnecessary, but another common one is that since it’s on and not on of, it must be off and not off of. I also see complaints that it’s dialectal or informal or American, that one can’t put two prepositions next to each other, or that it ought to be from. And worse, given all of these problems, the phrase is supposedly spreading.
Let’s take these in reverse order. First, I’m unconvinced that it’s spreading, unless you’re talking about a very recent (last 20 years) spread. Here’re the Google Books counts, and you’ll note that modern off of usage is still below its peak in 1910. The Corpus of Historical American English has a slightly different picture, with more-or-less stable usage from 1900 to the 1980s, and then a jolt up in the 90s and 2000s. Maybe it’s spreading, maybe not. But let’s talk about why it’s not bad either way.
I’ll start with the easiest objections. No, it shouldn’t just be from. Consider:
(1a) The numbers station is broadcasting from a shed off of Route 395.
(1b) *The numbers station is broadcasting from a shed from Route 395.
And yes, you can put two prepositions next to each other, as in this unobjectionable example:
(2) I pulled a coat out of the closet.
Going on to a somewhat more complex objection, antonymic phrases do not have to share structures or prepositions. The fact that you get on and not on of a train doesn’t mean that you have to get off and not off of it. Consider:
(3a) I put the sandwiches into the picnic basket, but someone has pulled them out of it.
(3b) One velociraptor was in front of Muldoon, the other next to him.
And now on to the involved discussions. One question is whether off is always sufficient, and off of thus always unnecessarily wordy. And the answer, I think, depends on that of a second question: whether off of is dialectal.
In my idiolect, off of is perfectly standard. I was probably in my twenties before I heard someone object to it. That’s not to say I can’t use off without of. To the contrary, I prefer (4) without of, though both forms are acceptable to me:
(4) The leaves fell off the tree.
That said, of is not always superfluous to me. A few examples where I find removing of to make the sentence noticeably worse:
(5a) It’s a way of profiting off of something you expect to drop in value.
(5b) My new invention will knock the socks off of the scientific community.
(5c) I broke your statue by knocking the top off of it.
You may not agree, even if you come from an off of idiolect, that these forms are better, but that’s not important. The key point is only that sometimes, to some people, off of is distinctly more mellifluous than off. Dismissing off of out of hand as superfluous is valid only in dialects that already don’t allow it.
Let me elaborate this “necessity depends on dialect” point by proposing an insane argument. I’ve mentioned before that, being from Pittsburgh, I am perfectly content to say The car needs washed instead of The car needs to be washed. Within my dialect, to be is often superfluous, and there are some sentences that I find greatly improved by omitting it. Thus, I could see arguing that to be is, at least sometimes, unnecessary. But if I argued this to someone speaking a “standard” dialect of English, I would sound crazy. Saying that of in off of is across-the-board unnecessary sounds equally crazy to me.**
So is off of dialectal and/or informal? The answer would seem to be yes to both. The Oxford English Dictionary calls it “only colloq. (nonstandard) and regional” in current use. The Merriam-Webster Dictionary of English Usage says it’s “primarily a form used in speech”. The Columbia Guide to Standard American English says it’s avoided at “Planned and Oratorical levels and in Semiformal and Formal writing.”
Those sources are generally pretty trustworthy with their opinions, and given the amount of people who find off of unacceptable, I’m inclined to believe that it really is dialectal. When that’s coupled with its primarily spoken usage patterns, it’s no surprise that it would feel informal, especially to people from other dialects. And using the Corpus of Contemporary American English as a measuring stick of informality, off of occurs in speech twice as often as in written fiction, about four times as often as in newspapers/magazines, and almost ten times as often as in academic writing. The more formal the style, the less likely you’ll see off of.
All that said, its informality doesn’t mean it’s an illiteracy. Off of used to be standard in English; the MWDEU starts off with a Shakespearean usage  and continues with Pepys  and Bunyan . In the last century, they show it used by Hemingway, Faulkner, and Harry Truman, among others. So if it is making a comeback, it’s no harbinger of linguistic doom, just a return to form.
Summary: There is nothing linguistically or grammatically wrong with off of. It’s nonstandard in some dialects and informal in most, so you should probably avoid it if you’re concerned about your writing seeming formal. But when formality isn’t a concern, use it as you see fit.
*: This is a surprising stance, because it comes from Patricia O’Conner of Grammarphobia, who’s normally a lot less judgmental about such things. In fact, three years later, she softened her stance, although she remains against off of. I included her original opinion because her reconsideration shows that even hard-line opinions can (and should) be altered in the face of evidence, so long as the commentator is reasonable.
**: In fact, I and others within my dialect seem to have strong intuitions about times when the to be can and can’t be felicitiously dropped, in the same way as I see off of. It’s not a matter of necessity but of felicity.