On Crossing Borders

I’m thinking of you, Allen Sawan.

I’m in the U.S. — Massachusetts, to be exact — watching images and reading stories about adults detained, children taken from parents at the southern U.S. border. Their only crime, if they can be said to have committed one, is to have been born in the wrong place at the wrong time.

A place so unpredictable and violent that undertaking a many-hundred-mile journey north with a two- or five- or ten-year-old in tow seemed the better bet.

I lucked out. I was born into a safe place and a safe time. The only real dangers I’ve faced in my life have been dangers I courted, by speaking out when I could have been silent or walking into possible difficulty with my eyes wide open. Yet I can imagine the desperate conditions that prompted these people to make this terrible journey, hoping — knowing — that whatever place they arrived at would have to be better than the home they had left.

I’m not even a mother, but still — I can imagine.

Not easily, mind you. The mind flinches from imagining, the way a finger recoils from a hot burner. But I can imagine.

This is why I’m thinking of you, Allen Sawan. You were born in a fine place at a fine time, but when you were ten years old things went horribly wrong. The place was Lebanon’s Bekaa Valley. You turned ten in 1975, the year civil war broke out in Lebanon. Your life was changed forever. By the time you reached twenty, you wrote — much, much later — you “had seen more body bags than most people in the civilized world have seen garbage bags.”

I knew about Lebanon’s civil war. I thought I knew about Lebanon’s civil war. I started college as an Arabic major. If I hadn’t changed course, I probably would have spent my junior year in Beirut, around 1971–72, several years before everything blew up.

What was it, three and a half years ago? You contacted me out of the blue. As an editor I’ve been contacted out of the blue quite a few times by hopeful writers, and in most cases I’ve had to say: Not so fast. This isn’t ready for prime time.

But your sample chapters were ready. They took me somewhere I’d never been, into the world and mind of a young man not yet twenty whose life had been turned upside down and who had risen to the challenge.

Travvy and I read the very first copy of Allen Sawan’s Terrorist University.

We took each other on, editor and writer, writer and editor, and on an accelerated deadline you produced Terrorist University. It’s one of the books I’m proudest of having worked on. But you kept going. You found a mainstream publisher, and out came Al Shabah, The Ghost, closely based on Terrorist University but tighter. I was thrilled to find that the work we’d done together was pretty much intact.

In the years since, we’ve become friends — friends who’ve never met in person but still friends. You live in Ontario now. You and your wife have raised your three children in peace. Each of them was born in the right place at the right time, and their world didn’t turn upside down when they were ten.

I joke that Canada should build a wall on its southern border, to keep out the USians who despair of their country and want to emigrate to someplace better. You joke that you will build a tunnel that my dog and I could escape through. I know for absolute certain that if we needed that tunnel, you of all people would be willing and able to build it.

Your kids, like me, have been lucky. They were born at the right place and time, in a Canada that let you in and let you stay. They’ll learn about your life the same way I did: from the stories you tell so well.

So I’m thinking of you, Allen Sawan. Of you and your children — I’ve never met them either, but one of these days I think I will. Of all you went through to make it possible for them to grow up more like I did and less like you did.

And I’m thinking of the children taken from their parents at the U.S. border. What stories will they have to tell, ten and twenty years from now? What lessons will they pass on to their children?

What stories will the parents tell? Of struggling against such odds to get this far, and then being treated like criminals by the richest country on earth?

I think of your story, Allen Sawan. It never goes away.

Writing for Change

Over the holiday weekend I drafted a letter to the editor of my area’s two weekly newspapers, the Martha’s Vineyard Times and the Vineyard Gazette. (Can you guess where I live?) The letter dealt with ways to reduce gun violence. By the time I emailed it off yesterday morning, eight other women had reviewed it, commented, and signed on. All were members of a local women’s group I belong to. (A 10th signer was added last night.) You can read the pre-publication text on the website I manage for this group.

A couple weeks ago, I blogged about Postcards to Voters (PTV), a national all-volunteer outfit that writes get-out-the-vote (GOTV) postcards to Democratic voters in state and municipal elections across the country. My #1 goal was to let others know about PTV and encourage them to get involved. To make sure I got my facts right, I emailed the link to the leader of the group. He emailed back to say he’d already shared the link with a candidate inquiring about PTV and was planning to do so again.

On the editorial side, when I first saw the political e-newsletter What The Fuck Just Happened Today? (WTFJHT — “Today’s essential guide to the shock and awe in national politics”), it was love at first sight. When curator-editor-publisher Matt Kiser put out a call for assistance — not just for financial contributions to enable him to do this full-time but for volunteers to help with the writing and editing — I thought, Hey, I can do this.

So now I copyedit most issues on the fly. The first draft of each issue usually appears online in very early afternoon Eastern Time (Matt’s on the West Coast). I’m on- and off-line a lot while I’m working, so I generally catch it not long after it posts. Editing is via GitHub (which took me a while to figure out, but I managed).  Matt appreciates my contribution, I keep up with the national news, and I have the immense satisfaction of putting my skills to good use.

