function jdb_page_navigation()
sPageSlug = blog
sPageTitle = easily amused
header:139:aPageArgs:page_title = easily amused
header:140:aPageArgs:section_title =
functions-johndberry:262:aPageArgs:page_title = easily amused
functions-johndberry:298:sPageTitle = easily amused
functions-johndberry:359:sPageTitle = easilyamused

easilyamused |

An ironic typeface used for a non-ironic purpose

Published

’Twas the eighteenth of April of Twenty-fourteen…” Yes, it was, actually and literally. That’s when I snapped this picture of the sign at the edge of the Calvary Cemetery, overlooking University Village in Seattle.

Easter sign using the typeface Mason, zoomed in

The typeface, with its postmodern ecclesiastical look, is Jonathan Barnbrook’s Mason, which was originally released by Emigre Fonts in 1992 under the name “Manson.” For reasons that you can imagine, that name caused a lot of unease, and Barnbook soon dropped one n and renamed it “Mason.” By either name, it’s very much in the tradition of ironic type design, taking recognizable features from the past and combining them in unusual ways to achieve a new effect.

The smaller type, identifying the cemetery and its web address, appears to be the appropriately named Requiem. Presumably, irony was not uppermost in the mind of the designer of this welcoming and wholly un-ironic sign.

Massimo Vignelli & organizing information

Published

When Massimo Vignelli died last month, the obituaries and remembrances all mentioned his famous 1972 map of the New York City subway system. The New York Times, of course, spent a good deal of ink and pixels on the subject. In retrospect, everyone keeps talking about how confusing that map was to people at the time, implying that it may have been a brilliant design object but that it was a failure as a navigational tool. That’s not what I remember.

I first learned how to navigate the complex, contradictory New York subways in the late 1960s, when the Vignelli map had not yet appeared but the Vignelli-inspired system of color-coding the lines and identifying them by numbers or letters had been implemented. This was truly a system, and it made sense of a wildly inconsistent tangle of lines; it also made the sometimes chaotic interiors of the subway stations themselves navigable and understandable, at least to an extent. The system was designed not to tame the chaos but to give its users – the subway riders, both straphangers who used the system every day and newcomers or first-timers like me – a tool for navigating, for making our way through the jungle and getting to a destination.

The maps we used before 1972 were already highly stylized; they were really diagrams, not maps, despite the nod to geography in the background shapes of the city’s waterways and landforms. The 1966 subway map, which would have been the first one that I used, was already nothing like a realistic map; the lines in the outer boroughs were compressed and condensed, while Manhattan was shortened and fattened, not reflecting the actual geography at all. But the lines still had names, not numbers or letters (“SEA BEACH, W. END” or “JEROME LEX AV”).

By 1968, the map was clearly a wiring diagram of the city, and it introduced the consistent system of identifying each line by a unique number or letter (6, F, RR). The lines were color-coded as well, just like the signs within the stations. (In the 1966 map, the only color distinction was used to show which lines were part of the old IRT, IND, or BMT systems.) The map was complex, because the city’s subway system was complex, but it formed a very useful and usable chart that enabled you to understand how the system was put together and how to get from one point within it to another efficiently.

The famous 1972 map was just a continuation of this to a slightly more abstract level. Actually, to a slightly more abstract-looking level; the abstraction was already there. Compare the 1968 map to the 1972 one: both are diagrams, it’s just that the ’72 map makes this even more obvious. The biggest innovation was how it showed potential transfer points: instead of inscribing all the line numbers or letters in little boxes, the Vignelli map placed black dots side-by-side where trains from adjacent lines stopped at the same station. It was simple and clear, and if your line passed by but didn’t show a dot, that meant it didn’t stop at that station.

None of these subway maps were intended as a way to understand the city; they were intended as a way to understand the subway system, and to use that to get around the city. They were superb at that, and the more abstract they got, the better they did that job. I know; I used them constantly.

