Derek Hayes wins inaugural Basil Stuart-Stubbs Prize

Congratulations to Derek Hayes, whose British Columbia: A New Historical Atlas has picked up yet another honour! Hayes’s visually stunning opus has won the Basil Stuart-Stubbs Prize for Outstanding Scholarly Book on British Columbia, a new award from UBC Library and the Pacific BookWorld News Society. More details here.

Ethics for editors—with Mary Schendlinger

Mary Schendlinger, senior editor at Geist and faculty member in SFU’s Master of Publishing Program, led an eye-opening and thought-provoking half-day EAC-BC seminar about ethical issues in editing. When we edit and publish, she said, we are mediating culture and knowledge—a big responsibility. Most of us get into this field to make a better world, but we also work in a business, and many of the ethical questions we face arise from having to balance the needs of a publication’s many stakeholders. As we saw through the seminar, these questions often don’t have black or white answers, but an ethical editor is one who recognizes an ethical question when it comes up and who thinks constantly about who is affected by her decisions and recommendations.

Schendlinger divided ethical considerations for editors into six broad categories:

  • Responsibility to the earth
  • Responsibility to the profession
  • Responsibility to writers and artists
  • Responsibility to confidential sources
  • Responsibility to other stakeholders
  • Responsibility to society

Responsibility to the earth

How can we editors reduce the impact of our work on the environment? Schendlinger admitted she feels pangs of guilt each time she prints out a hard copy to edit or proofread but that she often works better that way. We can mitigate our effects on the environment by reducing, reusing, and recycling, of course, but it’s also important for us to voice our opinions about using printers and suppliers that actively support environmentally friendly initiatives, for example.

Schendlinger also raised the issue of the carbon footprint of online activities. Although we’re inclined to believe that working on computer is more environmentally responsible than working on hard copy, Schendlinger pointed out that two Google searches produces the same amount of carbon emissions as boiling a cup of water, so those of us working digitally aren’t as green as we might think.

(Not discussed at the seminar but pertinent to this topic is the ability of editorial quality-control systems to keep waste to a minimum. Discovering a mistake that must be corrected too late in the production process could mean that an entire printing of a publication has to be pulped. Systematically using editorial checklists and carefully checking galleys and printer’s proofs can help you see those problems before they’ve been committed to hundreds or thousands of paper copies.)

Responsibility to the profession

Schendlinger gave us several scenarios to discuss, relating to how we participate in our industry and how we treat staff, colleagues, clients, subcontractors, and suppliers. For example, what do you do when a client asks for your opinion of a fellow editor whose work you think is subpar? What do you do if you, as a copy editor, discover several problems left unresolved by the substantive editor? Is it acceptable to charge a fee to a colleague to whom you’ve referred a client? Do you tell a client if you subcontract a project to another editor?

Schendlinger advocated honesty, integrity, and transparency in all cases. Always assume competence on the part of your colleagues and give them the benefit of the doubt. Be diplomatic and tactful, but always convey your honest opinion, keep your promises, and do your best to avoid conflicts of interest.

Responsibility to writers and artists

How do we talk to an author about what we do? Schendlinger cautions against using negative language that we may be so accustomed to that they seem standard: “cleaning up a manuscript,” “correcting errors,” “resolving problems.” Instead, she recommends something along the lines of, “making the language more appropriate to the situation,” emphasizing that for every project we have to keep in mind audience, purpose, and occasion.

That triad is the reason Schendlinger does not recommend editing a manuscript pre-publication or pre-agent. She said she’s seen a number of authors get burned by having paid an editor to work on their manuscript only to have to start from scratch when a publisher or agent picks it up and has a different vision for the work. Copy editing is fine, she said, but she discouraged doing any kind of developmental or structural editing.

Schendlinger then asked, is it okay to go the wall arguing a point of grammar or syntax that you know is right? She pointed to Amy Einsohn’s The Copyeditor’s Handbook, in which Einsohn noted that if you do argue, make sure you’re doing it for the right reasons and not for ego. Make it clear that you’re motivated by wanting to maintain the author’s credibility in the eyes of readers.