I don’t know about you, but when I think about writing and editing, it’s usually with the product in mind: books, stories, poems, reviews, plays. newspaper features, blog posts, etc. I tend to forget that writing and editing are also useful skills with lots of practical applications. In these trying political times, the need for clear writing has never been greater. For starters, activist groups frequently have occasion to issue press releases, letters to the editor, position papers, and calls to action.

Plenty of people have the ability to produce such documents, but those of us who practice writing and/or editing as vocation or avocation have an edge that comes with experience. An example: On social media and in the organizations I’m involved with, I’ve noticed that capable writers often don’t think enough about their audience. I’ve seen arguments and even flamewars ignited by careless wording. Earnest activists sometimes forget that to be effective, what they write must be read and, ideally, shared; and readers all too readily skip over documents that are so jam-packed with detail that there’s no white space on the page.

Press releases and letters to the editor are more likely to make it into print if they’re clear, concise, accurate, and well organized. Posters are more effective when the information on them is correct and complete, and if you’re paying for printing, it’s a lot cheaper to get it right the first time. Lots of people can spot the occasional typo (and crow loudly about their catch!), but it takes someone with proofreading or copyeditorial experience to maintain the focus to do it consistently.

So, writers and editors, the Resistance needs your skills, and maybe you’d find the experience of putting them to good if unpaid use immensely satisfying.

Of Older Styles

Editors, writers, and other word people sometimes get into battling about style as if their lives, or at least the fate of the English language, depended on it.

“The Chicago Manual of Style says . . .”

“But according to the Associated Press . . .”

“That’s not true of British English . . .”

And so on and on and on.

Lately, for a writing project, I’ve been reading works published in the U.S. in the 1840s and 1850s. For the record, so far they include Narrative of the Life of Frederick Douglass, (1845); Harriet Beecher Stowe’s Uncle Tom’s Cabin (1852); and Solomon Northup’s Twelve Years a Slave (1853), as well Escape to Freedom, a young adult adaptation of Douglass’s Narrative, and Douglass’s very famous Fourth of July speech from 1852, which I’ve had the honor of reading parts of aloud at an annual performance.

The contemporary editions of all the full-length works retain the style, spelling, and punctuation of the original. While my writer-reader self takes in the content, my copyeditorial self is noting especially the style choices that contemporary U.S. editors might take issue with.

Perhaps my most important takeaway is that I’ve found all of these works, published between 164 and 172 years ago, readily comprehensible. The words I didn’t recognize are still found in English-language dictionaries. With the works of Shakespeare and others of his time — the late 16th century and early 17th — my eyes often drop to the footnotes. Footnotes were neither provided for nor required by this 21st-century reader of these mid-19th-century works.

To be sure, my 21st-century sensibility sometimes got impatient with the flowery style and digressions of Uncle Tom’s Cabin, not to mention some plot implausibilities toward the end, but Stowe’s interwoven stories, her attention to detail, and her acute insight into human nature more than made up for it. Twelve Years a Slave is a page-turner from beginning to end, and the main reason Douglass takes me longer to get through is that I often pause to read passages aloud — a practice I highly recommend, and not just with the Fourth of July speech.

If you’ve read my recent and not-so-recent posts on the subject, you won’t be surprised that my copyeditorial eye paid particular attention to hyphenation. All these works use considerably more hyphens than either Chicago or AP allows, or even the more hyphen-friendly online Oxford (UK version).

Opening Twelve Years a Slave at random, I find work-bench, blood-hound, and half-way on facing pages. Merriam-Webster’s Collegiate (MW) and the UK Oxford have them all solid, one word, no hyphen.

A single page of Uncle Tom’s Cabin offers store-room, linen-presses, and china-closet all in the same sentence. Current English style would make storeroom one word and both linen presses and china closet two.

Aside: For storeroomMerriam-Webster’s notes the first usage as 1685. It does not note whether that first usage was one word, two, or hyphenated, leaving one to believe that it’s been one word all along. I tend to doubt it. This is one of my pet peeves with MW and one reason I prefer the American Heritage Dictionary. AHD is more likely to offer the hyphenated alternative for words that are indeed styled both ways in good English-language writing.

In Twelve Years a Slave some two-word proper nouns are hyphenated, notably New-York and New-Orleans. The styles I’m familiar with all dispense with the hyphen, probably on the theory that it’s obvious the two words constitute one name. The older style survives in the official name of the New-York Historical Society.

As noted in my earlier “Dash Away, All” post, Chicago style advises an en dash when such an “open compound” is joined to another word, as in New York–Boston train. It’s unlikely that, if only a hyphen were used, anyone familiar with U.S. geography and/or capitalization style would ever read that as a “new York-Boston train,” but I’ve been en-dashing such constructions for almost 40 years so the hyphen just doesn’t look like enough.

Reading Uncle Tom’s Cabin I noticed almost immediately the unusual — to me — styling of contractions.  In most cases Stowe and/or the typographer inserted a space between the two words being fused together: I ‘ve, I ‘ll, it ‘s, is n’t, did n’t, there ‘s, and so on. However, in a few cases the contractions are set solid, the way we’d style them today: can’t and an’t. An’t, which we would write ain’t (but never, ever use except in the most colloquial dialogue), contracts either am not or are not; thus it might have been rendered a’ n’t. Quite possibly that failed Stowe’s “it looks funny” test, as it fails mine. And since cannot appears as one word, it makes sense that the contraction can’t would do likewise.