The first “schematic” map of the New York subways was produced in 1959. If you want to see what that was an improvement on, take a look at the 1948 map, which makes a brave attempt to reflect the geography and still show the tangle of lines and where they go. The comparison is educational. I know which one I would want to use as a guide.

Strangely, many of the people who complained about the 1972 Vignelli subway map would be perfectly content to use the equally abstract London tube map, which was introduced decades before New York’s attempts. Nobody in London would claim that the tube map gives you any idea of the layout of the city; but it’ll get you from station to station within the system brilliantly. The 1972 NYC subway map did the same.

Thank you, Massimo, for making it easier for me and a lot of other people to get around.

[Image: a detail from the recent digital version of the Vignelli subway map, even more simplified and rationalized than the original.]

Big on the web

Published

This week a pithy statement of mine has been making the rounds on Twitter: Only when the design fails does it draw attention to itself; when it succeeds, it’s invisible. I first noticed this quoted by Graphis, but when I googled it, to remind myself where and when I had said it, I was amazed to see how many times it’s been quoted and requoted over the past seven years. It even appears as one of “50 Inspirational Quotes on the Art & Science of Design.”

When I wrote this, in a 2007 column for Creativepro.com, I was talking about something very specific: designing the table of contents for a book. But obviously this sentence has struck a chord for many people, and it’s certainly applicable to many aspects of design.

If I ever do a second edition of Hanging by a serif, my small book of aphoristic statements about typography and design, I’ll have to include this one too. I wonder what serif I’ll decide to hang it from?

Covering books

Published

Edward Rothstein’s review in last Friday’s New York Times of the current exhibit at the Morgan Library focuses attention on the book jackets that make up an obvious part of the exhibit. The show, “Gatsby to Garp,” is about 20th century American literature, and one of Rothstein’s points is that the book jacket embodied – and sold – that literature in book form. “Jackets were the way books announced their significance in the modern bookstore — an institution that had this single century of hearty life.” It was, as he says, “the jackets’ golden age.”

Another of Rothstein’s points is that any public exhibit like this cannot convey the content of the books; by its nature, a display is about the form. You might show several copies of the same book, open to different pages, but that’s only a series of glimpses at the interior, where the words live. Reading is a continuous experience; viewing a staged exhibit is a series of observations. “This is usually one of the difficulties in literary exhibitions: it is impossible to offer the actual substance of the books, so the curator must make something of their presence, use them to illuminate one another, show why they are gathered in one place.” The Morgan’s curators seem to have dealt with this inherent contradiction in imaginative ways, but it’s still a conundrum.

Book jackets are the most obvious representation of a book, yet they aren’t really part of the book itself. The older term “dust jacket” is telling: the first purpose of a book jacket was simply to protect the book’s actual cover, which might be a highly decorated binding. In the development of commercial bookselling, it didn’t take long for publishers to realize that they could use these functional paper wrappers as advertising for the book inside.

That’s the primary function of a book jacket. It’s meant to attract the attention of the potential reader. But since most books for several decades have been paperback rather than hardcover, the distinction between the jacket and the cover has been obscured. Instead of an advertising wrapper that you could strip off once you’d bought the book, the paperback cover remains an integral part of the book when it’s on your shelves. The packaging, in effect, stays with the product.

Today, the book cover – or book jacket – has to function in a new way: as a small image on a digital screen. It’s still meant to attract the eye, but it has to do this at thumbnail size; and the hoped-for action by the potential buyer isn’t to pick up a book off a table but to tap or click the image on the screen.

How, I wonder, will a future collector like Carter Burden, whose collection forms the basis of the Morgan Library exhibition, commemorate the complex interplay of reading, writing, marketing, and bookselling that makes up publishing in the 21st century?

Back on the wall

Published

It’s gratifying to see, from a story on the TDC’s website, that the three-dimensional typographic mural that Lou Dorfsman constructed in 1966 for the cafeteria at CBS headquarters in New York City has finally found a permanent home.

