The Pragmatic Grammarian

If you have any familiarity with grammarians, you probably know there are supposedly two types: prescriptive and descriptive. The former is obsessed with knowing all the rules and exceptions, and with forcing all writing and speech into compliance with those rules and exceptions. The latter is also obsessed, but not with rules. Rather, the descriptivist focuses on usage in the living language, which is always in flux. Rules? Bah. How people use the language is more important than whether they follow the rules. Reductionist thinking, you cry. Yes, for my purposes that is exactly how I’m describing the two types. Keep reading, okay?

Therefore, I posit a third type: the pragmatist. You may ask, What does that mean? And well you should. It acknowledges that most grammarians, whether they care to admit it or not, blend prescriptivist with descriptivist and make the writing or speech fit the purpose, the audience, and the subject matter as required. I know the rules. I am quite fond of most of them, actually. I also know how “real people” use the language. I am often less fond of this, but as I am also one of these “real people” I try to cut some slack, as the saying goes. If someone’s speaking casually to a friend, I won’t leap in to correct their subject-verb agreement or their use of a reflexive pronoun instead of a simple objective one. It’s just not that important under those circumstances. It’s really not. However, if I’m asked to copyedit someone’s work, you can bet your boots I’ll take at least these three things into account: the type of work, the subject matter, and the intended audience. Once I’ve determined those things, and the extent to which I need to mold the work into a particular shape, I’m off to the races.

This poses a problem for new writers who ask grammatical questions in an open forum where I am far from the only professional editor. At times I simply don’t answer. My views are sufficiently fluid that I can easily cause more problems than I solve with my “well, it depends” answers. If I can tell that the questioner is more likely to be confused than helped by my answer, I withhold the information. I wait, instead, to see how the others respond; I watch the interactions, watch the wording and the behind-the-scenes body language (c’mon, you can tell when someone’s hunched over the keys stabbing at them with pudgy—or bony—fingers while blood drips from their brow), and take my time deciding whether I need to interject my opinion. Often the answer is no. When the answer is yes, I take even more time and care crafting the response. I’m not out to denigrate any of my fellow professionals, nor am I out to make a new writer feel stupid for asking a grammar or usage question. (They’re pretty good at doing that to themselves, from what I can tell, without help from anyone.)

Things become muddier still when the question is about US vs. UK conventions. I have a very basic working knowledge of UK grammar, spelling, and mechanics. That doesn’t make me an expert on it, but it does provide a basis from which I feel mostly safe answering simple questions (which tend to be about terminal punctuation with quotation marks). Even so, my simple answers—which I self-edit to remove words and concepts that tend to answer unasked, tangential questions—usually invite others to chime in with “But she forgot this” and “Of course, there’s also this over here” and the occasional “Yeah, what she said.” From my pragmatic grammarian view: If you’re writing for the US market, use US grammar/spelling/usage/mechanics/style. If you’re writing for the UK market, do what’s expected from the UK. Don’t fuss over which one’s better, or more correct, or easier, or looks prettier to you, or whatever. Just don’t. Write using the rules for the market you’ve chosen. And if you don’t know those rules, guess what? I’ll tell you not to write for that market. That whole debate (US vs UK style and whatnot) grates on my editorial senses, frankly. There’s nothing to debate from where I sit. Use the rules for the country where you grew up, or use the rules for the country’s market you’ve chosen (after you’ve learned them or teamed up with someone who can guide you through them), but don’t trouble your pretty or handsome head over which set is superior. The answer is both and neither. They are what they are, for the reasons they are, and that’s really all you need to know. It’s what I will tell you if you hire me to work on your project. And I will ensure that your work conforms to US rules to whatever degree is expected.

I don’t think I’m breaking any new ground with this pragmatic grammarian stance, except perhaps by naming it. I know prescriptivists who sometimes relax the rules, and descriptivists who break out in hives when someone says “Anyone can do whatever they want.” All I’m saying, folks, is let’s be honest about the situation. Let’s admit that neither approach can stand entirely on its own. People aren’t going to speak to their friends and family in the formal language of a doctoral dissertation. They’re not going to write their dissertations with contractions and dialectical figures of speech (unless the dissertation’s on linguistics, focusing on dialects, and they’re providing examples).