For a semicolon-lover like me, these 19th-century works are a feast. Douglass, Stowe, and Northup were not afraid of long sentences, and for writers of long sentences semicolons are indispensable. Stowe sometimes strings as many as four independent clauses together with semicolons, a practice that would send most U.S. copyeditors screaming for their red pencils (or, more likely, their Track Changes). And Northup writes, of Mistress Epps:

She had been well educated at some institution this side the Mississippi; was beautiful, accomplished, and usually good-humored.

(Are you itching to insert an of after “side”?)

Stowe is very fond of dashes, though not as fond as Emily Dickinson, and often, though by no means always, her dashes are preceded by a comma: “Topsy only thought Eva’s speech something funny and inexplicable,—she did not believe it.” Northup’s aren’t, and neither are Dickinson’s. In the later The Minister’s Wooing (1859) and Oldtown Folks (1869), Stowe was still preceding dashes with commas and even semicolons. Clearly no editor was telling her that this just wasn’t done,—or if they did, she was having none of it.

Dash Away, All

Dashes and hyphens are so often considered together that when I got to the end of “Sturgis’s Law #10,” I knew something was missing. After all, the Chicago Manual of Style (CMS) devotes several pages to dashes, and so do many other style guides. Surely I should devote at least a few words to the subject?

But I’d already gone on too long (blog posts that top 1,000 words make me nervous), and besides, nowhere in Sturgis’s Laws are dashes even mentioned. (That may change in the future.)

Meanwhile — let’s talk about dashes.

In U.S. usage, dashes come in two sizes. The em dash ( — ) is so called because it’s generally the length of one m. The shorter en dash (which, surprise surprise, is the length of an n) is the one that gets mixed up with hyphens.

As my typographer friends point out, a dash is a dash. How it’s styled — em or en, with or without space before and after — is a typographical decision. In British English (BrE) the kind of dash that indicates a break or sets off parenthetical remarks (as in the previous sentence) is generally rendered by an en dash with a space on either side, like this: How it’s styled – em or en, with or without space before and after – is a typographical decision.

  • To create an em dash on a PC: Alt+0151 (use the number pad) or ALT+CTRL+minus key (the latter works in Word but not in WordPress). Using AutoCorrect, you can also tell Word to automatically convert two hyphens (which is how we indicated em dashes back in typewriter days) to an em dash. I don’t allow Word to AutoCorrect anything, but you may be more tolerant than I.
  • To create an en dash on a PC: ALT+0150 or CTRL+minus key (see above)
  • To create an em dash on a Mac: Option+Shift+minus
  • To create an en dash on a Mac: Option+minus

In this blog and in my own writing, I insert a space on either side of my em dashes. This is to avoid bad end-of-line breaks. Word processors may treat “styled—em” in the sample sentence as one word and keep it all on one line, which may lead to an unsightly gap in the line preceding. The shorter dash seems to be coming into its own in ebooks, and with good reason: ebooks can be read on devices with relatively narrow lines, and in a narrow line a full em dash can look huge.

Em dashes generally herald a break of some kind. In dialogue, they are commonly used to indicate in interruption: “But I was about to say—” Frankie began before Sal cut her off. (Dialogue that trails off is generally indicated by an ellipsis. For more about this see “Of Dots and Dashes.”)

In non-dialogue, they can signal a change of subject or an aside. When the aside occurs in the middle of a sentence, it becomes more or less a parenthetical and is set off by em dashes. Why not use parentheses in such cases? You can use parens in such cases. For me an aside set off by parens is more peripheral — expendable, even — than one set off by dashes.

Em dashes are big. They call attention to themselves. Flip through a book — on paper or on screen — and chances are your eye will be drawn to the em dashes. If a writer is overusing em dashes, it’s often the first thing I notice when skimming through a manuscript. So use them sparingly. Like just about everything else in writing, they lose their power when overused.

Emily Dickinson is noted for her extravagant use of dashes, but she could get away with it because (1) she was a poet, (2) her poetry was brilliant, and (3) she was writing in the 19th century, before the Chicago Manual of Style was invented. Long after she died, one of her editors got into big trouble for taming her dashes into commas. If you’re adding Dickinson’s collected poems to your library, make sure the edition you choose has the dashes.

En dashes are somewhat specialized, and different styles have different takes on when to use them. In the social sciences, for instance, an en dash is often used to indicate that a compound comprises two words of equal weight, e.g., “I’m a writer–editor.” Chicago does not recommend this, and neither do I. Here’s my reasoning: The difference in length between a – and a – is not huge. When you’re reading along, you may not notice it at all — unless of course you’re a copyeditor like me. If it is important to know that the two halves of a compound are of equal weight, I would not depend on an en dash alone to get that across. However, if you’re in a field that follows this style, you should too.

