Thursday, January 10, 2013

One fewer non-rule to follow

Though I don't frequent Starbucks, I very much enjoyed S.A.P.'s post about "Starbucks names," as did most of the many commenters. (A couple of cranks took the trouble to object that the topic was too trivial for The Economist's blog. Some people just aren't happy till they let you know they're unhappy.)

But I think S.A.P. (or "Sam," to Starbucks) commits an increasingly frequent hypercorrection when he says, "My Starbucks name just gives me a way to blend into bland normalcy: it's one fewer thing different about me."

Yes, one thing is definitely a countable. But "one less" is the preferred idiom, as Google's Ngram Viewer (insert cautionary language here) shows: 



Considering the reams of usage commentary (some simple-minded, some more accurate) on the less vs. fewer distinction, there's surprisingly little mention of the one less/one fewer issue. MWDEU, which goes on for nearly five columns about less and fewer, says simply, of less: "And of course it follows one," giving as examples "one less scholarship" and "one less reporter." 

Theodore Bernstein, in "The Careful Writer" (1965), suggests a possible rationale for this fewer avoidance:
There is one oddity about fewer: Whereas it is fine to write, "The Liberals won
three fewer seats than in the previous election," you run into idiom trouble if you reduce the number to one; you cannot say "one fewer seats," nor can you say "one fewer seat." The only escape hatch is "one seat fewer."
(He goes on to point out what less/fewer purists often ignore: that even countables may, in a given context, be considered as quantities rather than numbers. "For instance: 'Not many of these buildings are fewer than thirty years old.’ The thought here is not of individual years but of a period of time; therefore, less.")

And since the commentary is so scant, I'll mention that in Johnson's 1755 Dictionary, "one" is defined as "less than two" (not "fewer than two," though he's obviously referring to whole numbers).  

I don't think I ever heard the "one less" rule during my editing years, but if others did -- or if you have further citations on it -- I'd be interested to know the where and when. Google Books doesn't turn up anything, but it's not working well lately, so that non-result can't be trusted.

Update: I forgot I had some earlier research on this, from my column in the Globe in 2009 (when Google Books was more responsive):
Earlier generations of usage critics, however, certainly used "one less," even if they subscribed to the traditional less-fewer line. Here's John Russell Bartlett, from his "Dictionary of Americanisms" (1848): "To play dummy, is to play with one person less than the requisite number." Joseph Fitzgerald, in "Word and Phrase" (1901): "Total for these three languages 57, or one less [vowel sound] than for English alone." H.L. Mencken in the American Mercury (1925): "There is one hypocrite less in London today."
[Bryan] Garner notes that in nearly one-fourth of his current examples, "writers use one fewer, an awkward and unidiomatic phrase," where one less would be better. "One can't help thinking that this is a kind of hypercorrection induced by underanalysis of the less-fewer distinction," he says. That is: it's a mistake caused by simple-minded application of a rule that isn't really so simple.

Tuesday, January 1, 2013

English books in American translation

From a book review in the NYT's Science Times section today: 
Despite his encompassing knowledge about noise, Dr. Goldsmith can seem oddly out of touch with it personally. It is not just that the American publisher put the British edition straight into type, resulting in mildly inept Britishisms. (A 1930 report found the major source of noise complaints in New York to be "lorries -- and so it is to this day.")
The only Britishism cited is that "lorries," and I can't think of any sense in which it could be called an inept Britishism, so I'm guessing the original (or intended) word was inapt. (Meaning that Manhattanites will find it jarring to hear that lorries are roaring down Second Avenue.) But so far it's still inept at the Times website, so maybe the writer and editor think that's what they meant. 

The author's implication -- that selling Americans a book in British English is a lazy shortcut -- is an interesting counterpoint to recent complaints about the opposite problem: publishers' insistence on Americanizing the language of British books (and not just Harry Potter). Both Ben Trawick-Smith ("'Americanized' Non-American Novels") and Tim Parks ("Learning to Speak American") think  American readers can easily handle, and would usually prefer, British writing in its original form, and their blog readers agree. The discussion continues, with another huge cast of commenters, at Language Log, where Mark Liberman  looks into the sources of Parks's editing woes. If you missed any of these in the pre-holiday scramble, now's the time to put up your feet and enjoy them.

Wednesday, December 19, 2012

"Apparent" and reality

Is there any such thing as an “apparent heart attack”? In a post at Visual Thesaurus, Merrill Perlman takes on that journalistic bugaboo. She cites me as a defender of the usage (siding with the Associated Press, versus Bryan Garner and any number of grizzled editors), and so I am, but she doesn't really explain the arguments for the defense. (Her own recommendation is cautious: Use it when you must, if your editor allows it.)

So I thought I'd resurrect my 2008 piece here, before it disappears behind the Globe's paywall. (The Perlman article is already behind a paywall, but buy yourself a Visual Thesaurus subscription for $19.95. You won’t regret it.) 

And while I'm being argumentative, let me dissent from another of Perlman's rulings. "If you do use an adverb, be sure to put it in the right place," she says. That is, write "she died, apparently of a heart attack," not "she apparently died of a heart attack." This is a variation on the placement-of-only fetish, and it's just as misguided. In most contexts, "she apparently died of a heart attack" would be the normal word order, just as in "he probably died of fright" or "they reportedly survived by eating worms." And there's nothing wrong with "Apparently she died of a heart attack," either. Let's not go looking for trouble.

"The Word," Boston Globe, Jan. 6, 2008
"One of my pet peeves is 'he died of an apparent heart attack,' a reader and former newspaperman wrote recently. (His name, alas, has been lost to an e-mail mishap.) "Try as I might," he said, "I have been unable to find an 'apparent heart attack' on any list of maladies that might kill someone."

His peeve is not one of the best known, but it's familiar to many journalists. The New York Times style manual cautions writers not to report "apparent" heart attacks or robberies: "Only real heart attacks and robbery attempts are dangerous," it says. Instead, write "Apparently, he died of a heart attack."

Bryan Garner offers similar advice in Garner's Modern American Usage, along with an analysis of the problem: "The adverb apparently gets morphed into an adjective and paired with the wrong word (a noun) when logically it should modify a verb," he says. "A person may die 'apparently of a heart attack' but one doesn't die 'of an apparent heart attack."'

As usage issues go, the apparent argument is fairly new. The Times used the phrase "apparent heart attack" as early as the 1920s, but the earliest objection I've found comes only in 1965, in a book by Roy Copperud, a journalism professor and usage writer. Copperud called "apparent heart attack" ambiguous, arguing that it might imply that the ailment was merely psychosomatic. By 1980, though, he was backing off: "Critics say sentences like this are ambiguous, though no one misunderstands ... the intention," he admitted.

Others remained steadfast in opposition: Morton S. Freeman (no relation!), in a 1990 usage book, banned the expression outright, because "an apparent heart attack is not fatal."

Now, I'm not especially fond of the apparent heart attack construction. But the arguments against it have holes you could drive an ambulance through.

First, some critics are cheating on the definition: When they say "apparent" heart attacks aren't fatal, they want to imply that apparent is the opposite of actual -- that it means "unreal." Not so: it means possibly unreal, says the American Heritage: "Appearing as such but not necessarily so; seeming; an apparent advantage."

Yes, the apparent heart attack might turn out to be something else -- indigestion or a stage performance, say. But apparent doesn't mean "not genuine"; it only means "not verified."

Then there's the matter of syntax. Garner claims we must say "He apparently died of a heart attack" because apparent, an adjective, would have to modify a noun; we need apparently, the adverb, because we're modifying the verb, died.

But apparently isn't, in fact, modifying the verb in that approved sentence. The deceased didn't "apparently die" (unless he's missing and only presumed dead). If he's dead, then "he died"; apparently modifies the prepositional phrase, "of a heart attack."

As for the adverb getting "morphed" into an adjective, as Garner speculates -- well, apparent is already an adjective. According to the Oxford English Dictionary, it has been used in this sense - "Appearing to the senses or mind, as distinct from (though not necessarily opposed to) what really is; seeming" -- since the mid-17th century.

So if it's not the sense, and not the syntax, what's really wrong with "apparent heart attack"? Maybe it's the company it keeps. That apparent is journalistic shorthand, often used, like reportedly and allegedly, as a hedge against the uncertainties of breaking news.

I suspect that's the real reason usage writers dislike apparent; they lump it together with "fled on foot" and "slay suspect nabbed" and other condensed cliches of the trade.

Oddly, though, the apparent stigma applies only to crimes and fatalities. The Times bans "apparent" heart attacks, but in the past year it has allowed "an apparent trade dispute," "an apparent reference to the border with Iraq," "an apparent friendly-fire episode," "an apparent gaffe," and more. All these apparents mean "seeming" or "presumed," just like the banned apparent modifying "heart attack."

So it looks as if apparent heart attack is merely another random peeve, a usage plucked out for special abuse while similar constructions get a pass. If you think it's overused jargon, of course, it's fair to argue against it. But let's be clear: the debate is not about "ambiguity" or grammar; it's just a question of taste.

Wednesday, December 12, 2012

Taking the shine off "coruscate"

John McIntyre’s current word of the week is coruscating -- literally "flashing, sparkling, glittering," and metaphorically, per American Heritage, "exhibit[ing] sparkling virtuosity."

But do we have a consensus on that? I've had coruscating on my watch list for a while, and I think it may be shifting its sense in a way that the dictionaries haven't yet recognized, though they surely have active files on the case. 

The thing is, coruscating is supposed to be complimentary, but sometimes it's obvious the writer doesn't mean it that way. Instead, it's a negative,  apparently meaning "corrosive, harrowing, scathing, excoriating, castigating," or the like. For example:
The poem ... is a coruscating portrait of her father as a dead weight on her mother's psyche. (New York Times, Nov. 8, 2012,  in a review of a book called "brutal and sorrow-filled.")
In his concession speech, Romney showed he had heard the message. He called for renewed bipartisanship, an end to coruscating political divisions. But the Republican hard men still don't get it. (Guardian, Nov. 7, 2012)  
One of the peculiarities of modern conservatism is that the most coruscating examinations of its doctrines are often issued from dissidents within its own ranks. (NYT, March 2, 2012).
Entwistle's early lack of leadership and gravitas led to coruscating attacks from media commentators. (Independent, Oct. 29, 2012)  
And though coruscate is listed as an intransitive verb, a few writers have coined an adjectival coruscated, which might mean anything, but seems unlikely to mean "sparkling" here: 
He slathered the walls with coruscated layers of paint and clay. (Observer, Oct. 28, 2012)
You close ''Don Quixote'' and ''Tristram Shandy,'' ''Middlemarch'' and ''Augie March,'' and the cosmos takes on a coruscated import it rather lacked before. (NYT, Aug. 19, 2012)
I suspect, after poking around the newspaper archives, that the change is more advanced in the English press; they like to call critical official reports "coruscating," and you know they can't mean  sparkling. So what's going on in your linguistic neighborhood? Does coruscate still shine for you, or are the lights going dim?


Update 12/13/12: I see that Ruth Walker, whose language posts at the Christian Science Monitor are (sadly) not all that easy to find, wrote about coruscate last year, and mentioned the "corrosive" connection:
This writer [on a website of the University of Hull] goes on to say, however, that people often use the word to mean "very hostile" or "savage," and suggests that the word they are reaching for but not quite finding is excoriate … Corrosive may be another word writers have in mind when they use the nonsparkly coruscating.
She also sums up why it’s so easy to spread a new sense.
When a 50-cent adjective like coruscating appears in a sentence where it's not essential to meaning, readers are freer to draw their own inferences. In this case, the two meanings are very different, but in any given context, each is likely to be plausible. Readers then use the word themselves in the meaning they have inferred.
Sure, a dictionary would help -- but we don't learn most words from dictionaries, and until someone throws a warning flag, the person using the word has no reason to doubt his inference.  As Walker concludes: "This is how language changes. Alas." (I'm not sure if this one is going on my "Alas" list or not, but that's a personal decision.)

Wednesday, November 28, 2012

The outage outrage

Nick Kristof, call your editor. The two of you committed a language gaffe -- by Times standards, at least -- in your Nov. 22 column. But I doubt that any ordinary New York Times readers saw the problem in your third paragraph:
A month ago, I would have written more snarkily about residential generators. But then we lost power for 12 days after Sandy -- and that was our third extended power outage in four years. Now I’m feeling less snarky than jealous!
I wouldn't have noticed it either, had I not learned of the issue two days earlier in the Times’s weekly After Deadline blog. Commenting on a reference to “storm damage and power outages,” Philip Corbett, the paper's standards editor, said, “The utilities prefer this euphemism, but we should call them what they are: blackouts or power failures.”

Outage is a euphemism? In decades of editing and peeve-watching, I've never seen that nit picked. But Corbett is just enforcing the Times style guide, which (in the book version, published 1999) calls outage “jargon and a euphemism for failure, shutdown or cutoff.”

I couldn’t find much support for this notion in the usage archives, but one source went into it deeply enough that I suspect it of starting the anti-outage movement. That source is the Morris Dictionary of Word and Phrase Origins, by William and Mary Morris. In the second edition, published in 1977, the authors go into the outage question in detail:
One winter our town was hit by a particularly damaging sleet storm, with the result that we were without light and heat for five days. Partly out of understandable vexation at the hardships resulting, we expressed our displeasure at the term used by the electric light company to cover the situation. It was, they said, a ‘power outage.’ We thought ‘power failure’ would be more expressive – and said so.
The authors don’t say where they expressed their displeasure -- perhaps in the first edition of their Dictionary, 10 years earlier -- but in response, they say, “a knowledgeable reader wrote,” and they print his comment:
An outage is not a synonym for “power failure.” In the electrical generating industry, the term covers any situation in which equipment is not functioning; it means simply “The equipment is out.” It might be out for maintenance, improvement or replacement, as well as for breakdowns in service due to malfunction, accidents or acts of nature …
Knowledgeable Reader has a very plausible analysis of the situation:
I’m of the opinion that this bit of industrial jargon has moved from power plant usage to application throughout the industry and only recently into the vocabulary of the information media. Of course, the mass media’s uses would be during times when the public was inconvenienced and doubtless irritated by unplanned, accidental outages. Perhaps that more restrictive application has resulted in the unfavorable connotation and impression, as you seem to have implied, that outage is a euphemism.
KR points out that this use of outage was newish in general usage and associated with a special lexicon, both traits that can arouse word rage. Indeed, in 1977, not long after the Morrises encountered their outage, the Times heard from a reader not enchanted with the novel usage:
Re: “Outage” -- a new word.  In the “age” of lawlessness there should be no shortage of courage in dealing with an “outage” spawning “lootage” by “loutage.” The system demands “stoppage” or there may be no system to salvage. 
And the Morrises, as I read them, accept the Knowlegeable Reader's point of view. They don't press their case against outage; they give KR the last word. And they don't mention outage at all in the second edition of their Harper Dictionary of Contemporary Usage (1985).

But it's harder to kill a peeve than to invent it. Some editor apparently took the Morrises' initial rant to heart, and kept the animus alive long enough to infect a contributor to the Times style manual -- and now it's online, trolling for new fans. Here's hoping it fails; this misbegotten peeve has earned its current obscurity.

Saturday, November 17, 2012

Keeping the "suck" in "successful"

I’ve heard accessories called “assessories,” and succinct pronounced “sussinct” (not so often, but then it’s not so common a word), and flaccid started down the road to flassidity so long ago that the wrong pronunciation is now right. (That is, all our dictionaries list it, some as the majority usage.) Still, most English words with this Latin-derived double-c -- originally pronounced kk, as John Wells explains at his phonetics blog – continue to sound the cc as ks: accident, success, vaccinate.

But just as there’s no apparent reason for succinct to change its sound, there’s no way to know when another new pronunciation may appear. A couple of weeks ago, I had my first encounter with the nouveau successful, pronounced “sussessful.” The speaker was a caller to “On Point,” WBUR-FM’s talk show, who hailed from White House, Tenn., and who predicted an electoral victory for Mitt Romney. Why? “He’s a sussessful governor and a sussessful businessman as well.”

Yes, he had a Southern accent, but my Southern-speaking friend doesn’t recognize this as a regional thing, and of course it could be idiosyncratic. Anyone else out there hearing – or saying – “sussessful”?


Friday, November 9, 2012

Fighting off the 'were'-wolves

It's a good day, with the sun shining again and, over at Lingua Franca, a post by Geoff Pullum addressing Philip Corbett’s unnecessary anxiety about the was vs. were choice in the New York Times's columns.

As Pullum notes, many of us waffle on the choice of was or were in the subjunctive, or irrealis, construction. Merriam-Webster's Dictionary of English Usage quotes Swift, Byron, Thackeray, Frost, and other worthies opting for was where a purist would use were. (Byron: "I wish H. was not so fat.") 

Like these august writers, and like many educated users of English, I go back and forth in actual usage. I learned early on that it was OK to be blasé about was vs. were, thanks to Bergen and Cornelia Evans’s Dictionary of Contemporary American Usage (1957). Back in the mid-20th century, a lot of language authorities thought the subjunctive were was dying, and the Evanses were among them: "Was has been used as a past subjunctive in literary English for more than three hundred years and is the preferred form today." 

It's unlikely the Evanses had statistical proof for that "preferred form" judgment, and I doubt that it's even true. But given the number of subjunctive wases they saw in educated writing, they were confident in saying there were only two constructions in which were was clearly preferred: "If I were you," more or less a fixed phrase, and the literary "were I in a desert." 

We haven't abandoned subjunctive were as quickly as the midcentury mavens predicted. But if it disappeared overnight, as Pullum points out, there would be no loss of clarity; for other English verbs, the irrealis form is already the same as the simple past, or preterite: "If he had the money, he'd buy a generator." Is there any example in print of a failure to use the irrealis were causing genuine ambiguity? I don't think I've ever seen even a made-up example.*

By contrast, the recent blending of may and might – saying “if he had a raft, he may have survived” when you know that he didn’t survive -- can cause actual misunderstanding. (Way back in 2002 and 2003, Language Hat was bemoaning the development: "One of the changes going on in English that distresses me the most ... is the obsolescence of the contrary-to-fact past 'might have.'") Yet the takeover by may continues, and few notice the ambiguity. 

Why, then, should the meaningless was/were distinction persist, where no ambiguity ensues? I guess it's just one of those quirks of peevology.

*The myth of the "misplaced" only, on the other hand, has inspired dozens of made-up examples of alleged ambiguity, of the "I ate only the almonds/I ate the only almonds" genre. Yet I''m still waiting for a reader to show me an edited, printed example of an ambiguously placed only.