Let’s be pragmatic, shall we?

Not the best way to treat your customers

Lately I’ve been posting pictures of signs that feature typos. Here’s one that suffers from a different kind of problem. It meant to say one thing but ended up saying another.

So if parking is limited to 90 minutes for Whole Foods Market customers only, does that mean people who are shopping in a different store can park in the lot for as long as they want? Can the guy who lives down the block leave his car in the lot all the time? I guess Whole Foods Market customers are the only ones getting the shaft here. Doesn’t seem like the best way to treat the people spending money in your store!

They could have avoided the problem by adding a few more words to the sign. Something like: “. . . parking is limited to 90 minutes and is for Whole Foods Market customers only.” It’s usually worth giving a little extra attention to ensure that your message is being conveyed accurately, especially when it’s displayed in public.

(The above photo was kindly donated to the blog by Josh Weinberg. Thanks, Josh!)

There’s no “I” in “they,” either

Yesterday, Karen posted about how she’s fine with the use of the singular “they,” as in, “Everyone can decide for themselves.” My initial response to her was, “Of course you know this means war.” (Yes, that phrase comes from where you think it comes from.)

But then today I saw this article about how the Queen’s English Society closed up shop recently. For 40 years, the QES had pushed for the continued use of proper English despite what the group perceived as declining standards. It took the prescriptive approach to grammar—trying to enforce the rules as they should exist, rather than adapting the rules to reflect what was actually happening to the language.

So I started to wonder: when (for example) I continue to insist that “they” is not singular, and I go out of my way to recast phrases such as “Everyone can decide for themselves” to “People can decide for themselves,” does that make me part of the language police? When is it worth fighting, and when is it better to go with the flow?

I don’t have an answer yet. I just wanted to ask the question and see what people thought.

Also, while looking into the QES, I couldn’t help but notice that the group’s website says nothing about disbanding. In fact, they’ve announced that their next annual meeting will take place in September. So perhaps the QES is not dead yet!

That would be a good thing; if nothing else, their website has a section called “On the Lighter Side” that has some decent language entertainment. For example, check out the Oxford Word Challenge, in which you have to identify a pair of homophones from clues. And then read “A Lesson Learned (the Hard Way),” which dramatizes the terrible things that can happen when you end a sentence with a preposition.

Everyone can decide for themselves.

No, really. Everyone can make their own decisions about the singular “they.” (I happen to know that Ray and I are on opposite sides of this particular issue. I’m posting about it only because someone I’ve known longer than I’ve known Ray posted about it over on my Facebook wall about a half-hour ago, and in the process of responding to her, I relocated the two wonderful blog entries that helped me face my fear of “singular they” and move past it.)

You may or may not realize that being up in arms over “singular they” while remaining placid about “singular you” could be called hypocritical by some. (Not by me, but by some who are even more rabidly grammar-nerdly than I. There are such people. Oh, yes, there are.) I point this out as a matter of concern for my readers’ relative safety while roaming the Internet.

Once upon a time, long long ago (but not in a galaxy far far away), “ye” (now “you”) was the plural second-person pronoun, and “thou” (now mostly extinct except in historical and fantasy writing) was the second-person singular. Over time, the latter fell into disuse and the former became the acceptable catch-all second-person singular and plural pronoun. And that, my readers, is how we wound up needing phrases like “all of you” and dialectical constructs like “you’uns” and “all y’all” (because “y’all” is singular, you know?). Pitching a fit over a singular they, but accepting singular you without question, causes some people to react very badly indeed. Of course we’re still in the very midst of the shift for the singular they, while most of us were raised with the singular you (unless we lived in Yorkshire in the 1940′s, for example, when “tha” was the dialectical form of “thou” used in everyday speech).

And so, here are the links I mentioned at the start of this ramble. I hope that if nothing else you will find them entertaining. (I can also hope that some of you might decide that the singular they makes sense, just like the singular you does.)

http://chronicle.com/blogs/linguafranca/2011/12/16/pronoun-agreement-out-the-window/

http://chronicle.com/blogs/linguafranca/2012/01/05/dogma-and-evidence/