Here are the most common uses of en dashes, per Chicago:

  • To signify through in number ranges: pages 3–17; the years 1941–1945. The range can be open-ended: my dog Travvy (2008–).  Figures and tables in nonfiction books are often given numbers like 2-5 and 3-17. The hyphen denotes that this is NOT a range; the first number is generally that of the chapter and the second that of the particular figure or table. The distinction comes in handy in footnotes and endnotes, where page ranges run rampant and table and figure numbers are sometimes concealed among them. By the way, It’s a faux-pas to use the dash when the range is preceded by from: She lived in France from 1978 to 1982, not “from 1978–1982.”
  • To signify to in destinations, votes, or scores: the Boston–Washington train; my team won, 99–92; the vote was 5–4.
  • To form compounds when one element is itself an open compound: the post–World War II baby boom; the New York–Boston rivalry. This is to avoid reading the former as post-world and the latter as York-Boston. Editors sometimes differ on which open compounds have to stay open and which can be hyphenated when attached to prefix, suffix, or another word. Proper nouns generally stay open, but when the New-York Historical Society was founded in 1804 another style prevailed, and its official name is so styled to this very day. Chicago 16, section 6.80, recommends country music–influenced lyrics, but I see nothing wrong with country-music-influenced lyrics.

All clear now? Dash away, dash away, dash away, all. And I really should come up with a dashing Sturgis’s Law . . .

Sturgis’s Law #10

Some while back I started an occasional series devoted to Sturgis’s Laws. “Sturgis” is me. The “Laws” aren’t Rules That Must Be Obeyed. Gods forbid, we writers and editors have enough of those circling in our heads and ready to pounce at any moment. These laws are more like hypotheses based on my observations over the years. They’re mostly about writing and editing. None of them can be proven, but they do come in handy from time to time. As I blog about them, I add them to Sturgis’s Laws on the drop-down from the menu bar. Here’s Sturgis’s Law #10:

“Consistent hyphenation” is an oxymoron.

According to Sturgis’s Law #5,  “Hyphens are responsible for at least 90 percent of all trips to the dictionary. Commas are responsible for at least 90 percent of all trips to the style guide.”

Arbiters of style.

No, that 90 percent figure isn’t based on any survey, much less a scientific study or even systematic observation of my own practice. Good editors and writers are always looking things up. But commas and hyphens seem to provoke an anxiety that needs frequent reassurance even when we really do know our stuff.

Funny thing, I was blogging about commas only last week — and quoting Sturgis’s Law #5. So hyphens seem to be a logical next step.

And yes, it is OK to use “hyphens” and “logical” in the same sentence. If you understand the logic behind hyphenation, you won’t spin yourself into a tizzy whenever dictionaries and style guides disagree.

Which they do. A lot.

Hyphens can do many things, but the two biggies are joining and separating. Hyphens are so clever that they occasionally do both at the same time.

A hyphen can fuse two words capable of standing alone into a compound that incorporates both: I’m a writer-editor. The pond looks blue-green.

It can join a prefix or suffix to a root word: an anti-intellectual movement, a business-like attitude. In the former example, the hyphen is also separating the two vowels. Except in skiing and taxiing and maybe a few other words that I can’t think of at the moment, i‘s rarely occur side by side in English, so it looks pretty weird when they do.

Several common prefixes end in e — re- and pre- come immediately to mind — and when they run up against another vowel, misreadings can happen. I can’t look at reignite without initially seeing reign. Plenty of writers have no problem with reignite, but if an author prefers re-ignite, I have no problem with it.

In some cases the separation is crucial. Consider the difference between coop and co-op.

The Chicago Manual of Style (CMS), the style guide I use most often, has a long section on hyphenation. In the 16th edition, which has just been superseded by the 17th, it’s section 7.85. It is very, very useful. Plenty of hyphenation decisions can be, in effect, automated: Always use them in some cases (e.g., second-floor apartment, forty-one); never use them in others (e.g., grandmother, northeast).

In other cases, though, there’s plenty of gray area. CMS’s recommendations rely almost entirely on patterns: adjective + participle, gerund + noun, and so on. It suggests hyphenating most compounds when they occur before a noun — a well-rounded education — but leaving them open after a noun: Her education was well rounded.

What CMS and many copyeditors don’t acknowledge often enough is that the words themselves make a difference, and so does the intended audience. CMS does advise taking “readability” into consideration, but what’s readable and what isn’t depends a lot on context. Some noun + noun compounds are so familiar that inserting a hyphen when they appear before a noun looks like overkill. Yeah, “high school student” could be read to mean a school student on drugs, but when was the last time you saw it used that way?

On the other hand, “running shoe store” could conjure unintentionally hilarious images in enough readers’ minds that “running-shoe store” seems the better option.

CMS recommends that adjectives formed with half- be hyphenated before or after a noun but that nouns so formed be open. OK up to a point, but half sister strikes me as odd because all those half- relationships are words in their own right. Besides, if stepsister is one word, why should half sister be two? This is why “consistent hyphenation” is an oxymoron.

