Category: Books

Maps: type style and citations

As a book editor, I’ve learned to rely pretty heavily on the dependable Chicago Manual of Style. Once in a while, though, I run into an esoteric subject that Chicago just doesn’t cover well. Maps—both in terms of working with a cartographer to create a map and in terms of citing old maps—are one such subject, and they deserve special attention because they have both visual and textual considerations and because they can serve a wide spectrum of functions: in some books they give geographical context by telling readers the locations of unfamiliar places, whereas in others, like guidebooks, they can be critical navigational tools.

In my early days at D&M, one of the more senior editors asked me to copy edit some map labels to be sent to a mapmaker. “So just make sure that the formatting is correct,” she told me. “For instance, bodies of water should be in italics—you know that, right?”

I didn’t, at the time, and a few years later, when I was putting together an editorial wiki for the company, which included our style guidelines, I wanted to add a section specifically about maps. I pored through Chicago and searched online but couldn’t find a particular authoritative source that stated the bodies of water = italics convention. I ended up listing it as a house style but never stopped wondering where that came from.

Recently I sent the question to the Canadian Cartographic Association, and the president, Gerald Stark, a cartographer for the Government of Alberta, not only wrote me an incredibly thorough response of his own but also forwarded my query to the CCA membership. Below is a summary of some of the members’ contributions to the discussion.

Type considerations on new maps

Writes David Forrest, senior lecturer at the School of Geographical and Earth Sciences at the University of Glasgow:

In terms of map design generally, there are no definitive specifications that must be followed, except in a few specific cases such as hydrographic charts. Some map topics, such as topographic and geological maps, have developed “conventions” over the years, but these need not be slavishly followed, and topographic maps, even at the same scale, vary greatly around the world.

The use of italic for water names is such a convention, but you can find many maps which don’t. The main thing is that variations in letterform are used to enhance the classification of features on the map. Labelling everything in the same typeface is generally poor, but it does depend on the individual map, the number (and density) of names and what the map is for.

In a book the important thing would be to have a consistent approach throughout—much like most atlases do—but the choice of type styles may depend on whether one is trying to give the map a modern look or an historical look, for example.

On another point, in the caption for historical map illustrations, one thing really useful, but often absent, is a note of the size of the original, or the % reduction (e.g. shown 55% of original), as scale is one of the most critical factors in map design.

Henry Castner, author of Seeking New Horizons: A Perceptual Approach to Geographic Education and editor of A History of the Cartography of Russia up to 1800, writes:

In book editing, I suspect most of your maps are unique special-purpose and thematic maps for which the purpose of the map overrides some perceived need for design consistency. So depending on the purpose for labelling the water area(s), for example, it may be that large bold letters are required in one case, and small inconspicuous ones in another. In other words, an editor has much greater freedom in designing special-purpose and thematic maps as long as attention is given to the visual tasks involved and the role each map element plays in their execution. The worst sin in map designs in books, in my experience, are maps that don’t locate the places mentioned in the narrative.

So there you have it. Typographic considerations for a map depend on the map’s purpose in the book and the need for consistency within a book. If you are a publisher that works frequently with mapmakers, defining a house style for type on maps may be the way to go.

That said, if you need a place to start, check out the conventions used by national topographic mapping bodies. Gerald Stark writes:

Most national mapping programs have well-established standards for map design (e.g., United States Geological Survey; Natural Resources Canada—National Topographic Series; Ordnance Survey of the U.K.). Maps produced by these agencies do provide guidelines for producing topographic maps.

Of particular interest is a link Stark gave me to the Atlas of Canada discussing type design on maps.

For further information about map design in general, Stark recommended several books; since they’re not specific to type style on maps, I won’t include them here, but if you’re interested, get in touch with me, and I would be happy to pass along his list.

I don’t know that I agree with David Forrest’s assertion that a map’s scale of reduction is absolutely necessary to state in a citation—again, because maps serve different functions when reproduced in a book. If a map is included purely for illustration and not for navigation, an indication of a map’s reduction may be interesting to a cartographer but not needed for the general reader. Which segues beautifully to…

Citing maps

Another area that Chicago doesn’t discuss in detail is map citation. Although in many cases they can be considered art or photography and may be cited as such, their inherently informative nature usually demands more bibliographic detail, especially if the work in which they appear is meant to serve as a reference.

My query to the Canadian Cartographic Association and to the David Rumsey Historical Map Association about proper map citations brought back a number of online guides, all of which pretty well cover print and digital maps:

Alberta Wood of the Association of Canadian Map Libraries and Archives also generously shared with me a draft of best practices in map citation; when her document has been formally approved, it will be posted on the ACMLA site.