As I wrote six years ago, the “Gastro­typographical­assemblage,” which a subsequent régime at CBS was ready to junk, got saved thanks to the efforts of NYC designer Nicholas Fasciano, and was given a temporary home at the Center for Design Study in Atlanta, while funds were being raised to preserve and restore the crumbling masterpiece.

Now, as you can see from this short video, it has been lovingly restored and installed at the Culinary Institute of America, in Hyde Park, New York. Sounds like a visit to Hyde Park is called for.

A measured response

Published

In on online discussion recently about book design, someone with long experience in print design made the claim that it was a proven fact that unjustified text was harder to read than justified. This was presented as an indisputable conclusion. That got me curious, so I made an effort to get hold of a copy of the source he cited: Colin Wheildon’s Type & Layout: Communicating – Or Just Making Pretty Shapes?. Obviously I would be in sympathy with a book with such a subtitle, but I was skeptical about the claim to hard data.

Wheildon first published this in Australia as a slim booklet in 1984; the version I found was the American edition, revised and expanded, published in 1995 by Strathmoor Press in Berkeley, with a cumbersome new subtitle: How typography and design can get your message across – or get in the way. (There’s a yet newer edition, from the Worsley Press in 2005, which I haven’t seen; happily, it goes back to Wheildon’s original subtitle.)

The heart of the book is the controlled experiments that Wheildon carried out, with as much care as possible and all the expert advice he could get, to test different typographic treatments, and try to find out, scientifically and measurably, which worked better and which didn’t. He came to this question from magazine publishing, with experience in both advertising and editorial design, so his examples are all from the pages, either real or made up for the experiment, of magazines.

Since Wheildon spells out in an appendix exactly how he conducted his research, it’s possible to judge the results. As far as I can tell, his methods for measuring comprehension after reading an article make sense, as far as they go; comprehension of facts may not be the only thing that’s important in reading, but at least it’s measurable.

Basically, he tested comprehension of articles that the participants had read, using a randomized series of questions that would tell him whether they had read all the way through the article or just read the first part and skimmed or skipped the rest. He also mixed this with anecdotal responses to particular features of his sample layouts, which he probably found irresistible but which renders many of his results dangerously subjective.

The real problem, though, is that in too many of his experiments, he didn’t measure comparable alternatives. It doesn’t really tell you much about the difference between serif and sans-serif text typefaces if the serif face you’re testing is Corona, a workhorse newspaper face, and the sans-serif is Helvetica, which was never intended for long text – and you’ve set both examples at exactly the same point size and leading. Testing a sans-serif typeface that was designed for text, and adjusting the size and spacing parameters to make them appropriate and comparable, rather than literally the same, would have been a much better comparison. Similarly, in a section about optimal text sizes, he made no allowance for varying x-heights and the difference in apparent size of different typefaces; he just compared 10pt to 10pt, no matter what the font. Even his test of ragged-right versus justified text tells us nothing about the details of how the text was typeset; it was just the same layout with either justified or unjustified setting.

I showed my borrowed copy of Type & Layout to Kevin Larson at a recent type pub in Seattle. Kevin is Microsoft’s researcher into typographic readability and legibility, so this is right up his alley. Naturally he refused to pass judgment based on just browsing through the book, but he did ask some pertinent questions about the specific test conditions and methods, which I found useful in thinking about Wheildon’s results.

What I found missing in Wheildon’s examples and his tests was the fine points of text typography that I’ve been dealing with for the past thirty-five years. In comparing serif and sans-serif settings of the same text, he used typefaces that, while indeed serif and sans, do not otherwise have much in common. Not surprisingly, the test subjects had a harder time reading a column of 8/9 Helvetica than they did a column of 8/9 Corona.