It’s also why I think writers and editors are well within their rights to impose some consistency and logic on hyphenation in a particular work, even if this involves deviating from the recommendations of dictionary or style guide. The American Heritage Dictionary (AHD) lists policymaker as one word. In Merriam-Webster’s Collegiate (MW) it isn’t listed, which means it’s two words. AHD has both policymaking and policy-makingCMS would probably suggest policymaker for the noun (by analogy with shipbuilder) and policy-making when it precedes a noun. But what if you’ve got people who make policy and people who make decisions in the same paragraph?

With certain prefixes, like pro- and anti-, separating the prefix from the root with a hyphen calls a little more attention to the root. Consider pro-choice and prochoiceanti-choice and antichoice. In this case I’m all for the hyphen, but when an author hyphenates something that I probably wouldn’t, there’s a distinct possibility that s/he’s seeing or hearing a distinction that I don’t.

Most non- words can be safely closed up, but with new or unfamiliar coinages, a hyphen can be helpful. A recent author used non-state actors several times. Fine with me. British English tends to hyphenate more non- words than its American counterpart: NGO is spelled out non-governmental organization, not nongovernmental organization. If a U.S. author wants to do likewise, fine with me.

I’m proud to call myself a HARPy — HARP stands for Hyphens Are a Reader’s Pal. When I come across a hyphen that doesn’t follow the “rules” of the guiding dictionary or style guide, I ask, Is it useful? Does it get in the way? Is it consistent with the author’s other preferences? Sometimes I’ll consult CMS, MW, AHD, and the UK English section of the online Oxford Dictionaries. If it passes muster, I’ll enter the spelling in my style sheet so I’ll remember it if it comes up again, and so the proofreader will realize that this was a conscious choice, not a mistake.

Wield hyphens with confidence. They’re helpful little buggers, and nothing to be afraid of.

 

Editing Workshop, 7: Commas

Extra commas.

I just copyedited a very good memoir that was seriously overburdened with commas. According to Sturgis’s Law #5,  “Hyphens are responsible for at least 90 percent of all trips to the dictionary. Commas are responsible for at least 90 percent of all trips to the style guide.” I have written about commas (and hyphens!) before, but thanks to this job I’ve got plenty of examples of unnecessary and even misleading commas in my head, so this seems a good time to write about them again.

Rest assured that it will not be the last time, and if you’ve got any comma questions or comments, please do use the contact form at the end to send them in.

The examples follow the structure of the original, but I’ve changed the words because quoting without permission from an as-yet-unpublished book is ethically dubious. Not to mention — I don’t want anyone to think less of an excellent book because the uncopyedited manuscript had too many commas in it.

When she arrived at the concert hall early, she discovered that the rest of us were early, too.

There’s a zombie “rule” (a rule that no matter how often it’s refuted keeps coming back from the dead) floating around that you must have a comma before “too” at the end of a sentence. Not only is it not required, sometimes it actually gets in the way: your eye pauses briefly before it gets to the end of the sentence. If you want that pause, by all means stet the comma. If you don’t, take it out.

“Too” doesn’t often show up at the beginning of a sentence, but when it does, you will almost certainly want a comma after it. Same goes for “also.” They generally link the sentence to the one preceding. This is often OK in informal writing, but it can come across as rushed or sloppy when you’re trying to make a good impression.

The comma after “early” in the example is a good idea. When an introductory phrase or subordinate clause is short, you can often get away without the comma — “When she arrived I was on my second beer” — but if there’s any chance that the phrase or clause might slide into the main clause, consider using a comma.

Once he’d read the street signs, and consulted the map, he pulled away from the curb.

We’re looking at the comma after “signs.” I could make a case for it if the author wanted a bit of a break between the reading and the consulting. But I’m pretty sure he didn’t. When I’m editing, I note what the writer does habitually. This writer inserted a comma before the conjunction “and” so often that I wondered if maybe he thought it was a rule, like that comma before “too” at the end of a sentence.

A very strong convention — “rule,” if you will — is to use a comma before any conjunction that joins two independent clauses. This convention makes enough sense that the burden is on me or the writer to show that it’s not necessary, for instance when the two clauses are very short: “I got home from work and we sat down to dinner.”

I deleted the comma after “signs” but kept the one after “map,” which ends a rather long introductory subordinate clause.

After she entered the hall, so many people swarmed around her, as she moved toward the podium, that we couldn’t see her at all.

Notice the clause set off with commas in the middle of the main clause? Those commas make the clause almost parenthetical, meaning that you could omit it without losing anything. “. . . so many people swarmed around her that we couldn’t see her at all” does make perfect sense, but we no longer see the subject moving toward a podium. In other words, we’ve lost something. I deleted both commas.

When I’m copyediting, I want to improve the sentence as unobtrusively as possible. If this were my own sentence, I might revise with a heavier hand, perhaps “After she entered the hall and moved toward the podium . . .” Or maybe “. . . so many people swarmed around her that we couldn’t see her at all as she moved toward the podium”? Or maybe not. As is so often the case, there are several options, equally correct but somewhat different in nuance, emphasis, and/or cadence. Unless there’s a compelling reaason to do otherwise, I stick as close to the author’s version as I can.

As much planning as we did, to my way of thinking, we should have done more.