The CCA members also recommended two print guides. The first is

Kollen, Christine, Wangyal Shawa, and Mary Larsgaard. Cartographic Citations: A Style Guide, Second edition. Chicago: Map and Geography Round Table, American Library Association, 2010.

It’s a thirty-two page handbook covering everything from manuscript maps, single-sheet maps, and atlases to remote-sensing imagery and computer spatial-data files. I found a copy at the UBC library; it’s comprehensive and easy to use, and it has a helpful glossary defining cartographic terms. Its raison d’être is clear from its introduction: “The majority of general citation guides and style manuals either do not include any information on cartographic materials or only provide guidance on how to cite a single stand-alone map or as figures in an article or book.” It is meant as a supplement to standard style and citation guides. You can buy it here for $20, but given its very specialized focus, I would say that it’s worth the investment only if you know you’ll be working with cartographic citation frequently. For most purposes, the online guides are as much information as you need.

The other recommended print guide is

Mangan, Elizabeth U., ed. Cartographic Materials: A Manual of Interpretation for AACR2, Second edition. Chicago, Ottawa, and London: Anglo-American Cataloguing Committee for Cartographic Materials, 2006.

This reference isn’t so easy to find: the only copy in the city that I could track down is in the UBC library’s reference staff area and hence unavailable for borrowing. In fact, when I went to look at it when I picked up Cartographic Citations, the reference staff was in a meeting, and I couldn’t even get access to it. Further, it’s pretty big, at 400 pages, and it carries a $138 price tag. Because Cartographic Citations is more than adequate for most editors’ purposes, I’d suggest going for that one, if you work often with maps, or leaning on the online sources.

What Mangan’s Cartographic Materials may provide specific guidance on is historical maps. I’ve had the privilege of working for several years on Derek Hayes’s magnificent historical atlases, for each of which he has had to compile a detailed catalogue of all of the maps that appear in the book. We have the odd disagreements about the format of these citations, he being more inclined to preserve the style of the original and I being partial to clarity and consistency. We’ve found a compromise we seem to be comfortable with—matching the case of the title given on the map, unless it’s in all caps, in which case we use title case. We do add punctuation for clarity if punctuation is implied but not actually written at the end of a line (for example, adding a comma if the title of a map has “Vancouver” on one line and “British Columbia” on the next). However, there are lingering questions, like when, if ever, it’s acceptable to truncate the very long title of a historical map, and where. And if a historical map appears to have several titles, how to decisively identify the map’s “main” title.

Paige Andrew, maps cataloging librarian at Pennsylvania State University Libraries, refers me to Rule 1E3 and Appendix G, “Early Cartographic Material” in the second edition of Cartographic Materials. When I return Cartographic Citations, I’ll take another shot at checking if Cartographic Materials is available to see if we can settle these issues once and for all.

Acknowledgments

If it isn’t already clear, I was overwhelmed by the outpouring of helpful responses from the Canadian Cartographic Association membership. Thanks to all of them, I’ve been able to clear up some of my confusion surrounding  editorial considerations in cartography.

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.

Top 10 controversies surrounding cattle

I’m an (extremely) occasional contributor to Listverse. Its quality has been hit or miss as of late, but I usually see one or two lists a week that I find interesting and learn something from. This morning my most recent list, inspired by Florian Werner’s Cow: A Bovine Biography, and a David Rotsztain cheese workshop I attended a couple of months ago, was published.

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.

Awards news

Thanks to Grace Yaginuma for reminding me that this past week Flavours of Prince Edward Island by Jeff McCourt, Allan Williams, and Austin Clement (Whitecap Books) won Gold at the Canadian Culinary Book Awards in the Canadian Culinary Culture Category, English-Language and Vij’s at Home: Relax, Honey by Meeru Dhalwala and Vikram Vij (Douglas & McIntyre) won Silver in the Cookbook Category, English-Language. Congrats to all authors! The awards were announced November 7; see a list of all of the winners here.

A celebration of Fred Herzog

“Today’s cameras are not designed by photographers. Today’s cameras are designed by geeks. And geeks do not take good pictures.” —Fred Herzog

Tonight’s event was, hands down, the best book launch I’ve ever attended—probably because it was more than just a book launch. It was also the advance screening of a documentary on Fred Herzog (part of the Snapshot) series, which will air on the Knowledge Network on Monday, November 14, at 10 pm.