That’s the most obvious failure, but there are all too many places in Wheildon’s examples where he’s testing gross differences rather than well-adjusted settings in each format. He wrote this in the 1980s, so it’s no surprise that it doesn’t reflect the current state of typesetting technology, but it doesn’t even reflect the state of the technology in the 1980s: I was amazed that in his discussion of letter-spacing he confused kerning with tracking, and he seemed to think that letter-spacing in digital type could only be adjusted using one to four rather large units. (Perhaps he was thinking of the four pre-set tracking values in Aldus PageMaker?) Even at that time, typesetting systems were spacing in tiny fractions of an em.

Nothing in his trials had any way of measuring how much of a reader’s response was inherent and how much was just a matter of what they were already used to. (“We read best what we read most,” as Zuzana Licko famously quipped.)

What I came away with, after reading this book, was disappointment. I appreciated what Wheildon was trying to do; I just wish he had done it better. Some of his data is useful; some of it, unfortunately, is useless, or even misleading.

The focus of Wheildon’s attention was on magazines and advertising, rather than books, though most of what he says about reading text would have some relevance for books too. This 1995 edition of Type & Layout is not itself a very good example of book typography; the publisher and editor, Mal Warwick, makes it clear in a note that he is no typographer, and this is borne out on every page. Too often, Warwick’s re-creations of Wheildon’s examples use a different typeface, usually the light digital version of Goudy Old Style that he’s using as the text face of the book. That makes the examples impossible to judge. (Most of the examples that are reproduced directly from other sources are shown much too small to read, so we have to take the author’s conclusions on faith.) The general text typesetting is perfunctory, not carefully considered and adjusted. It’s a shame that the book itself doesn’t set a better example.

This edition is decked out with a foreword by David Ogilvy, an afterword by Tony Antin, and an introduction by Warwick, all of whom make much more grandiose claims than Wheildon himself does. Where Wheildon offers his conclusions modestly (though not without strong opinions), his promoters put them forward as proof positive of everything they hold dear. I don’t blame Wheildon for that, but it undercuts his book’s effectiveness. And it certainly doesn’t help that the publisher added two chapters of his own, which just show bad examples and make snarky comments about them; those two chapters can safely be ignored.

It’s the subtleties of composition, not just the broad strokes of layout or the size or choice of typeface, that make a page of text easy and inviting to read. Anyone who works professionally with book pages and text composition spends all their time on these fine points; and they don’t do it by rote or rules, but by intuition, experience, and paying attention to the text.

The allure of hard numbers – what software companies love to call “metrics” – is that you can quote them to clients or managers as a justification for your design decisions. But when the metrics rule the design, the tail is wagging the dog.

Rules of thumb can be very handy, but all they are is useful patterns; if you treat them like imperatives from on high – or from a few limited tests that others have inflated into ironclad laws – they’ll trip you up every time.

It would be interesting to see the real subtleties of readability tested, but it’s very hard to do, and it would take a lot of time and effort to come up with anything meaningful.

Mike Parker 1929–2014

Published

It’s hard to remember when I first met Mike Parker. I’m sure I had seen him and heard him at ATypI and other conferences before I ever got to know him; his tall, erect posture and booming voice were hard to miss, whether he was making a pronouncement or telling a joke (sometimes both at the same time).

I certainly got to know him better when he moved to Seattle for a while in the mid-1990s, to provide the typographic vision behind a start-up called Design Intelligence. Mike recruited me to design templates that would use suites of typefaces and hierarchical page designs to create a system of flexible layouts in various styles – not unlike what he had been working on already with his Pages Software, and not unlike what we are still trying to do today with adaptive page layout onscreen. We used to talk about where this idea could be taken, and while we were doing that he would tell me stories from his long history in the typographic field.

Mike was an inveterate storyteller. He might have embellished a story or two, as one does, but they were all wonderful to listen to. And they filled in many a hole in the history of type and the people who made it. Pity I can’t remember any of them in detail.