I want to address one more point, because I can hear the thought rumbling around out there in the ether. While I have come to accept the usefulness of singular they when the gender of the antecedent cannot be known and I want to avoid the wordiness of “his or hers” or “himself or herself” or what-have-you, when I am copy editing this is an issue I discuss with the author. If said author is apoplectic at the concept of the singular they, I will do my best to recast sentences to not need gender specificity. If said author is receptive to the concept, happiness ensues. It’s all part of my job, ensuring that the author’s voice is clear even after I’ve fixed all the problems. This isn’t really a problem. It’s a choice–one that everyone can make for themselves.

 

The Hatter, the Hare, and the Dormouse had it right, you know.

Mad Hatter: You might as well say that “I see what I eat” is the same as “I eat what I see!”
March Hare: You might just as well say that “I like what I get” is the same thing as “I get what I like!”
Dormouse: You might just as well say that “I breathe when I sleep” is the same thing as “I sleep when I breathe!”

They’re not the same thing at all, really, even though poor Alice tried to say that “I mean what I say” is the same as “I say what I mean.”

How did I arrive at this literary source material? By way of a friend who shared this image with me, which I now share with all of you.

No word on whether AT&T responded to this with a corrected Tweet or not. I could hope, but I won’t.

I’m reminded of a handout I created during my tenure at TSR, Inc. about how word order changes meaning. The word “only” isn’t much of a word, really, having a mere four letters and two syllables–but watch how the sentence meaning changes with the position of this lowly modifier (it can be an adjective or an adverb or even a conjunction depending on placement).

Only the bear ate the hunter. (There were other animals, but the bear’s the only one that ate the hunter.)

The only bear ate the hunter. (No other bears were around, and the other animals are innocent.)

The bear only ate the hunter. (The bear didn’t kill the hunter, but he did eat him.)

The bear ate only the hunter. (The bear ignored the wife and kids, but ate the hunter.)

The bear ate the only hunter. (There weren’t any other hunters.)

Perhaps I should send this to AT&T’s social media peeps. Then again–naah. I need the blog fodder, y’know.

 

 

Baby puppies and High Velocity Angry Canaries

Many years ago, when I worked for Scott, Foresman and Company (yes, the Dick and Jane people), editorial seminars were de rigueur. At one such gathering, we received handouts containing examples of “baby puppies.” Regrettably, I no longer have the handout, and none of the other examples stuck with me like that one did. However, I can still discuss the concept–and how my view has changed over time.

We were told in no uncertain terms to avoid redundancies such as “baby puppies.” And, dutifully, we excised them from our texts. Luckily for those of us in the nascent Electronic Publishing Division (now extinct), our work seldom included such things. We dealt with user manuals for educational computer games and school management software. That gave us whole other grammatical and usage-related jungles to hack through with our CMoS-issued machetes, but very few “baby puppies.” I felt cheated, sometimes.

Now, I have a different perspective. Yes, a puppy is a young dog. But not all puppies are babies, are they? Some are nearly a year old, and certainly no longer deserving of the “baby” descriptor. Those little cuties who aren’t yet weaned, though–they’re baby puppies, for sure. The same logic applies to baby kittens. Baby kittens are itty-bitty furballs with tiny, high-pitched mews. And hypodermic-needle-sharp claws and milk teeth.

When I was forced to take a creative writing section in high-school English, I used the phrase “bone-dry dust.” In large (not-so-friendly) red letters in the margin, the instructor wrote “What other kind is there?” So much for my creative writing. That pretty much killed what little interest I’d had to start with, to be honest. Even at that age I was much happier fixing poor grammar and mechanics than trying to be creative. At least I didn’t have to go through that again.

We still find examples from the Department of Redundancy Department, often in the chromakeyed lower-third crawls on local news programming. “Fatally killed” is a common one. “Fatally shot,” fine. “Fatally stabbed,” sure. “Fatally killed” just makes someone who (thankfully) remains faceless and nameless look foolish (while being faceless, which is a pretty cool feat all by itself, isn’t it?).