The screening was hosted by Knowledge CEO Rudy Buttignol and featured speakers Douglas Coupland, Gary Stephen Ross, Sam Sullivan, Andy Sylvester, and Shelagh Rogers, who each chose one of Herzog’s photos and interpreted the image from his or her own perspective. Rogers had a family emergency and couldn’t attend personally, but, being the pro that she is, recorded her essay in studio for all of us to hear as an MP3. These special presentations were capped off with Herzog himself, an incisively witty and charming man, who gave his take on the photos that the others had commented on.

At the beginning of the evening Scott McIntyre got an opportunity to briefly recount the growth of D&M’s relationship with Herzog, and even gave me and Peter Cocking shoutouts for working on the new book. That was the evening’s first surprise. The second was that I’m shown in a scene of the documentary shaking Herzog’s hand at the opening of his Reading Pictures exhibit at the Equinox Gallery this past February.

Herzog said very explicitly in the documentary that he doesn’t sign books, and so although I’d brought along my copy in the hopes that I could get his autograph, I was a bit too intimidated to ask him at the reception. Zoe Grams and John Burns gently egged me on (the latter even providing the pen), and Herzog was gracious enough to make an exception, even as he was just on his way out.

All in all, it was a spectacular evening and a complete privilege. I’ve thought about contributing to the Knowledge Network for several months now, and tonight has strengthened my resolve.

Free range indexers

A book’s index is an afterthought for most publishers—allocated the pages that are left over from the last signature after the main body has been set. What ends up happening (entirely too frequently) is that indexers are handcuffed by a severe lack of space. I once had to compile a six-page index to a 336-page book—that’s less than 1.8 per cent of the page count—and I was forced to trim so many entries that the index was, for all intents and purposes, useless.

For a reference books or technical manual, the index can be one of the most important components of the publication, and most of the indexers that I know charge by the indexable page rather than the entry, so they’d be charging the same total fee regardless of index length. To severely limit the index space would hurt the book more than it would the indexer (although I’d like to think that most indexers would be disappointed to put forth an inferior product).

What we need, then, is—dare I say it?—a paradigm shift. Publishers and editors and whoever has input into the total extent of a book needs to consider the index integral from the outset. Do a rough cast-off based on the manuscript, and if what’s left over of the last signature is less than, say, 2.5 per cent, consider adding another half or full signature, depending on the total length of the book, and use this new page count in your project budget and P&L.

The American Society for Indexing has some guidelines for index lengths. For trade books, indexes should be about 3 percent of the book, whereas for technical reference books, they could be up to 15 or 20 percent. These figures can be squeezed a little bit, especially if you’re reducing type size in the index, but they shouldn’t be significantly less than what the ASI has recommended, if you want the index to be functional and readable.

On the other end of the spectrum are self-publishing authors or publishers who don’t give any index specs at all and say, “I’ll just do what I need to do to make your index fit.” This scenario is cropping up more frequently as more people are turning to print-on-demand options where they can add pages two at a time rather than worry about a full sig. It sounds like an indexer’s dream, but, in reality, we appreciate constraints. Without a size limit on the index, the temptation to hand over a bloated, unedited draft is entirely too high. Having index specs helps indexers trim the fat—to put careful thought into clear and concise subentries and eliminate redundancies that can lead to clutter.

Basically what I’m saying is that indexers are a lot like chickens (an analogy I’m sure you’ll hear no other indexer repeat). We’re happiest—and we produce the best product—when we’ve got space to roam around and breathe fresh air. But we also understand the need to be penned in, for our own protection. And, of course, getting a generous amount of feed for our troubles doesn’t hurt, either.

Kobo gets into publishing

I’m a bit slow on the draw here, but Kobo announced yesterday that it’s going into the publishing business. (I find it a bit curious that, a day later, none of this information seems to be on the main Kobo site—at least not in any of the obvious places, such as its blog or press centre.)

Apparently Kobo will be actively acquiring new titles and editing as well as designing them. I wonder what rates the company will be willing to pay its editors and whether they will be competitive with those of traditional publishers. Will Kobo bother to hire top-notch editors? Or will it take advantage of the low-cost outsourcing opportunities available on such sites as Elance and oDesk? It’ll also be interesting to see what the workflow will look like and whether this further addition to the burgeoning ebook medium will lead to formal, systematized professional development opportunities to train editors on ebook best practices.

Generally I’d say that the recent growth of ebooks is good news for editors; as many of my colleagues have discovered, helping self-publishing authors with their manuscripts can be huge business. However, with the glut of uncurated content, it can also be hard to impress upon the authors the importance of professional standards (I take heart in the fact that people on social networks still bother to correct others’ spellings—though Muphry’s Law does apply), and being an editor for a self-publisher can also mean becoming de facto project manager—a role you may or may not have wanted.

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.