Here’s another thing to watch for when you come across a phrase or clause set off by commas in the middle of a sentence. The question here is about what half of the sentence “to my way of thinking” belongs with: “As much planning as we did to my way of thinking . . .” or “. . . to my way of thinking we should have done more.” Reading along, I skidded to a halt to sort this out. Based on both context and the sentence itself, I was pretty sure that the latter was intended, so I deleted the comma after “thinking” to avoid separating phrase from clause.

Mind you, if the whole sentence were “To my way of thinking, we should have done more,” that comma would have been unexceptional — not required, but not a problem either. In the middle of a complex sentence, however, it creates enough ambiguity to make a reader pause. In some cases, such commas or the lack thereof can even create serious confusion about the meaning of the sentence.

* * * * *

There’s plenty more to be said about commas, but I think this is enough for one post. Have you got a comma question, or a sentence that needs a second look, or one you successfully sorted out? Use this contact form to send it in, and I’ll work it into a future blog post — or reply privately if you prefer.

Go back

Your message has been sent

Warning
Warning
Warning
Warning
Warning

Warning.

 

Notes, Endless Notes

Beyond (possibly) acknowledgments and an author’s bio, fiction writers and editors generally don’t have to think much about backmatter. That’s a publishing term for the part of a book that comes after the main text ends.

Writers and editors of some kinds of nonfiction don’t have to think much about backmatter either. Memoirs and how-to books, for instance, may include a few endnotes and a “for further reading” list, but that’s usually it.

I edit a lot of the other kind of nonfiction. University press books, academic papers and dissertations, trade books about history or current events, that sort of thing. (Note:  “Trade” in this sense means more or less anything that isn’t academic.) These works are based on research, so documentation is crucial to their credibility.

If you’re somewhat familiar with a work’s subject matter, a skim through its bibliography can give you an idea of well the author has done his or her homework.

All sources are not created equal. Multitudinous notes and a long bibliography alone do not necessarily translate into a reliable book. Maybe 20 years ago I copyedited a mass-market book about UFOs. It cited plenty of sources, many of them on the World Wide Web (which was pretty new at the time). Fact-checking was part of my job, so I checked all the URLs. Woo-whee! This was my introduction to conspiracy theories about UFOs, alien abductions, chemtrails, and what has come to be known as the alt-right. The “evidence” for UFOs was internally consistent; it just wasn’t linked to the world of verifiable facts.

The job I just finished was thoroughly, even exhaustively, sourced. I was warned before I took it that the (electronic) manuscript was about 750 pages long and about a third of those pages were backmatter — endnotes and bibliography. Fine with me: I actually like copyediting this stuff. My detail-oriented brain kicks in, recognizes missing info and info out of place, clarifies inconsistencies, and knocks everything into shape.

Different fields and disciplines have different citation styles. Most of the books I work on follow one of two systems laid out in the Chicago Manual of Style,  often with some adaptations. I expected this one to do likewise.

Well, it did and it didn’t. In Chicago style, the titles of books and comparable works (such as films, TV shows, albums, full-length musical works, and the names of journals and newspapers) are generally italicized. Shorter works, like short stories, poems, songs, journal articles, and book chapters, are set in roman and with quotation marks. In the Works Cited section of this job, there were no italics and no quotation marks anywhere. My Chicago-trained eye had to look hard to tell the books from the articles. I had to figure out which was which and apply the appropriate style. I was warned about this too. “Billable hours,” said my production editor.

While editing the text (which presented few problems and was very interesting), I flipped back and forth between it and Works Cited, doing maybe 10 pages of entries at a time. I was cruising. It was a big job but for sure, I thought, I was going to make the July 5 deadline.

Then, around July 1, I took my first hard look at the endnotes. OMG. Most of the notes contained three to five citations in author-date style, often along with some text and a full citation or two. It was a hybrid of Chicago‘s two styles: notes and bibliography, and author-date. I’d never seen such a thing.

Author-date style is common in academic writing. You’re reading along and you come to a sentence like this:

The aardvark population of West Tisbury has been stable since 1998 (Sturgis 2016).

For the full citation, you flip to the Works Cited section, where you should find something like this:

Sturgis, S. J. 2016. “Do Aardvarks Help Curb Tick-Borne Diseases?” Journal of Creative Solutions 14(2): 37–42.

You should be able to find the source article, “Do Aardvarks Help Curb Tick-Borne Diseases?,”  on pages 37–42 of volume 14, issue 2, of the Journal of Creative Solutions.

In a work that uses the notes and bibliography style, instead of “(Sturgis 2016)” you’ll probably find something like this:

The aardvark population of West Tisbury has been stable since 1998.3

The superscript “3” tells you to go to note 3 for the current chapter, where you should find this:

Susanna J. Sturgis,  “Do Aardvarks Help Curb Tick-Borne Diseases?,” Journal of Creative Solutions 14, no. 2 (February 2016): 37–42.

In most cases (newspaper articles are a frequent exception), the work will also be listed in the bibliography:

Sturgis,  Susanna J.  “Do Aardvarks Help Curb Tick-Borne Diseases?” Journal of Creative Solutions 14, no. 2 (Spring 2016): 37–42.

