Editing the editor: style sheets

It’s easy to understand how a book’s style sheet can fall off a copy editor’s priority list in the rush to meet a deadline—and how tempting it can be simply to alphabetize the word list and send it in. But I’d like to argue that editing a style sheet is just as important as creating it.

Indexers understand that up to half of the time spent indexing is devoted to editing the draft index—ensuring consistency in entry structure, eliminating wordiness and unnecessary entries and subentries, correcting spelling errors, etc.—to make the final product as useful as possible to the reader. An index and a book’s style sheet have a lot in common; in fact, the word list of a style sheet could almost be considered a most basic, preliminary proper noun index, without the page numbers, so it’s not surprising that a lot of the simple editing techniques for the index could also be applied to the style sheet to produce a more polished product.

But why bother? After all, doesn’t the style sheet have a very limited lifetime and an even more limited audience? To address this question, we’ll have to look at the style sheet’s end-users:

  • The author. I always include a copy of the style sheet when I send an edited manuscript to an author, because I feel that it’s foundational to good author relations. Not all authors will look at style sheets, but those that do read them carefully, and presenting a well-edited, consistent style sheet helps authors understand that you aren’t just making arbitrary changes to their text. Conversely, a poorly organized style sheet could potentially torpedo an attentive author’s confidence in his or her editor’s competence.
  • You—the copy editor. When the author returns the copy-edited manuscript, you’ll have to refer to and update the style sheet. Why not make it easier for yourself?
  • The proofreader. This person will undoubtedly use your style sheet the most. An inconsistent, disorganized, or contradictory style sheet can be an enormous source of frustration for a proofreader, as it leads to a lot of duplicated fact-checking work. Think about how a proofreader will use your word list, and refrain from the (indexing!) sin of overclassification: there’s no need to divide your lists into names of people, names of places, names of organizations, etc.; in such a case, the proofreader has to pause, decide what category a term falls under, then find it in an alphabetized sublist, whereas a single alphabetized list makes confirming a word or term simpler and easier. Even if you and perhaps the author find the classification helpful, a proofreader will probably prefer the single master list.
  • The indexer. As an indexer, I rarely import the style sheet directly into an index, but I do use it to double-check the spelling of my entries and confirm the style for the wording of headnotes and subentries. I’ll also look through the style sheet to ensure that I haven’t missed any important names or topics. (Importing the style sheet word list into an indexing program isn’t something I’m fundamentally opposed to—it’s just something I’ve never tried. For a proper noun index, doing something like this may significantly expedite the indexing process.)
  • Any member of the editorial team that may have to work on a new edition of the book, a spinoff, or a new book within the same series. Here is where a style sheet can have a much longer lifetime than just the production cycle of the book. Think about the editor who will have to use the style sheet when writing cover copy for a new format reprint or the editor who has to work on a revised edition. A well-organized style sheet can be a major time saver in these situations, where sometimes the fact that these books are “just revisions” means that they aren’t allotted much time in the schedule.

All of this is not to say that my style sheets are always (or ever) perfect. But I feel that at a minimum, a copy editor should do the following after alphabetizing the word list:

  • Go through the list and cull duplicate entries. This exercise not only eliminates redundancy, but it can also help identify missed inconsistencies and errors, particularly if you notice two distinct entries that you think ought to be the same.
  • Run a spell check. This process can be slow, since a style sheet is typically loaded with names that don’t appear in a word processor’s dictionary, but it’s helpful in identifying not only spelling errors within the style sheet itself but also in the manuscript, essentially forcing you to pause and double-check your fact checking.
  • Spot check a handful of entries against the manuscript. Using judgment, do global searches for a selection of style decisions, especially those that can have variants in spelling, hyphenation, or capitalization—and those entries that just look kind of funny and that you’d like to confirm.