Finally, we discussed the case of Gordon Lish’s work on Raymond Carver’s books, as documented in this New Yorker article. We all agreed that Lish was overstepping in the way he altered the author’s voice. Schendlinger pointed out that Carver was dependent on Lish to have his books published—and thus to earn his income. As editors, we are often called upon by publishers to offer our opinion, and that puts us in a position of power; it’s important that we don’t abuse it.

Responsibility to confidential sources

Editor–author relationships can be very intimate, Schendlinger noted. Authors may confide in you or tell you things that they expect you to keep confidential. Keep your promises, both explicit and implicit, and protect confidential sources and information.

Responsibility to other stakeholders

We know that as editors we have to mediate between author, publisher, and reader. Who else might have a stake in a written work?

  • printers and other suppliers
  • designers
  • photographers and illustrators
  • production managers
  • advertisers or sponsors
  • sales and marketing reps
  • booksellers, retailers, and e-tailers
  • libraries
  • people in the media
  • private or public investors
  • researchers
  • people named in the work
  • future artists who might create a derivative work

The list of stakeholders is long and not necessarily predictable. We have a responsibility to all of them, to varying degrees.

Editors have to keep an eye out for plagiarism, libel or potential libel, invasion of privacy, and obscenity, among others issues. Schendlinger emphasized the need to be careful and tactful when approaching authors about these issues; for example, plagiarism isn’t necessarily malicious or even intentional. Quoting from Oliver Sacks’s “Speak, Memory” in The New York Review of Books, Schendlinger demonstrated how malleable memory can be and how easily an author can internalize another writer’s work and regurgitate it as his or her own. It’s important to approach these cases sympathetically, said Schendlinger, never accusingly.

When advertisers or sponsors are stakeholders in a publication, ad–edit boundaries become concerns for the editor. Organizations such as Magazines Canada have issued guidelines (PDF)  based on principles of editorial integrity that deal with issues such as adjacency and proximity (where ads are placed relative to content) and how pieces such as advertorials are labelled.

Responsibility to society

Writing not only reflects society; it also shapes it. We have a responsibility to the public record: we need to do our best to check facts and to ensure that biases and stereotypes don’t get perpetuated. She led us through an exercise to identify problematic language such as

  • non-parallel references that give unequal status to people who should be equal
  • unnecessary categorization of people
  • negative connotation of illness
  • stereotypes based on gender, sexual orientation, social status

and to suggest fixes.

Finally, we discussed the fuzzy boundaries of truth in creative nonfiction. After all, we never remember something exactly the way it happened, and different people remember events in different ways. Schendlinger noted that readers approach nonfiction differently, because knowing that something actually happened to someone makes that story more compelling. How far can we push creativity and still bill a work as nonfiction? Is it okay to change people’s names? Is it okay to combine several different people into a single character? Is it okay to change the order of events? No easy answers, but Schendlinger pointed us to John D’Agata and Jim Fingal’s book, The Lifespan of a Fact, for guidance.

***

Schendlinger’s seminar was incredibly illuminating, although I have to admit that I left not only with more questions than I had going in but also with a new sense of paranoia that I’ll miss an ethical problem or make the wrong call in my work. The main takeaway—and this might sound trite and simplistic—is to be professional:  keep your promises, be honest and transparent, and flag problems early.

Ethical issues are a tricky but unavoidable facet of our work. I’ve always maintained that you can excel at the mechanics of editing—even fulfilling all of EAC’s Professional Editorial Standards—but may still be unethical, which reflects poorly on the profession. As Schendlinger pointed out repeatedly, sometimes we err not because we want to but simply because we don’t know any better, which is why I would eventually like to see an organization like EAC develop a code of ethics, if only to educate and inform. I understand that the association currently doesn’t have the resources to police a code of ethics, but having an aspirational document would still provide us some guidance and move us toward becoming a genuine profession. Until then, we can learn so much from one another: if Schendlinger offers this seminar again, I’d wholeheartedly recommend it for all editors, no matter your level of experience.

What does your markup say about you?

This interview also appears on The Editors’ Weekly, the Editors’ Association of Canada’s official blog.

***