In my author’s hybrid style, most endnotes included multiple author-date citations, each one of which had to be cross-checked on first appearance with the Works Cited list. I split my Word screen so I could flip back and forth easily between Notes and Works Cited . . . and realized PDQ that many — perhaps as many as 20 percent — of the works short-cited in the notes were not in Works Cited at all. And that some of those that were had discrepancies in the year of publication or the spelling of the author’s name.

Where discrepancies could be quickly resolved with an online search, I Googled. For each missing citation I typed a query in the notes: “Work not in Works Cited. Please add.” This quickly dwindled to the shorthand “Not in WC.” At first I typed a placeholder in the Works Cited list for the missing citation, but after chapter 4 I realized this was taking much too much time so I stopped.

Still, the billable hours were hefty, and I expect to pay off my credit card (dental bills!) and catch up with my quarterly tax payments when that invoice gets paid.

The moral of the story for writers: If you’re citing any sources in your work, get all the details and get them right. Familiarize yourself with the citation style(s) commonly used in your field. If you’re writing for a general audience in the U.S., Chicago will usually do. Your copyeditor will thank you, and if you’re paying the freight yourself, you’ll save a bunch of money.

Editing Workshop, 6: Parallelism

Chances are you’ve been told at least once by an editor, a teacher, or another writer that “this construction isn’t parallel.” Or someone has scrawled “faulty parallelism” in the margin of your manuscript or in a comment on your Word file.

This is shorthand for straying from, as Words Into Type puts it, “the principle that parts of a sentence that are parallel in meaning should be parallel in structure.”

Faulty parallelism comes in an daunting array of varieties. It can involve nouns, verbs, phrases, clauses, and whole sentences. It’s easiest to spot in a list, like this one:

These tips might help you complete a long writing project:

  • Schedule a specific time for writing.
  • Write even when you don’t feel inspired.
  • No distractions.

The first two elements are imperative verbs. The third has no verb at all. This is an easy fix: make the third element parallel to the first two by adding a verb. “Avoid distractions”? “Ignore distractions”? “Resist distractions”? It’s your call.

Faulty parallelism can be harder to spot in a sentence, especially a long, complex sentence — which is exactly where parallelism tends to go off the rails, so to speak. The list above can be turned into a sentence: “To complete a long writing project, schedule a specific time for writing, write even if you don’t feel inspired, and no distractions.” The sentence is short enough to make it pretty clear that something’s wrong.

The longer the sentence, the harder it can be to keep track of its parts. Here’s where the ability to diagram sentences can be very helpful. If you didn’t learn it in school or have forgotten how, plenty of websites out there can give you the basics, including “How to Diagram Sentences” on WikiHow.

It happens often enough that the parallelism is faulty but the meaning is still clear. I encounter many sentences like this one: “She let the dog in, gave him his supper, and then they went for a walk.” It sets off to be a series of three verbs with the subject “she,” but then the subject changes. What we’ve actually got here is two independent clauses, the first of which has two verbs, the second of which has one: “She let the dog in and gave him his supper, and then they went for a walk.”

I sometimes feel a little pedantic inserting the conjunction, because the meaning is clear, but often enough the meaning isn’t clear, or the sentence can be interpreted in more than one way. The other day I came across a doozy in a nonfiction book I’m copyediting. In this example, I’ve changed the details but retained the structure of the original. The original subject was a man who never wrote a best-selling novel and didn’t go to Spain either.

Mindy Moore had not begun to think about traveling to Spain, still less write her best-selling novel.

See the problem? There are three verbs in the first part of the sentence — “begun,” “think,” and “traveling” — and it’s not obvious which one “write” is meant to be parallel with. Keeping in mind that even very good writers occasionally mess up our verb tenses, you could read this in (at least) three ways, some of which might not be accurate.

  • Mindy Moore had not begun to think about traveling to Spain, still less written her best-selling novel. (“Written” is parallel with “begun”: “Mindy had not begun . . . and had not written . . .” If this were the intended meaning, I would probably insert “yet” before “begun” to make it even clearer.)
  • Mindy Moore had not begun to think about traveling to Spain, still less to write her best-selling novel. (“To write” is parallel with “to think,” meaning that Mindy hadn’t begun either to write her best-selling novel or to think about traveling to Spain.)
  • Mindy Moore had not begun to think about traveling to Spain, still less about writing her best-selling novel. (“Writing” is parallel to “traveling,” meaning that Mindy hadn’t even begun to think about writing her best-selling novel.)

Context gave me no clue about which of the three options was intended, but my gut said it was probably #2 because it was the easiest to clarify: add the “to” to show that “to write” was an infinitive and therefore parallel with “to think.” So I added the “to,” but I also queried the author and explained the other options. He’s the only one who knows for sure what he intended and what was in the subject’s head.

* * * * *

Got an editorial question or comment? Send it in on this form, or use the one in the “Got a Question?” tab at the top of this page.

Go back

Your message has been sent

Warning
Warning
Warning
Warning
Warning

Warning.

Shortening

The word count on draft #3 of Wolfie just slipped below 100000, from six digits to five, from this:

Word count for draft #2

to this:

Word count for draft #3 (in progress)

I cheered out loud, though (or maybe because) no one but the dog could hear me. Once he realized that no outing and no treats were coming his way, he went back to sleep.