Another issue pointed out on the handout for that particular seminar was assuming that your editor/proofreader knows what you’re talking about. The example was from a brochure for a heating and air-conditioning business. The copy used the acronym “HVAC,” and the senior editor had noted “write out” in the margin. A junior editor got the project next, and took a shot at the meaning without looking it up (this predated the Internet, you see–it would’ve meant physically moving around in search of a reference book or someone else who knew the information). That’s how the phrase “High Velocity Angry Canaries” found its way into one version of the brochure in question. No word on whether it actually saw print. One would hope it did not. (For anyone who doesn’t know, HVAC stands for “heating, ventilation, and air-conditioning.”)

If by chance you’ve written a technically-oriented piece, please do your editor a solid (ooh, I’m trendy!) and provide a file of the specialized vocabulary you used. That will save everyone involved time and frustration, and potentially could save you (the writer) money as well–because your editor won’t have to dither around looking up information you’d have been better off providing yourself. This is also true for fantasy/science-fiction writers, truth to tell. If you’ve made up a number of alien races, providing a file containing the names of each (spelled, capitalized, punctuated the way you want them) will save your editor hours of headaches wondering whether the right form is “Graz’zyt” or “Grazz’yt.” (And honestly? Apostrophes have been done to death. Please consider not using them in proper nouns. Thank you.) Also please include proper names of any members of those races, with correct mechanics and spelling. Extrapolate as you will from what I’ve said here and decide what else you need to apply this to. I have confidence in you. I really do.

And editors? Don’t be afraid to ask your writer about providing such a file. They might grouse and grumble at first, but once you’re deep into the project and you don’t have to harass them daily with questions such as how they really want to spell “Graz’zyt,” they’ll thank you. (And if they don’t, shame on them.)

Until next time, then, I hope you all have as much baby puppy face time as you wish. (Or baby kitten face time, if that’s your thing. Or baby something else. Maybe you don’t even like babies, in which case–okay. I need to go now.)

 

I’m not making this up. Honest.

I’ve been ranting a lot here and elsewhere about the sorry state of ebooks from indie authors, relating to the (apparent) lack of editorial skills (paid or otherwise) applied to those ebooks. I decided to provide concrete examples from the book I’m currently trying to read. I say trying, because I want to read it, I want to enjoy it, but the appalling number of errors is really harshing on my serenity, dude.

I won’t name names or titles, or say where I got the book. I will say I’m glad I didn’t pay for it, though. If I’d parted with any money for this I’d be pretty upset. More upset than I already am. At least having paid nothing for it, I can’t bemoan the loss of money I could have spent on, I don’t know, food or gas or something useful. All I’m losing is time.

These, then, are actual errors from an actual book. I’m not making this up. Honest.

I will note that I’m only 25% of the way through the book, according to my Kindle. I took a tip from another editor and started highlighting errors as I came across them. What an eye-opener that was! I mean, I knew there were errors; I can’t not see them. Proofreading is hardwired into my brain. However, highlighting them makes them seem that much worse. Now I really can’t not see them.

Some of them I’ll explain, some I’ll let speak for themselves. By all means comment if you don’t understand why I’ve called something an error. I’ll do my best to enlighten. I will also state that I’m not quoting full sentences, but only the portions containing the error. It’s also important to know that the writer is from the UK, so some of the mechanics just drive me batty on principle and some of the word choices are unfamiliar to me.

#############

no sights, no sound (For parallelism, I’d change that to “sounds” in this description of a setting.)

standing next to it, was M (Delete that unnecessary comma.)

lit up the lens of his glasses (Unless he’s wearing a monocle, he has lenses, plural.)

gunge (As an American English speaker, I didn’t know this word. It’s a UK term that I figured out contextually and then checked against a dictionary online. If I had been editing I might’ve queried it even after finding the definition. Therefore, this isn’t so much an error as a language issue–but I’m still pointing it out as something that can stop readers in their tracks.)

” . . . we can-.” (Oh, dear me. No. Not even in British usage. If the sentence/thought isn’t finished, there’s no period, no full stop, whatever you wish to call that dot at the end. Also, rather than a hyphen, I’d have used an em-dash to indicate the sudden breaking of the thought/speech. This particular mechanical error occurs throughout the book. I cheated and looked ahead, so I know.)