A friend of mine was venting to me about his old boss, who used to look over his reports. Whenever his boss found an error, he’d not only circle it but also emphasize his discovery with an exclamation point—a practice that drove my buddy nuts. Encoded within this tiny mark of punctuation was his micromanaging boss’s chiding disapproval: “HEY! THERE’S A MISTAKE RIGHT HERE! WHAT’S WRONG WITH YOU?”

I was relating this story to my good friend Naomi MacDougall, an award-winning designer, and she told me she once had to work with a proofreader whose markup she found “overly aggressive.” We both had a good laugh about that, but the conversation got me thinking: Whereas most of us have switched to editing on screen, a lot of us still proof on hard copy, and our markup is often the only communication we have with a designer, whom we may not know and may never meet. It’s a bit of a weird working relationship—more distant than others in the publication production chain. How can we be sure that our markup isn’t inadvertently pissing off the designer? I asked Naomi to sit down for an interview to talk about some of these issues.

IC: When you mentioned that a proofreader you’d worked with had “overly aggressive markup,” what did you mean by that? What did the proofreader do that rubbed you the wrong way?

NM: Mostly it was the use of all caps and lots of exclamation points at the end of every note. It made me feel as though I was being yelled at. The tone of the markup put me on the defensive.

IC: Are there other things proofreaders have done that you wish they wouldn’t do?

NM: There have been times when the markup hasn’t been clear, and obviously that’s tricky. It’s frustrating to have to sit there and puzzle over what a letter is. Also, occasionally, I feel like the markup has left too much for interpretation. Because we’re often going through these changes quickly, I don’t want to have to be deciphering code.

On the flip side, if something is very obvious in the markup—like if a letter is dropped or a word inserted into a sentence—then you don’t have to spell it out again by rewriting the sentence in the margin. But when there are lots of moving words and punctuation marks in a sentence, it’s really helpful if the proofreader rewrites the sentence in the margin.

I guess what I’m trying to say is that I’d like as much clarity as possible in markup. I’m intelligent, but I’m not a mind reader.

IC: When there’s a problem like a bad break or a widow, would you prefer that the proofreader just point out the problem so that you can find a solution, or would you rather the proofreader suggest a fix?

NM: That’s a good question. In most cases I would say just point out the problem, unless it’s obvious it’s going to be very tricky to fix—then it’s hugely appreciated when the proofreader suggests a fix, especially if it involves cutting or inserting words.

IC: What’s your preference when there are more extensive passages of text that need to be inserted? How long would an insert have to be before it’s better to send you new text in an email rather than writing it in the margin for you to rekey?

NM: I would say I’d want new text for anything longer than one sentence or two short sentences. There’s just more room for error when I have to type a bunch of text. And if you’re moving more than, say, four words around in a sentence, just rewrite the sentence and have me retype it. It takes less time than moving all those words around and making sure they’re all in the right place.

IC: I think you were telling me earlier that different proofreaders approach word substitutions differently. Some mark a word as deleted and then add a caret to show that a word in the margin should be inserted, whereas others just cross out the word in the proof and write its replacement in the margin, without the caret.

NM: Yes, I like the caret. I find it clearer.

IC: It’s a visual cue for the designer to look in the margin.

NM: Exactly. It takes out that second of guesswork.

IC: Which can really add up!

NM: Yes!

IC: Is there anything else proofreaders do that you really appreciate?

NM: I always appreciate a neat printer, and I always appreciate it when a proofreader uses a bright ink, like red or purple or anything that stands out against the type. Often I’m scanning a page quickly, and if the markup is in pencil or black or blue pen, I tend to miss more of the changes. They don’t jump off the page as easily, so I have to take more time to look at each page closely.

Also, I really appreciate it when the proofreader suggests a global change at the beginning of document if a word is misspelled throughout. It’s so much quicker for me to search and replace these in one go. But I also like it when these words are highlighted in the text so that I can double-check that the change was made and check for reflow, since, during a global change, there’s always the potential for a line to break differently.

IC: Do you ever return communication on the proofs? What kinds of things to you say to the proofreader?

NM: Not often, but if I do it’s almost always a note that a change can’t be made because of reflow issues—mostly to do with hyphenation. And occasionally I’ll make note of a design style that overrules a type change.