I do remember two incidents from somewhat later, during the San Francisco TypeCon in 2004. There was a big party hosted by a design firm in its studio on the top floor of an old building south of Market Street; everyone was invited, but the only access was through a rather small elevator, so you might have a long wait before you got to ascend to the party floor – and once there, you’d be reluctant to leave. Both Mike and I found ourselves uninterested in the lively dance scene that dominated the room, so we grabbed a couple of folding chairs, propped them against the wall, and spent the next hour or two watching the action and chatting comfortably between ourselves. That, I believe, was when Mike explained to me the chthonic origins of a river name in England, and regaled me with tales of the neolithic standing stones at Avebury. This was an altogether perfect way to spend the evening. Every once in a while, one of us would get up (usually me) and get us another couple of drinks.

The other conversation I remember from the same conference was over dinner, at an Italian restaurant near Union Square that Mike suggested. I don’t recall how we got on the subject, but we were talking about the transition from metal type to phototype and then to digital type, and the design compromises that had been made in adapting so many text faces to the new technology. In particular, I mentioned ITC New Baskerville, which had begun life as Mergenthaler’s adaptation to phototype of a popular Linotype text face. I lamented that New Baskerville seemed too “bright,” too high-contrast, to work well in text, and I speculated that in adapting the design from metal, they had used too large a master (14pt or larger) rather than a text size such as 10pt.

What I was momentarily forgetting was that Mike Parker had been, for more than a decade, the head of typographic development at Mergenthaler, overseeing the transition of their library from hot metal to phototype.

Mike just leaned over the table toward me and said, quietly, “I’m sorry.”

I started, then we both laughed, and continued the conversation.

[Image: From the cover of a tribute booklet from TypeCon 2012, when Mike was given the 2012 SOTA Typography Award. Illustration by Cyrus Highsmith. The type, of course, is Starling.]

Questionable practices

Published

Many of you know that I live with an author: my partner and wife Eileen Gunn is a well-respected short story writer, whose first collection, Stable Strategies and Others, was published in 2004 by Tachyon Publications. Not surprisingly, I designed and typeset that book (and ended up doing a good bit of design for Tachyon, sometimes covers, sometimes interiors, over several years). We also developed a visual identity for the book and its marketing campaign – a necessity in today’s publishing world – where I had fun putting the incendiary cover image to work in other contexts.

EileenGunn.com

Now I’ve designed her second collection, Questionable Practices, which will be out in April from Small Beer Press. The interior text design echoes the earlier book, but we gave this one a distinctly different cover design – though one that I think will sit comfortably on a bookshelf next to Stable Strategies. The publisher has just sent out ARCs (Advance Reading Copies) to reviewers.

The cover for Questionable Practices went through three entirely different versions, as these things often do (not counting the innumerable iterations of each still lurking on my hard drive). It’s in the nature of commercial book publishing that the publisher needs a cover image, for publicity and marketing purposes, long before they need a finished book; indeed, often enough the text isn’t finalized until long after a cover image has been widely distributed. When I was working as a typographer at Microsoft Press in the mid-1980s, we used to get outside “designs” from a local studio that simply provided cover sketches and sample pages with typical interior design elements; these were done long before the book was even written. Not only did we have to execute the final covers, but we often had to invent designs for new interior elements that came along as the books were written and edited. Eventually, since we were doing half the design work anyway, we took the interior design in-house.

Eileen’s stories don’t fit into obvious categories; they’ve almost all been published as science fiction, but she refuses to ever repeat herself, and her work rejects easy classification. When I designed the cover for her first collection, I was trying to do something that would stand out both on the general-fiction table and in the science-fiction section of a bookstore. As I discovered, though, few bookstores were willing to shelve copies of the same book in two different sections; it was always one or the other. Today, with online marketing and bookselling, perhaps it’s easier to place a book in multiple categories at the same time. In any case, today a book cover needs to be clear and work well as a little thumbnail image, not just at full size on the physical book.

Naturally, each of the three cover versions for Eileen’s book seemed perfect to me at the time, but in the end the one you see at the left worked best – and will be on the book. As a completely objective and nonpartisan observer, I can say: watch for it.

