| |
March 1, 2010
By Wendalyn Nichols

Subject: Misnomers and misconceptions
I watched the Olympics as much as work would allow, and enjoyed the shots of the Vancouver area. I grew up in the Pacific Northwest, and when I see views of the region, I want to hop on a plane and head straight for the rocky beaches to spend a weekend poking through tide pools and breathing in that briny, fir-scented air.
I get a dose of home by going with my daughter to the American Museum of Natural History and walking through the hall that houses examples of the art and artifacts of the Pacific Coast Indians. There, totem poles stand at the support pillars; removed as they are from their context, they’re still awe-inspiring, in the true sense of awe that mixes wonder with fear.
Totem poles were the subject of one of those “local color” features that the television programmers use to fill the gaps between Olympic events. I was only half listening to the reporter, finding nothing new in what he was saying, until he said, “People often think that the image at the top of the pole is the most important, but that’s a misnomer.”
Well, no, it isn’t. It’s a misconception, not a misnomer.
The -nomer part of misnomer comes from the Latin word for name. A misnomer is an incorrect use of a name. For instance, when I mention to people that my family lived in Fort Bliss for a short time, I often add that Fort Bliss is a misnomer, because there was nothing blissful to me about the place when I lived there. Calling what is now the Government Accountability Office the General Accounting Office is a misnomer. When scientists reclassified the animal now known as an apatosaur, brontosaur(us) became a misnomer.
I’ve heard misnomer misused with more frequency in the last few years; it seems to have joined is comprised of, parameters, and sundry other “big” words and expressions that are trotted out by people who have heard them used by other people who are also trying to sound smart, without actually looking up the words to be sure they’re using them correctly.
And speaking of awe: A phenomenon related to this disregard for looking things up is the apparent attitude that one homophone is as good as another. Exhibit A is a comment that was posted this past week to the Facebook page of one of my cousins, who has just become a grandfather at the advanced age of 40. He had uploaded the usual new-baby pictures, and one of his friends wrote, “Awe…She’s beautiful!”
(And no, she was not making a deliberate play on awe/aw.) 
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: English usage Posted in Copyediting Tip of the Week | 1 Comment »
February 24, 2010
By Wendalyn Nichols

Subject: Thumbs down for small caps
In the last Tip of the Week post (Anachronistic acronym style), I put the question to readers of whether the practice of setting acronyms in small caps to show they should be pronounced as names should be done away with. I gave two reasons for considering this step: (1) the argument that long acronyms look terrible set in full caps is undermined by the fact that some initialisms, which are set in full caps, are longer than some acronyms; and (2) readers are more likely to perceive the small caps as a mistake because they don’t know the reason for setting them that way in the first place.
Twelve people responded (ten by e-mail); as of this writing. Of them, eight are quite ready to jettison the use of small caps, and no one outright defended the practice. Of the four who weren’t entirely happy with getting rid of the small-caps convention, two said they didn’t see how the practice could continue, but regretted that things had come to this pass; one suggested “an initial cap and then lowercase letters for abbreviations (of any length) that should be pronounced as a word, and all caps for initialisms”; and the last thought the practice might be continued in scholarly works.
Using the up/down style for all acronyms is an appealing idea, though I think this works best with familiar acronyms (set ACES as Aces and you could cause some confusion among readers who are not copyeditors). And it doesn’t solve the problem of the ugliness of lengthy initialisms, which have been and continue to be set in full caps. Getting rid of small caps altogether does remove the possibility of a reader’s interpretation of the small caps as a mistake, but then we’d have even more screaming capital letters to contend with in texts. Observing the typographic distinction in scholarly works alone would mean that all other texts would still be peppered with full-capped abbreviations.
More publications than not have done away with small caps, of course, and perhaps it’s true that our tolerance for full-capped abbreviations is higher now, as one of the responders asserted. What I find incongruous is the combination of full and small caps jumping up and down in an article that uses both kinds of abbreviations — a point that Linda Lowenthal also made in a comment. Since we’re unlikely to persuade publications to institute a policy of setting all acronyms and initialisms in small caps, the most straightforward treatment would seem to be to set all abbreviations in all caps.
One respondent said, “Who else [but editors] thinks of these things?” Indeed. Because Copyediting is a publication for editors, and we still observe fiddly conventions like the four-dot ellipsis and spelling website as Web site, I’ll probably keep using small caps for acronyms for now. At least until the next time I notice that I’ve missed an acronym or two in a just-released issue, and throw up my hands. 
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Acronyms, Editorial style Posted in Copyediting Tip of the Week | 1 Comment »
February 19, 2010
By Wendalyn Nichols
STUPID RULES 13: Don’t use “then” as a conjunction
The thirteenth in a series of podcasts about rules that Copyediting editor Wendalyn Nichols says are misguided, if not actually stupid. (3 min.)
Click here for more FREE podcasts on the topic of copyediting.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: conjunctions, Stupid rules Posted in Podcasts | No Comments »
February 18, 2010
By Wendalyn Nichols