IC: We’ve focused on hard-copy markup so far. Any thoughts about proofreaders working on PDF?

NM: I know in some instances I’ve missed smaller fixes in PDFs, like a change to one letter or a punctuation change, because they’ll just show up as tiny, tiny marks, and they’re easy to miss even in the full list of changes. If you click on the markup and add a short comment to it, though, it pops up as a little box, so it jumps out.

PDFs are great for shorter publications; I can copy and paste the text right out of the markup boxes, so that makes my life easy! But for a big book, hard copy is preferable. Having to go back and forth between windows on the computer is the issue.

IC: How much does it annoy designers when we make a change on first proofs and reverse it on second?

NM: It’s not usually a big deal—unless it’s a complete change from Canadian to U.S. spelling throughout, say. If that ping-pongs, then it can get annoying—though I’m sure it is for everyone involved! In that case a note about global changes is hugely appreciated.

IC: What can a proofreader do to ensure that the relationship with the designer is as collegial and productive as it can be, given that it’s such a bizarre, arms-length interaction?

NM: If markup is done professionally, then the relationship will be smooth. Just be clear, be thorough, and print neatly… and no all-caps yelling!

IC: Yes! I think those are all of my questions. Do you have anything to add?

NM: Just that I appreciate how much work goes into a thorough proofread, and I don’t know how you all do it! Sometimes your hawk eyes blow my mind!

Upcoming editing and publishing events

A lot is happening over this next week! I hope to be posting about all of these editing- and publishing-related events—though probably not all at once. Look for my summaries over the next few weeks.

1. Ethics for editors

Having been a member of the Editors’ Association of Canada’s code of ethics task force about a year and a half ago, I’m very interested to hear what Mary Schendlinger will have to say about ethical dimensions of editing at her EAC-BC seminar on Saturday. At our January EAC-BC meeting, David Harrison and some members of his audience had discussed whether a code of ethics was the only piece of the puzzle we were missing before we could consider editing a bona fide profession. Schendlinger will tackle such issues as how creative a piece of creative non-fiction can be and how best to navigate a situation in which an author has used racist or sexist language.

Registration for this seminar is closed, but if you can’t attend and have some ethics-related questions about editing, get in touch with me, and I’d be happy to take them to the session and bring back whatever answers I can get.

2. Plain language certification

Katherine McManus, director of the SFU Writing and Communications Program, will speak at our March EAC-BC meeting about SFU’s role in the project by IC Clear, the International Consortium for Clear Communication, to launch certification in clear communication and plain language. McManus will also give us a preview of the upcoming PLAIN 2013 conference in October, where IC Clear hopes to pilot its first course. Join us on Wednesday, March 20, at 7pm, at the YWCA on Hornby.

3. Robert R. Reid Award and Medal to Will Rueter

The Alcuin Society will present its Robert R. Reid Award and Medal for lifetime achievement in the book arts to William Rueter of Aliquando Press on Thursday, March 21. At the free event, which starts at 7:30pm at SFU Harbour Centre,  Rollin Milroy of Heavenly Monkey will interview Rueter and show illustrations of Rueter’s work.

Editing books in translation

Yesterday I gave a talk at the EAC-BC meeting about editing books in translation, and I was buoyed by the thought-provoking discussions that came out of the audience, which was packed with expertise. Here’s a short summary of my presentation.

Why translations?

Unlike a piece of visual art, which virtually anyone can see and appreciate, a book has an audience limited to those who understand the language in which it’s written. When you work on a translation, you’re bringing a work of art, a point of view, or a piece of knowledge to a much broader audience than it previously had—a pretty powerful idea, when you think about it. Canadian historian of translation Louis Kelly declared that “Western Europe owes its civilization to translators,” and although that statement may seem grandiose, the Protestant Reformation and the Renaissance wouldn’t have played out the way they did if the Bible and classical Greek and Latin texts hadn’t been translated into the vernacular.