[Update, Jan. 16: I just sent the book to the printer today. Publication date: March. Typeface: Dolly Pro.]

Structured writing for the web

Published

At the end of June, at the Ampersand conference in Brighton, Gerry Leonidas gave a shout-out to an early version of the prospectus for Scripta (“Typographic Think Tank”) in his talk. I had somehow missed this until Tim Brown mentioned it in an e-mail recently inquiring about Scripta. I can highly recommend Gerry’s talk, and not only because he quotes me (7:07–7:49 in the video). Although he starts out with a disclaimer that “this is a new talk” and he’s not sure how well it will hang together, in fact it’s extremely coherent; Gerry is both articulate and thoughtful about the wide range of questions (and, rarely, answers) involved in typography on the web.

Gerry used my “wish list” from “Unbound Pages” (in The Magazine last March) as a jumping-off point for his own ideas about the structure of documents and the tools that he wants to see available. He wants tools for writers, not just for designers, that will make it easy to create a well-structured digital document, one that will maintain its integrity when it gets moved from one format to another (as always happens today in electronic publishing). Gerry’s own wish list begins at 20:47 in the video, though you won’t want to skip the entertaining steps by which he gets there.

What he proposes is a way to separate the sequence of information from its relative importance and interrelatedness. “This is what I really want: I want someone to go out there and take Markdown, which I use constantly, and take it from something that clearly has been written to deal with streams of stuff with some bits thrown on the side … and allow me to have this extra intelligence in the content – while I’m writing it – that will tell me how important something is, what sequence it has with other things, and will then allow me to ditch quite a lot of this stuff that is happening there.” The “stuff” he wants to ditch is all the hand-crafted formatting and positioning that makes a digital document cumbersome and difficult to translate from one form to another.

The problem is, as Gerry admits, training people to write with structure in mind. (Every editorial designer who has tried to get writers to use paragraph and character styles will break out into a hollow laugh at this point.) What he’s advocating is tools that will make this easy to do, instead of something that only makes sense to experts. I think he was a little disappointed that nobody leapt up at the end of his talk to say, “We’ve already done that!” But perhaps he has planted the seed.

A brace of book launches

Published

I’ve been to two very well attended book launches in Seattle this week – both them within walking distance of my home. The first was for Nicola Griffith’s new novel Hild, at Richard Hugo House on Wednesday; the second, last night, was for Judith Gille’s self-published memoir, The View from Casa Chepitos: A Journey Beyond the Border, at the Elliott Bay Book Company. It was gratifying to see both venues packed.

Nicola’s book I have no connection with other than knowing and admiring Nicola and looking forward to reading each of her novels. Judith’s book I do have a connection with: I designed and typeset the interior. (I had nothing to do with the flamboyant and effective cover, which was designed by Dorit Ely.)

I got to use Mark van Bronkhorst’s recently released OpenType Pro version of MVB Verdigris, which was completely appropriate to the visual feel that Judith wanted for her book. I even got to confront the interesting problem of how to treat a chapter opening with a drop cap, when the first word is the beginning of a quote in Spanish, requiring not only opening quotation marks but an opening inverted exclamation point as well. I could have finessed the problem by de-emphasizing the punctuation marks somehow, but in the end we decided that it worked with some judicious spacing and fiddling around. (Oh, yes: our chapter-opening convention also included small caps for the first several words, which in this case required italic small caps. Happily, Verdigris Pro includes them.)

Chapter opening from 'The View from Casa Chepitos'

I’ve already read and enjoyed Judith’s memoir, a thoughtful and empathic account of becoming a part-time resident of San Miguel de Allende, Mexico. Now I’m enjoying Nicola’s lively historical novel, in which she creates a believable milieu and a strong character for the 6th-century Anglo-Saxon abbess, Hild of Whitby.

One thing that both books have in common is strong women – including the authors.