I’ve blogged before about how I don’t count words when I’m writing. It’s true: I don’t — but I sure notice the word count when I’m revising.

I expect my early drafts to sprawl. Early drafts are my discovery phase. With nonfiction, I’m discovering what I know and think about a subject. With fiction, it’s discovering what my characters are up to. In Wolfie I’ve given them a puzzle to solve — several puzzles, in fact.

Some of the puzzles weren’t there at the beginning. They’ve appeared in the writing, and they’re turning out to be interrelated in interesting ways. This is also true of some characters. Shannon thought she’d left her alcoholic family far behind. I was as surprised as she was when her younger sister, Jackie, left a message on her answering machine.

I’m not much of a gardener, but I steal imagery from gardens all the time. Significant revelations sprouted in the second half of draft #2. In draft #3 I’ve worked their roots in earlier and let them grow in fresh soil. Those early clues have served their purpose, but now they’re superfluous. Zap zap zap.

Basil sproutlings

This is more like pruning, or pulling excess seedlings. I’ve been doing this on and off all month to my basil plants. I wish I had enough containers and a big enough garden to give all the little seedlings a good home, but I don’t, and if I don’t give a few of them room to grow there’ll be no pesto for me in September.

“Kill your darlings” is a writerly cliché — I think it means don’t get too attached to your lovely phrases, sentences, and paragraphs — but at this point I’m not having much trouble deciding what to keep and what to delete. This is a good sign. It means I’m focused more on the story and not so much on my precious prose. Sure, some of the phrases, sentences, and paragraphs are lovely, elegant, clever, whatever, but they’ve served their purpose. They’re history.

Sometimes, though, I hesitate: Is this sentence or paragraph or scene superfluous, or does it add something important to the story? Is this word really a better choice than that one? I take my hesitations seriously. In these cases, I track my changes in Word so I can reconsider them later. I flip back and forth between the revised version and its predecessor. I don’t have to decide — yet.

When I come back a few days later, the issue has usually resolved itself without my worrying about it. Time may be the self-editor’s most important ally.

I don’t have a target length limit in mind for this book. I want it to find its own best length, but I don’t want it to wind up as a doorstop either. So how do I know what’s essential and what’s peripheral? Wolfie is the story of a woman, a girl, and a dog. Each one of them has a backstory that could probably be a novel, or at least a novella, in itself. I need to know a lot of that backstory, but not all of it belongs in Wolfie. 

When Shannon’s sister Jackie showed up, though, I saw immediately that her story cast both light and shadows on Glory’s, and it helped show Shannon the way forward. At first the extended sequence where Shannon shows Jackie around Martha’s Vineyard (where Shannon and I both live, albeit on different planes) seemed like an extended detour from the real story, but as it took root and grew, I realized it wasn’t. In draft #3 I’ve been integrating it with the other main threads and watching it deepen and grow.

When I’m revising, my rational mind is wide awake and overseeing the process, but so much of revision is done by feel: I have a hunch, or I just know. Which makes it hard for the rational mind to explain, but I keep trying.

Say It Loud

“Synechdoche”?

My eye skidded to a halt. I knew it was wrong, I was 99% sure the correct spelling was “synecdoche,” but I looked it up anyway in Merriam-Webster’s Online. I was right: “synecdoche” it is.

Aside: Back in my newspaper days, I was frequently asked why I usually worked with a dictionary on my lap. “You spell better than any of us!” my colleagues would say. And I’d smile sagely or smugly depending on my mood and say, “This is why I spell better than any of you.” This was before and then in the earliest years of the World Wide Web: online dictionaries were not yet A Thing. Now I generally work with two or three dictionaries open in my browser at all times.

Then I clicked the little speaker symbol. I was stunned. Good thing I’ve rarely if ever had occasion to say “synecdoche” out loud, because I would have screwed it up. As a friend later pointed out, it’s like “Schenectady”: the stress falls on the second syllable. In my mind’s ear I’d been thinking something like “syn-ek-DOE-key.”

To this day I remember the moment when my first college roommate realized that the word she pronounced “epiTOME” and the word she spelled “epitome” were one and the same. It was the very epitome of an epiphany. I was grateful to be having my synecdoche epiphany in the privacy of my apartment.

However, once I was secure in my new knowledge, I immediately blurted it out on Facebook: “Lucky me, I was never called upon to pronounce ‘synecdoche.'”

I’m pretty shaky on my figures of speech, but I did remember that during April’s A to Z Challenge, blogger Eva Blasovic’s S had stood for “synecdoche,” so I hastened to her Beyond the Precipice blog to read up on it: “A figure of speech in which the part is made to represent the whole, or vice-versa.” Eva provides several good examples and also compares it to “metonymy” — which you’ll have no trouble pronouncing once you get the hang of “synecdoche” and “Schenectady.”

Applying my new knowledge, I immediately recognized my author’s use of “white-coats” as an example of synecdoche: he uses it to refer to research scientists who spend a lot of time in laboratories.

Moral of story: Look things up, even when you know the answer. Check the pronunciation as well as the spelling. It may save you from making a fool of yourself in public.