On a more practical level, publishers like translations because, in a way, they mitigate a bit of the risk of cultural production. If you know that the source text has done well in its native territory and your target audience has a comparable culture, there’s a decent chance the translation may also do well. (On the flip side, publishers have to contend with the notion—whether it’s real or merely perceived—that the reading public is loath to buy translations.) Publishers also like translations because they’re often subsidized. Grants from the Canada Council for the Arts or from other funding bodies are available to offset the cost of producing translations for certain kinds of books (eligibility criteria vary depending on the type of program).

If you’re an editor, translations are a great way to cut your teeth: with the odd exception, they involve no structural editing, and most of the work is copy editing, with a bit of stylistic editing. You also get to work with translators, who, because they are language professionals like you, understand the role of the editor and often come into the working relationship with an eagerness to start a dialogue about the text. Many translators are also editors (in fact, I often like to think about stylistic editing as translating from English to English), and because both parties are, in a sense, working with what one translator called “borrowed words,” the relationship can be really collaborative and dynamic. You would normally be working with a translator who’s translating from the source language into his or her mother tongue, so, even if you don’t know the source language, there’s no language barrier to worry about.

Copyright and contracts

As the editor of a book in translation, you have to be aware of three different contracts:

  • the contract for the translation rights
  • the contract with the translator
  • the agreement with the funding body

The contract for the translation rights is usually between the publisher of the translation and the publisher of the original text, although occasionally it’s between the publisher of the translation and the author. An author has to authorize a translation before it can be published, and the translation rights have to be assigned to the publisher—this contract typically serves both of these functions. For an illustrated book, those rights may or may not include image rights. This contract may also specify an approval process for the translation, as well as the format of the copyright notice on the translation’s copyright page.

The contract with the translator defines the scope of the translator’s work—any tasks that fall beyond that scope (e.g., translating praise quotes for marketing copy) may mean the publisher has to pay extra—as well as project timelines. This contract will also specify how the translator will be credited. (Because a publisher will often try to downplay the fact that a translation is a translation, the translator’s name may not have to appear on the cover but would appear on the title and copyright pages.)

The agreement with the funding body, whether it’s the Canada Council or a foreign organization, such as the Goethe-Institut or China Book International or NORLA (Norwegian Literature Abroad), will usually include the exact wording of an acknowledgement clause, and possibly a logo, that must appear in the published translation. If you fail to include this clause, the publisher may lose its translation funding.

A publisher might not allow you to see these contracts directly, but you should know to ask for these specific pieces of information so that you can complete the project properly. Any tasks that these agreements don’t cover—for example, clearing image rights or handling text permissions—may fall to you as the book’s editor. The publisher may also ask you to approach well-known people to write a foreword or cover blurb for the book.

Working with a translated manuscript

When you receive the finished manuscript from the translator, the only structural work you’d be expected to do is a quick concordance check to make sure that all of the paragraphs in the original appear in the translation. Otherwise, you’re mostly copy editing, although you’ll want to offer stylistic suggestions when something in the translation doesn’t sound quite right.

You don’t have to know the source language to edit a translation, although, in my experience, having some experience with the source language can help you know what to look out for (and, as we’ll see later, can help you land work), including problems such as false cognates. Also pay attention to idioms that don’t work in the target language; you may have to suggest different idioms that convey the same concept. Prepositions are by far the most idiomatic part of speech, so if a sentence sounds a little off, check the prepositions to see if the appropriate ones have been used. When a translator is switching back and forth between languages, it’s really easy to use a preposition that works for the source but not for the target language. Finally, punctuation is treated differently in different languages, so be sure that the punctuation in the manuscript is appropriate to the target language.

As you would for any manuscript, keep an eye out for quoted passages that may require permission to reproduce. Text permissions in translations are an especially tricky issue, because they can be multilayered—for example, even if a passage in the source text is in the public domain, the translation of the passage in the target language may still be under copyright. Avoid what the Chicago Manual of Style calls “the sin of retranslation”—if the quote in the source text had been translated from the target language, the translator must track down the original quote rather than translating it anew.