“Just one . . . at a time”. (Again, no. The period’s at the end of the spoken sentence, so it goes inside the closed quotation mark. I’ve read quite a few blogs lately about US vs. UK mechanics, and quotation marks with other punctuation is one of the most confusing things on both sides of the pond. However–no. It’s a sentence; it has a definite end; put the period inside the quote.)

alright (It’s not all right to use this. It’s all wrong. Two words. Always. All right? Thanks.)

small with a blue studs on top (It’s either a single stud, or perhaps this is a possessive missing its apostrophe and its object. I think it’s the first, and I’d delete that “s” on the end of “stud.”)

industrial sized Hoover (Adjectives made from two words–called compound adjectives–are often hyphenated. “Industrial-sized.” To a point this comes down to the editor’s preference in conjunction with a style guide, such as the CMoS. I far prefer the unambiguous hyphenation to an open version that in some cases leads to confusion or misunderstanding. That, and I like the look of the hyphenated form. So there. I suspect that in this case one might argue that “industrial-sized” is a temporary compound. I’ve not looked for the term in any dictionaries, so I can’t say. The concept is familiar to anyone who shops at places like Sam’s Club or Costco, though.)

give a once over (The idiom is hyphenated. “Once-over.”)

cotton weaved interior (I’m not entirely clear on the intent, here. I think the writer means the interior of this particular wig is woven from cotton. I’d have suggested changing it to “woven cotton interior.” On further discussion with the writer, I might have ended up with something more like “woven cotton cap,” since I believe that’s what the base of a wig is called–the part that fits the head like a cap, that is. I’m indulging in conjecture, of course.)

cheers and laughter . . . was a cacophony (I’d recast this, because while it seems a quick fix to say “were” and have the plural form for the plural subject, we’re also in that messy area of reciprocity. The sentence can’t be easily reversed using the same words (“cacophony” as the subject requires “was,” but “cheers and laughter” as the subject require “were”). I’d suggest recasting the sentence entirely to avoid the issue, and perhaps use the verb “created” instead of the form of “to be,” which is the heart of the problem.)

To the greying ice cream man, he couldn’t help but think . . (The greying fellow is the “he” following the comma. The sentence needs to be recast to eliminate the clumsiness. Perhaps “To the greying ice cream man the crowd looked like nothing so much as a cross between . . . .” Trust me, that’s where the sentence was going. I didn’t want to type the whole thing as it appears in the book, though.)

white-clothed (Again, this needs a hyphen.)

The driver slammed the breaks (No he didn’t. He slammed the brakes. A live proofreader would’ve caught this one.)

her inner thighs ran red raw from . . . (It took me a while to realize what’s needed here, I think because I was getting numb from the number of errors assaulting my editorial senses. Inserting a comma after “red” helps quite a bit, but I still would query the “running red” part. I know the condition the author’s describing, and I wouldn’t use the term “running” with it. “Were chafed and red,” perhaps. The way it’s written sounds like a hemorrhage.)

marine life getup (Another case here of needing a hyphen to create an adjectival compound. “Marine-life.”)

baggy (Pants are baggy. The plastic bag is a “baggie.”)

un-amused (Here’s one of the hyphens that was missing from the compound adjectives. It doesn’t belong in this word; “unamused” is a closed form.)

pre-occupied (Here’s another one. Delete it and close the space. “Preoccupied.”)

buy one get one free offer (Now we’re back to needing hyphens. “Buy-one-get-one-free offer.”)

collapse on to the floor (Usage problem. One could say “collapse on the floor” or “collapse to the floor,” but “collapse on to” is just poor usage.)

oxidisation (Aside from the UK s-for-z spelling issue, this just isn’t a word. The one the writer wanted was “oxidation.”)

pressed him for a minutae more (Just–no. No. One cannot have “a minutae.” “Pressed him for more minutae” preserves the author’s word choice and is grammatically correct. I had originally written another suggestion with a different word entirely, but I like this one much better.)

spaghetti bolognaise (If you’re going to write about a food, know how to spell it. Particularly when the food is regional Italian, like “spaghetti Bolognese.” Capitalize the “B” because this is a proper adjective.)