Another strategy, given the similarities between style sheet word lists and indexes, that I haven’t yet attempted (and that non-indexer editors will probably not want to try), is to use indexing software to create and maintain the style sheet. In theory doing so would eliminate the duplicate-entry problem; facilitate cross-references within the word list; allow for special glyphs, such as initial punctuation, without throwing off the alphabetization; and may allow errors to be identified earlier on, since the word list can be sorted and resorted in a number of ways, including alphabetically and by order of entry, that may highlight inconsistencies. I’ll post about the experience if I ever have the chance to try this.

A hindering hierarchy?

All editors aspiring to work in book publishing know what it takes to climb up the ladder: start off checking inputting and possibly proofreading, and once you’ve proven yourself, you can progress to copy editing. Only after mastering that will more substantive work come and then, if so desired, experience with acquisition.

The advantages of this system are many. First, you get a well-rounded understanding of all steps in the editorial process. Second, by checking corrections and inputting, you get into the heads of more senior editors and learn the tricks of the trade. Third, you develop an appreciation for the roles of all editorial, design, and production team members—an empathy that will serve you well as a mentor or project manager overseeing the copy editing or proofreading work of a more junior editor.

But how valid is this tacit hierarchy? It implies that acquiring and substantive editors are somehow better than copy editors, who themselves have a leg up on proofreaders. This stratification has real consequences: freelance proofreaders typically charge lower rates than copy editors, and substantive editors command the most. Editorial recognition like the Editors’ Association of Canada’s annual Tom Fairley Award for Editorial Excellence generally (by which I mean the overwhelming majority of the time) goes to a substantive editor rather than a copy editor or proofreader.

Although I would agree that no amount of proofreading will ever salvage a poorly structured and awkwardly written piece, I am concerned about the limitations of this rather firmly entrenched paradigm. The fact is that proofreading, copy editing, and substantive editing (the EAC goes as far as to split up the latter into stylistic editing and structural editing) each requires its own unique skill set. Whereas some editors work well with the big-picture stuff, others are adept at the details, and it’s time to stop seeing those editors who devote themselves to copy editing as failed substantive editors. And publishers that adopt this classic “substantive reigns supreme” model may miss out on hiring someone who hasn’t yet “proven herself” at copy editing but may be an astute developmental and structural editor.

One could argue that those who wish to focus on a specific skill would be better off as freelancers and that in-house positions are better suited to generalists who are willing to learn all facets of the editorial—and publishing—process. Many freelancers eschew the hierarchy by charging a flat rate regardless of the type of work they do. And those who hope to do substantive work without having to first perfect proofreading may have better luck finding opportunities at smaller presses, where, owing to a lack of human resources, structural and stylistic editing can often be assigned to whomever is available.

I, for one, am grateful that I did get the opportunity to learn the ins and outs of editing from the ground up. But to me, the ground doesn’t correspond to checking inputting or proofreading—it corresponds to a solid foundation of amazing mentors, high standards, and a drive to keep learning and improving, no matter what kind of editing I’m doing.

Fact and nonfiction

At a recent editorial retreat, a very experienced editor was telling us about how clients sometimes question why the research for a single piece of information can take what seems like an unreasonable amount of time. “The author had provided a photo of a bridge he wanted to use and a caption for it. I searched the name in the caption, found a photo, and it was the wrong bridge. So I looked at maps of where this bridge was supposed to be and tried to find pictures of landmarks close to it…” She ran into one dead end after another, until finally, after hours of searching, she found another photo of the bridge from a different angle, and a name to go with it. “That’s the bridge. So I changed the caption, but finding the right name took the whole day.”

“What would you have done before the Internet?” another editor asked.

“Nothing. There would have been an error in the printed book.”

That conversation made me think quite a bit about the accuracy of sources we consider reliable and this whole business of fact checking in the editorial process. Editors—copy editors in particular—are expected to check facts within the realm of general knowledge; with Google, though, more and more can be considered to be part of that realm. Does this mean that more of the onus of fact checking falls on the editor rather than the author? Much has been said about the unreliability of online information, but are print sources really any better? Didn’t the past lack of Internet search engines just mean that copy editors of yore simply couldn’t spend the time to track down primary sources of information? I can think of two projects I worked on over the past year that were new editions of print-only books, where authors used the old edition as a basis for the new book and my Internet searches revealed errors in their earlier text. I can only imagine that this now happens all the time, meaning that books, if they are properly fact checked, are probably more reliable than they have ever been.