Always ask the publisher for a copy of the source text. Not only do you need to do an initial concordance check, but you’ll want to be able to refer to the source if you run into passages in the translation that sound strange or awkward because of possible homonym confusion. Tools such as source language–target language dictionaries, and terminology databases like Termium can come in handy in those situations. (Of course, you’d never send a whole novel through Google Translate, but the tool can be useful for interpreting one or two problematic sentences as a starting point to a discussion with the translator.)

Other translation-related issues that you often hear about—including whether the translation should be literal or free, whether a translator should define unfamiliar terms with footnotes or glosses, how to approach culturally sensitive topics—are usually, if you’re working with an experienced professional translator, within the translator’s domain. You should absolutely be aware of these issues, since the translator may look to you for discussion or advice, but in many cases you won’t be expected to play too hands-on a role. With a less experienced editor, however, you may be called on to offer more input on these matters.

Finding work as an editor of translations

If you’re interested in editing books in translations, start, as you would for any kind of book editing, with a query letter to a publisher, but specify your interest in translations. (Of course, it helps to know someone on the inside, which is why it’s important to build relationships with publishers in other ways.) You can check the Canada Council website for a list of translation grants that have been awarded to find out which publishers in the country publish translations. Try also to build relationships with translators—such as members of the Literary Translators’ Association of Canada—because a translator who knows you and trusts your work may recommend you to his or her publisher.

If you know a second language, you can offer your services as a reader. Publishers return from the London Book Fair in the spring and the Frankfurt Book Fair in the fall with boxes of books in languages they may not know how to read; they’ll offer readers a fee to read and evaluate whether translations of these books might be good fits on their lists. If you identify a promising project and the publisher goes ahead with it, you’d be a natural choice to edit it.

Do a bit of research into funding programs for translations that are available outside of Canada. Many countries are eager to export their literature and have ministries of culture or associated organizations that subsidize foreign translations. If you approach a publisher right before a book fair with the pitch that you’re available as a reader, you’ve built connections with several literary translators, and you’re aware of a specific funding body that might subsidize the cost of a translation, that’s a pretty compelling package.

When evaluating books as a reader, consider the following:

Does it fit on the publisher’s list?

This point may seem obvious, but it can be tempting to recommend a book project even if it’s not a good fit just so that you’ll get to work on it. Doing so would only sabotage your credibility with the publisher.

How much localization does the work need?

Would the book need to be changed in any way to be comprehensible to the translation’s readership? Would the book benefit from a foreword?

How long will the translation be?

French texts are about 20% longer than English texts, and Spanish about 25% longer than English. if the original is short to begin with, will a translation be too slight to publish? Length is less of a concern for ebooks but is definitely a consideration for print books.

Are there image or text permissions to worry about?

Flag these for the publisher, because they may add to the schedule or to the budget, and they may affect how the publisher approaches the contract for translation rights.

For illustrated books, is there reverse type?

If the publisher of the translation hopes to use the same printer as the originating publisher, reverse type means added production costs: rather than replacing just the black plate, the printer would have to replace all four CMYK plates. Flag instances of reverse type so that the publisher is at least aware of them.

Further resources

If you’d like to learn more about the world of books in translation, I highly recommend Translators on Translating by Andrew Wilson and Why Translation Matters by Edith Grossman. You may also find resources on the websites of the Literary Translators’ Association of Canada, the Canadian Translators, Terminologists and Interpreters Council, the Society of Translators and Interpreters of British Columbia, and similar groups in other provinces.

February EAC-BC meeting

A week from today, on Wednesday, February 20, I’ll be giving a talk at the EAC-BC meeting about editing books in translation. I’ll talk about copyright, the editor–translator relationship, special issues in translation projects, and strategies for getting work as an editor of translations. I’ll also be giving away a couple of books that I’ve recently reviewed: Science in Print and Book Was There. Come join us (but leave all of your tough questions at home)!

There’s a pre-meeting pay-as-you-go dinner:

Elephant & Castle
385 Burrard Street (Marine Building)
5:00pm–6:45pm
RSVP here by the end of the day Monday, February 18

followed by the meeting at the usual location:

YWCA
535 Hornby Street, fourth floor
7:00pm–9:00pm

I start blathering at 7:30pm.

For those of you who can’t make it but still care, I’ll post a summary of my talk here by the end of next week.