############

That’s where I stopped taking notes for the time being. You’ll notice I’m not fussing about pacing, or characterization, or plot, or any of those bigger things. I’m not a story/fiction/developmental editor. I’m a copy editor and a proofreader. I see these little things that many people seem to consider “nitpicking.” They’re far from nitpicking, though. They’re signs of someone with an imperfect grasp of grammar and mechanics who would have done well to have hired someone like me–or any other professional copy editor/proofreader–to look over the work before publication. Then, readers like me wouldn’t find themselves becoming irritated and unable to enjoy the story because of the plethora of errors in the “nitpicky stuff.”

I’ll also say: I learned a new phrase from this book. “Keep schtum” means “keep quiet, particularly if you’ll get in more trouble otherwise.” While it sounds Yiddish, it apparently came from the criminal culture of the UK. It might come in handy someday, so I’ll tuck it away for later.

I would hope that this has shed some light on how a typical copy editor’s brain works while they’re reading. (I think I’m typical, anyway. I’m damned good at what I do, but I don’t think I’m all that special when compared to other professional copy editors.) That’s why I did it. Not to point at a writer and chastise his work. Not to complain for no reason. To point out the kinds of errors commonly made, to explain how I would correct them and why, and to provide an example of why writers really should drop some cash on professional editing and proofreading for their hard work. That’s all, really.

Thanks for reading.

 

 

Living Language Peeve: Slang at the CSM

I know some of my readers who are also real-life friends or acquaintances are aware of my “living language peeves.” Those are the things that we could eliminate, if we could only keep the language from evolving. Granted, some of those evolutionary steps aren’t necessarily bad things. Sometimes, for instance, we need a word for a thing that was just created or invented. That’s a Good Thing. However, my peeve for today falls into the Bad Thing category no matter how I slice it.

“Humongous” in a Headline? Really, CSM?

Now, lest someone out there think I’m a total stick-in-the-mud, I use that word plenty in everyday speech. I don’t shy away from slang. In daily speech, with my family and friends, there’s no reason to be stodgy. However, I draw the line at using slang in professional situations like when I’m teaching, or making a presentation to a group. I apply the same standards to writing. I don’t expect to see “humongous” in a headline at a news outlet with the reputation of the Christian Science Monitor. I just don’t. The Onion, sure. A college paper with a carefree bent, sure. The NYT? The CSM? The WaPo? No, I’m sorry–I expect their writers and editors to use standard English.

And that’s the way it is, Tuesday, July 17, 2012. Good night, David.

 

ETA: Later tonight, this version appeared on the RSS feed. Both links remain active at this posting. More info in my comment timestamped 7:02pm.

The King’s “impoverish(ed) English”?

Lest we think that we’re alone in our clearly declining standards in English usage, spelling, and grammar, I offer this article from the BBC News, dated 28 June 2012.

I’ll let the article speak for itself, but I will say this: Is anyone else bothered by the fact that every paragraph is a single sentence?

Okay, so I won’t let the article speak entirely for itself. I have to wonder, as an English teacher myself, at the claim that “(t)here’s very little evidence of a benefit to teaching grammar (through grammar drills and exercises).” Speaking purely for myself, that’s exactly how I learned. And I learned it well. Well enough that when I had to take an editing test for a position at a company, I not only found all the errors–I also found four more that the key didn’t include. (I believe the key was updated to reflect those, after I was hired.)

Mmm–tasty child labor!

Our first entry in the “Prepositional weirdness” category (also known as “It’s only a preposition; how important can it be?”) comes from Salon.com. Thanks go out again to Scott Douglas for sending this.

Tasty child labor!

How important can a preposition be? Well–it can make the difference between a headline no one would look askance at for grammatical reasons, like “Chocolate produced by child labor, says new report,” and one like Salon’s, which stopped our contributor and at least me for a long moment. “Chocolate produced from child labor”? I suppose if I were to think about it long enough I might be able to come up with a reason for using “from” instead of “by” that didn’t have anything to do with a) sheer laziness or b) poor usage, period.

I don’t feel like thinking that long, though.