| |
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 | 1 Comment »
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 »
January 18, 2010
By Wendalyn Nichols

Subject: An anacoluthon?
I came back from a longer-than-anticipated break last week to a very full in box. Tucked in among the great many notices about comments on the blog (all spam) was a legitimate query from an editor who writes to me with some regularity. He wondered whether he should be concerned about the construction of the following sentence:
When Europeans first arrived in Zululand, they appear to have been welcomed by the Zulu…
He wrote:
I’ve run into this in three of my last four projects. What the writer means, of course, is something like, “It appears that when Europeans first arrived…, they were welcomed …” And of course there are other ways of rewriting the sentence.
The tense inconsistency is illogical, isn’t it? Is this where we get to use that cool word anacoluthon? Should I correct it?
An anacoluthon is an abrupt change from one construction to another in the middle of a sentence. (The word, meaning ‘a logical inconsistency’, is Greek in origin.) I don’t think that is quite what we have in the example sentence, because the first clause does depend on the main clause. (Merriam-Webster’s Collegiate Dictionary, 11th edition, gives “I warned that if he drinks, what will become of him?” as an example of an anacoluthon.) What we have here is a much more familiar problem: a type of dangler.
It isn’t your common species of dangler, though, because they does indeed refer back to Europeans. The problem is that they, the Europeans, are not doing the appearing. The missing subject is a dummy subject, it:
It appears that, when Europeans first arrived in Zululand, they were welcomed by the Zulu…
Many writers have been taught that dummy subjects are always bad style, which is overstating things. Dummy subjects are very useful at times, but they should not be used to gloss over a lack of research on the writer’s part. It may be that the writer of the sentence in question was simply avoiding a dummy subject on principle and didn’t realize what effect it would have, but it might also have been deliberate, an attempt to obscure the fact that he or she hadn’t bothered to find out more specifics about the assertion.
A more accurate sentence would have attributed the assertion to a source—something along the lines of “Early records indicate that…” or “According to the journals of the first Europeans to arrive in Zululand, the newcomers were initially welcomed…” 
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Anacoluthon, English grammar Posted in Copyediting Tip of the Week | No Comments »
December 24, 2009
By Wendalyn Nichols
FIDDLY RULES 9: “Disabuse,” “disavow,” and confusables in general
The ninth 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 9: “Disabuse,” “disavow,” and more on Confusables in general. (4 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 »
December 21, 2009
By Wendalyn Nichols

Subject: A likely story
Note: The Tip writer will take her customary holiday break at the end of the year. The Tip will return on January 11, 2010.
Last Thursday, I’d finished my commuting book on the way in to work, so I picked up an afternoon tabloid to read on the way home. After reading a few pages, I was struck by something, then quickly flipped through to see whether the phenomenon I’d noticed was repeated throughout the paper. It was.
I’m talking about the use of the word likely in headlines. Seems it’s a frequent go-to word for headline writers, and not just the ones who work for the paper I was reading. I looked up likely in Google News when I got home, and a significant majority of the hits that were returned were from headlines.
Likely is one of a relatively small group of adjectives that end in -ly (unseemly, goodly, and portly are some others). Perhaps for this reason, a myth has been perpetuated that it can never be used adverbially. Before we get further in this discussion, let’s make sure you can spot the difference. In which of the following headlines is likely being used adverbially? (Some of the headlines are down-style, which is common for Web sources.)
1. Hazardous Mayon volcano eruption likely
2. Nick Johnson’s one-year deal with New York Yankees likely spells end for Johnny Damon with Bombers
3. Will Yankees Consider Matt Holliday with Johnny Damon’s Likely Departure?
4. Hanson says he’ll likely sign NDSU smoking ban
5. Guinea massacre likely a ‘crime against humanity’: HRW
6. No Change Likely In How NJ Fills Senate Vacancies
7. Full report of shooting likely still weeks away
8. US Attorney: Bruno likely to do prison time
9. Gibbs isn’t likely to be in the mix
10. Winter storm likely tonight
Seven of these headlines use an acceptable shortened form of “is likely to” or “is likely.” If you can expand a use of likely to the full phrase and it will still work in the sentence, then likely is acting as an adjective: “A winter storm is likely tonight.” “Guinea massacre is likely to be a ‘crime against humanity.’”
Headline number 9 uses the full form in the negative, “isn’t likely to be.” (I wonder why the writer didn’t choose unlikely there.) Likely can be used with linking verbs besides to be, as in seems likely, appears likely, and so on.
One of the headlines, number 3, shows how the adjective can be used in premodifying position—that is, before a noun (departure) instead of after a linking verb. This structure is less common, but it is exemplified in the idiomatic phrase that is the title of this Tip.
So that leaves headlines 2 and 4. In neither case is likely short for “is likely (to).” Both times, it is modifying a verb: in “likely spells,” it modifies the main verb in the present tense; in “will likely sign,” it modifies the main verb as part of the simple future structure.
In both cases, the use of likely as an adverb is helpful. Headline 2 is already quite long and does not need the wordy “is likely to spell” when “likely spells” is perfectly clear. “Hanson likely to sign NDSU smoking ban” would lose the attribution; in the existing headline, it is clear that the assertion of likelihood came from Hanson himself, so it carries more weight. Here again, “Hanson says he’s likely to sign NDSU smoking ban” is unnecessarily wordy.
In running text rather than headlines, I think the adjectival forms read better. But I encourage you not to correct every adverbial use of likely on principle. The principle isn’t actually as strict as that.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: English usage, likely Posted in Copyediting Tip of the Week | 1 Comment »
December 17, 2009
By Wendalyn Nichols

Subject: Two great gifts for the copyeditor in your life
Just a quick message: if you’re searching for the right holiday gift for your favorite copyeditor — or for anyone who’s passionate about good writing — I heartily recommend the following:
The Subversive Copy Editor: Advice from Chicago (or, How to Negotiate Good Relationships with Your Writers, Your Colleagues, and Yourself), by Carol Fisher Saller. University of Chicago Press, 2009.
The Chicago Manual of Style and other style manuals and usage books tell us more than we’ll ever remember about the dos and don’ts of writing and editing, but they don’t teach us how to be good editors and writers. Carol Fisher Saller, who answers the three-thousand-plus questions that people submit each year to the Q&A page at The Chicago Manual of Style Online and is a senior manuscript editor at the University of Chicago Press, has written a book that is all about the how.
When I received an early review copy of The Subversive Copy Editor, I stayed up far too late to finish it. I told Saller I felt as though I’d been to a revival meeting after reading it, that everything I’d ever hoped to accomplish as an editor and trainer was affirmed in it. She helps us step back and evaluate the way we do our jobs so that we can avoid letting our egos and our compulsions sabotage relationships with writers and colleagues, not allow our fondness for rules to limit our flexibility, and prevent disorganization from wreaking havoc with schedules and deadlines.
Publishers Weekly gave her book a starred review, calling it “relentlessly supportive” and saying it “may be the best copy editor’s companion since the CMS” and that “Saller writes with wisdom and a great generosity of spirit.”
Garner’s Modern American Usage, third edition, by Bryan A. Garner. Oxford University Press, 2009.
I reviewed GMAU3 in an extensive article in the December – January issue of Copyediting. Here, I’ll be brief: Even if you own the first two editions of what has become the usage bible for American writers and editors, get this third edition. The “Language-Change Index” alone is worth the price. In the main entries, Garner gives his weighty advice and passes judgment on good and bad usage, but then proceeds to give what are admirably unbiased assessments of how accepted, or not, a given usage has become, on a scale of 1 (still rejected) to 5 (fully accepted). You’ll also find more usage questions discussed in one place than in any other usage book.
 If you enjoyed this post, make sure you subscribe to our RSS feed!
Tags: Copyediting resources Posted in Copyediting Tip of the Week | 1 Comment »
|
|
|
|