Ruth Wilson gave a scintillating presentation at last evening’s EAC-BC meeting about style sheets—an area, she says, that new editors often struggle with.
A style sheet is distinct from a publisher’s style guide (which applies to all of the publisher’s books) and is a list of words, terms, usages, etc., that the copy editor creates when working through a particular document. Ruth encourages editors to create a style sheet for every document they work on, no matter how short. Even a two-page pamphlet requires decisions about the serial comma, capitalization, and so on. We freelancers especially must rely on style sheets to keep ourselves organized, since we’re often working on several projects at once, each with its own set of style decisions.
Ruth suggests that as you put together your style sheet, keep in mind that it’s a form of communication with others in the editorial and production process. The proofreader will certainly use it, and the author, designer, and indexer may also look at it.
Style sheets can be an invaluable piece of archival material; it means that you, or another editor, won’t have to start from scratch if the document you’re working on has to be revised. As a freelancer, Ruth says, she keeps all of her style sheets. In corporate world, she’s often the one introducing all of the styles. Style sheets can serve as a building block for the organization to start developing its own style guide.
So what should a style sheet include? Two mandatory elements are (1) which dictionary you’re using and (2) which style manual you’re using—editions are important. Whether or not to use the serial comma is also almost always on the style sheet. Even if it’s in the organization’s style guide, it’s helpful to repeat that information, particularly if those who will be working with the document after you is not in house or is not focused on editorial issues.
The style sheet is basically a record of everything you’ve had to look up—proper nouns, titles of books, acronyms, and the like—and everything for which you’ve had to make a decision about
- spelling (words with more than one accepted spelling),
- capitalization,
- hyphenation (e.g., hyphenated compounds before and after nouns, hyphenation of noun forms but not corresponding verbs, etc.),
- pluralization,
- abbreviations (e.g., periods or not, small caps or full caps, etc.), and
- foreign words (e.g., accents/diacritics or not, italics or not, etc.).
Style sheets often include how numbers should be treated. When should they be spelled out and when should numerals be used? What date format is used? What units of measurement? Cookbook style sheets may also have a list of measurement abbreviations, conversions, and even standard sizes for pans and other kitchen equipment.
If the book has back matter, it’s often helpful for both you and the proofreader to include on the style sheet not just a description but a sample of a typical note and bibliographic entry to show how these should look.
Finally, any deviations from the norm or from the organization’s house style should be noted. An author may have a strong preference to spell or format a term a certain way that may not be what the dictionary or style manual recommends.
Once you put your style sheet together, proofread it. Make sure the word processor hasn’t autocorrected or autocapped your terms, and run a spell check. Date the style sheet, archive it for yourself, and pass it on.
What shouldn’t go on the style sheet? If there’s only one way to spell a word, don’t include it. “You don’t want to display your ignorance on a style sheet,” Ruth says. “It’s your job as copy editor to fix the spelling errors and typos.” She will usually list place names with difficult spellings but not, say, Paris or London—names that everyone knows how to spell. Also, says Ruth, list just the words and terms—there’s no need to write a story or justify the style decision you’ve made.
The sample style sheets that Ruth brought prompted some discussion about categorization. She referenced one of my earlier posts about style sheets, where I noted that proofreaders generally prefer an uncategorized word list. Eve Rickert chimed in to say that as a proofreader, she often finds that she’ll look for a term in one category on a style sheet, not find it, and look it up in anther source, only to discover that it had be listed under another category all along. When she receives a categorized style sheet, she simply removes the headings and consolidates the word list. Ruth explained that while editing, she finds it can be helpful to compartmentalize. I wondered if the preference had to do with workflow and where you choose to check your facts. If you have to check a list of place names, for example, against a specific authority (like the B.C. Geographical Names database), then it may help to separate out the terms into categories, but if you’re plugging everything—people’s names, place names, organization names, titles, etc.—into Google, then that kind of compartmentalization may not be necessary. Ultimately, Ruth says, it’s prudent to simply ask the publisher or client what they prefer.
An audience member asked if made-up words in a science fiction book, for example, should show up on a style sheet. To ensure consistency in spelling, says Ruth, absolutely. Another audience member asked if words deliberately misspelled to convey a character’s accent should be included. Ruth replied that, as a proofreader, she would certainly find that helpful, but the question morphed into a discussion about whether such misspellings were derogatory. Is it better to describe the accent but not misspell the dialogue? Would that be telling rather than showing? Not being a specialist in fiction, Ruth didn’t have a definitive answer, but it was interesting to hear the diversity of opinions on the issue.
Ruth ended the evening by showing us an example of a style sheet (created by Ann-Marie Metten) for a novel because she’d been asked what the difference was between fiction and nonfiction style sheets. The answer? Not much. You still have to make the same kinds of decisions.
The evening’s presentation and discussions showed that although all style sheets have some common elements, there is no one right way to compose them. However, as with all facets of editing, using your judgment is key to ensuring that the style sheets will be useful to you and everyone who will use them after you.
Can we just throw Dryer’s English at them and run?