The flip side, of course, is that there such a deluge of new titles being produced now, especially since anyone can self-publish, that the majority of books can’t possibly be thoroughly vetted. And, of course, the Internet is not without its pitfalls. When I come across a term that’s not in my dictionary or a name that doesn’t appear in the Library of Congress Authorities, I do lean on Google to tell me that one spelling gives me 200,000 hits, whereas an alternative spelling gives me 1,200. And those 1,200 may very well be right, but often in those cases, “truthiness” prevails.

I sometimes feel that fact checking is more for the editors’ benefit than the authors’. Oh sure, we’re saving authors from potential embarrassment, discredit, and maybe, in the case of a misquote, a libel suit. But when we go to great lengths to hunt down the exact punctuation and capitalization of a sixteenth-century title that some ship’s second officer put together from his journal, and we end up finding a scanned copy of the original text in an online archive, it’s all about the satisfaction of sleuthing and getting it right. Maybe the reason fact checking can be particularly satisfying is that it’s so much less subjective than other facets of editing; in most cases, the goal is finding the one right answer, not, say, imposing a style decision. The hunt does take time, though, so I suppose we’ll have to subtly tease out of our authors what standard they expect us to uphold for each project. Does this author want me to spend the afternoon tracking down and watching a YouTube video of a lengthy speech to see if he’s accurately quoted a public figure? Or should I trust his research and simply alert him to the risk of misquoting?

Ultimately, even if we editors flag factual errors, authors are free to reject our suggested changes, and in the end our efforts may not matter. Most people still believe, for instance, that Marie Antoinette said, “Let them eat cake” (she didn’t) and that Philip Sheridan said, “The only good Indian is a dead Indian” (a misquote, if he uttered anything like it at all), showing that even for the most persuasive of editors, the reader’s interpretation is beyond her control.

Purgative roundup

I’d been vacillating about adding a blog component to this site, primarily concerned that my personal musings had no place in my business. But September’s Editors’ Association of Canada BC Branch meeting, which began as a showcase of portfolios and quickly morphed into a discussion about online marketing opportunities, convinced me that maybe blogging wasn’t such a bad idea after all.

Since this post is my first, and I’ve got a backlog of news, let me dive in. In no particular order:

1) After a long wait, Cow (Greystone Books), written by Florian Werner and translated from German by Doris Ecker, has finally been released. A million thanks to the amazing Temple Grandin for providing the foreword to this cultural history of the cow.

A massive part of my work on that book involved picture research—seeking out public-domain images whenever possible, tracking down image copyright holders, negotiating permission fees, and the like. At the September EAC meeting, I was lucky enough to win a free EAC seminar and am looking forward to the April 12 Picture Research seminar by Mary Rose MacLachlan and Derek Capitaine (MRM Associates).

2) D&M Publishers celebrated its fortieth anniversary with a party at the Vancouver International Writers Festival. In addition to seeing my old D&M colleagues, I got caught up with Jesse Marchand and Michelle Furbacher from Whitecap Books (friends from my old Ubyssey days!); Megan Brand of UBC Press; Ann-Marie Metten of Talonbooks; and fabulous freelancers Grace Yaginuma, Lara Kordic, and Stephanie MacDonald.

3) I’m excited to attend an advance screening on November 2 of a Fred Herzog documentary for the Knowledge Network, which will also be the launch of Fred Herzog: Photographs, an incredible privilege to work on. I’ll post the air dates of the documentary when I find out what they are.

4) This snort-inducing article about Mary Walsh as Marg Delahunty intimidating Toronto Mayor Rob Ford into calling 911 reminded me of the actress’s contribution to Shari Graydon’s terrific collection, I Feel Great about My Hands—a celebration of the unexpected benefits of aging. To keep up with Shari, read her blog here.