Subject: Anachronistic acronym style
In the most recent issue of Copyediting newsletter, I wrote an article that mentioned ACES, the American Copy Editors Society, several times. As I was checking the pages, I wondered whether it was finally time to jettison a style practice that was in place when I became the editor: setting acronyms in small caps.
The style of Copyediting is fairly formal, and setting an acronym in small caps is part of that. Doing so signals to the reader — to a knowing reader, anyway — that the abbreviation is an acronym rather than an initialism. It tells us we should pronounce the abbreviation as a word, like “aces,” not as a series of individual letters.
Using some kind of typographic marker for an acronym might be useful if enough people knew what it meant. But as fewer and fewer publications observe the convention, fewer readers know what it signals, and thus the small caps look more and more like a mistake. Newspapers don’t set acronyms differently, of course — they barely use italics. And I’ve seen some books and magazines use a point size somewhere between small caps and full caps, which makes me wonder why they even bother making a distinction. Surely that would look even more like a mistake?
Some newspapers have a rule that acronyms of five letters or more should be spelled as a name, as in Unesco and Unicef. The reason for this, I’ve been told, is that the acronyms stand out too much in a column when they’re long and in all caps. But what then about the UNHCR, which is not pronounced as a name and is therefore an initialism, or the AFL-CIO, or the ASPCA? These abbreviations are long, too, but the style convention says not to set them differently because they’re not acronyms.
I’ll put the question to you: What would the value be of continuing to set acronyms in small caps, when few readers know what the convention means and it makes acronyms look so odd on a page (especially in articles that are peppered with both acronyms and initialisms)?
[Like all the Copyediting Tips, this one was sent out as an e-mail blast. Some people have already responded, and their comments are posted below. If you're one of the people who commented and would like your name associated with the comment, just let me know.]
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Acronyms, Editorial style, Initialisms, Typeface Posted in Copyediting Tip of the Week | 13 Comments »
February 4, 2010
By Wendalyn Nichols
I received the following notice from The Chicago Manual of Style Online team on Wednesday, February 3:
One of our top subscriber requests since we launched The Chicago Manual of Style Online is that we offer our community a way to discuss issues that matter to writers, editors, and publishers. Today we are pleased to announce the release of The Chicago Manual of Style Online Forum.
Available only to subscribers of The Chicago Manual of Style Online, the Forum is a place to go when you want the opinions of your fellow writers, editors, and publishers. To celebrate the launch of the Forum, we are giving away $100 worth of University of Chicago Press books to one lucky subscriber. Simply post in the Forum within 30 days to enter to win your choice of free Chicago writing and editing books. The winner will be chosen at random and announced on March 1.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Chicago Manual of Style Online Posted in Copyediting -- Because Language Matters | No Comments »
February 2, 2010
By Wendalyn Nichols
FIDDLY RULES 12: “The comma splice”
The twelfth in a series of podcasts about fiddly rules that Copyediting editor Wendalyn Nichols says are nevertheless ones that careful writers follow. In this episode, fiddly rule number 12: Avoid the comma splice. (3 min.)
Click here for more FREE podcasts on the topic of copyediting.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: commas, Fiddly Rules Posted in Podcasts | No Comments »
February 1, 2010
By Wendalyn Nichols

Subject: Back off, tailgaters
Here’s a pop quiz for you: Can you spot what is wrong with the punctuation of the following sentences?
What’s your name, do you have a nickname we can call you?
Please disregard the previous e-mail, the situation has been resolved.
Don’t worry, we’ll see what we can do.
Do not publish your real e-mail address, within a week it will be scraped and disseminated throughout the underground spam world.
Today is month end, be sure to log off the accounting server promptly at 5:15 PM.
In each sentence, two independent clauses — parts that could stand alone as sentences — are joined by a comma.
That’s called a comma splice, and it is, or at least was, a big no-no. You can join the independent clauses in other ways, though. You can make two sentences:
Don’t worry! We’ll see what we can do.
You can use a semicolon:
Today is month end; be sure to log off the accounting server promptly at 5:15 PM.
You can use an em dash if you want to be less formal:
Do not publish your real e-mail address — within a week it will be scraped and disseminated throughout the underground spam world.
A comma marks a slight pause; when it’s used instead of a mark that indicates a distinct break, what you end up with is the syntactic equivalent of tailgating. It creates the most basic type of run-on sentence that we learn about in writing class.
But people seem to be losing their awareness that a comma joining two independent clauses is a mistake. It certainly seems as though the British have lost any sensitivity to it, if the communications I receive from my quite learned colleagues in the UK are any indication. As far as American English goes, I blame the tech people, especially the ones who may be great programmers but should never be allowed to write any copy the customer actually sees. They’re responsible for the ubiquity of messages like “You have entered an incorrect password, please contact your system administrator” or “Check your inbox, a confirmation has been sent.” If you think about it, we read messages such as these with great frequency, so we shouldn’t be too surprised if they’ve lost their power to jar. And once an error no longer jars, it’s not long before we no longer notice it, and then even begin to reproduce it.
(Cue the heavy sigh.)
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Comma splice, English punctuation, Run-on sentence Posted in Copyediting Tip of the Week | 2 Comments »
January 26, 2010
By Wendalyn Nichols

Subject: Right back atcha, Mr. Hyphenator
In the February–March issue of Copyediting, Linda Lowenthal writes about one of the most common stumbling blocks for copyeditors: hyphenating compound modifiers. In that article, she quotes an argument made by Bill Walsh in a blog post on Blogslot.com against a principle I use to determine whether some compounds need to be hyphenated. More on that in a moment, but first let’s describe the problem.
Hyphens help a reader know what parts of a compound modifier belong together as a unit and what parts are modifying the noun separately. An example I often use is white-veiled woman: with a hyphen, the woman is wearing a white veil, but we don’t know her race; without a hyphen, the veiled woman is white and we don’t know the color of the veil.
In the above example, the compound modifier is made up of two adjectives, each of which might reasonably be taken to be modifying the noun separately. Because of the ambiguity, it helps to use a hyphen to specify that the first adjective is modifying the second one rather than modifying the noun.
In some cases, what modifies what is completely clear. That’s why we don’t hyphenate compounds with -ly adverbs or those with very in them: we know that in a very gloomy mood, very is modifying gloomy, and that in a closely guarded secret, closely is modifying guarded. Similarly, capitalized compound modifiers don’t need to be hyphenated because we can readily see what the unit is: a United Nations resolution is not a united resolution of nations, but rather a resolution passed by the United Nations. We don’t need a hyphen to tell us that United Nations is a single unit.
Compound modifiers come in lots of combinations: adjective + noun (dark horse, snowy owl); noun + noun (town hall, maple syrup); adjectival participle + noun (marching band, split infinitive, chopped liver); and many others. Combinations such as those I’ve just cited are called fixed compounds: they have at least one discrete meaning, occur frequently and always in a fixed form, and have their own entries with definitions in dictionaries. Far more combinations are temporary compounds: I can write about a seven-step process but you won’t find an entry for seven step in a dictionary.
I have no quibble with using hyphens to join the parts of a temporary compound to show that they should be interpreted as a unit; doing so clarifies where the compound begins and ends. But I’ve long argued that fixed compounds don’t usually require hyphens for them to be understood as modifiers. A hyphen is a tool to use when ambiguity is a real risk, but when it is not — when no one would interpret maple syrup bottle as meaning the syrup bottle was made of maple — then using one is unnecessary. Insisting on ground-squirrel burrow, combat-fatigue symptoms, fox-trot steps, frying-pan handle, and the like is overly fussy, to my mind.
In saying this, I differ from Walsh, who would have us hyphenate high school cafeteria, presumably because we might otherwise think the school cafeteria was built on a hill, or on stilts. Linda Lowenthal says in her article, “Leaving compounds open if they’re in the dictionary is consistent — to someone who’s using the same dictionary as you, and who understands that this is why watercolor-painting classes is hyphenated but oil painting classes is not.” She goes on to thank Walsh for the example, citing his blog entry “How About It, Hyphen Haters?”
Here’s the full context, from a comment Walsh made on that post:
The permanent-compound approach (”law enforcement” isn’t in Webster’s New World, by the way) is flawed in at least a couple of big ways. “Oil painting” is in the dictionary, but “watercolor painting” isn’t, so you’d have “oil painting classes and watercolor-painting classes”? And some of those compounds are arguably onewordable — if rollercoaster seems like at least a possibly valid choice, I think it has to be “a roller-coaster ride,” not “a roller [dramatic pause] coaster ride.”
The idea behind the “onewordable” comment is that leaving a compound open makes its two parts seem less related, even though the open spelling is essentially arbitrary. (The fact that the two words have remained separate is simply an accident, judging by how many compounds have come to be spelled as closed over time.) Best to use a hyphen, Walsh argues, because it helps show how closely connected the words are.
But I don’t buy the “dramatic pause” argument. If the gap is so obtrusive, then why not insist that all open compounds be hyphenated or just closed up in all instances? Why insert a hyphen only when the compound is a modifier — and then only when it is in an attributive position, not when it comes after a linking verb? I think we come right back to the two core points, that hyphens are needed when ambiguity is possible, and not needed when it isn’t; and that they are needed to show where a temporary compound begins and ends, but usually not needed for fixed compounds.
I say “usually,” because in fact I would hyphenate oil-painting class. In the example of oil painting, Walsh is perhaps thinking, not without justification, about those who follow rules slavishly and treat dictionaries as holy writ — who might indeed determine that, since Wendalyn’s Principle is not to hyphenate compounds that have dictionary entries and to hyphenate ones that don’t, the right choice would be to hyphenate watercolor-painting class and not oil painting class. But dictionaries include or exclude entries for a number of reasons, and so the fact that a given compound has an entry can mean that one should consider the semantic pattern this entry represents in one’s determinations, whether all the possible iterations of that pattern are presented in a given dictionary or not. And in the particular case of oil painting, the primary meaning (an object, a work of art painted in oil) is so strong that it’s entirely possible that a reader would start to misread the modifier (which employs a secondary meaning) as a noun in its own right: “Free oil painting. Class. Oh, free oil-painting class.” Consideration of the context absolutely must come into play.
This means there isn’t a neat rule that will apply in all instances; as Lowenthal said, “Short of the hyphenate-everything approach, in fact, just about any system you devise risks looking inconsistent to someone.” If Walsh were to advocate the hyphenation of compounds whenever they are modifiers, regardless of position, that would be truly consistent. But I think even he would say that that would be overkill; and it would then seem arbitrary not to hyphenate all compounds all the time, and be done with it. All we would have done would be to shift the battle lines. Yet spelling is moving away from the hyphen: even the latest edition of The Shorter Oxford Dictionary made news a couple of years ago for its hyphen purge.
So the upshot is that Walsh and I draw the line in different places. I find the fixed-compound principle to be helpful (notice that I just hyphenated a temporary compound); I also, however, hyphenate compounds such as up-to-date when they occur after a linking verb, because they so often cause miscues on first reading when they are left open. I’m not worried about inconsistency — I don’t think many readers notice any system at all in the application of hyphens anyway, unless they’re used in ways that seem jarringly quaint. (As they do most of the time in fixed compounds, I would argue.) I’m more concerned about being unobtrusively helpful, allowing hyphens to do their job without calling attention to themselves.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Bill Walsh, Compound modifiers, English punctuation, English style, Hyphens Posted in Copyediting Tip of the Week | 5 Comments »
January 20, 2010
By Wendalyn Nichols
FIDDLY RULES 11: “Compare with/to”
The eleventh in a series of podcasts about fiddly rules that Copyediting editor Wendalyn Nichols says are nevertheless ones that careful writers follow. In this episode, fiddly rule number 11: Observe the distinction between “compare with” and “compare to.” (3 min.)
Click here for more FREE podcasts on the topic of copyediting.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Fiddly Rules Posted in Podcasts | No Comments »
January 18, 2010
By Wendalyn Nichols
FIDDLY RULES 10: “As opposed to”
The tenth in a series of podcasts about fiddly rules that Copyediting editor Wendalyn Nichols says are nevertheless ones that careful writers follow. In this episode, fiddly rule number 10: Save “as opposed to” for true opposition. (2 min.)
Click here for more FREE podcasts on the topic of copyediting.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Fiddly Rules, opposition Posted in Podcasts | 1 Comment »
|
| |