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 |

Archive for 2011

Designing digital books

Published

At TypeCon in New Orleans last month, I spoke about “New problems in book design” – basically the question of how to apply good typography to the design of books that are meant to be read on a screen. Here’s a little of what I said:

“What does it mean to design a book, at a time when books take multiple forms?

“I have no answers; this is all about questions. As Nick [Sherman] said, we’re in a period that people will look back on and see as a seminal time. It is; we’re inventing this as we go along. And the reason I find it interesting is that I read books, and I’ve been designing books for twenty-five years. I’ve spent most of that time — starting out demonstrating that you could use digital typesetting and design tools to do typography every bit as good as what could be done in old metal systems. And now it’s about time to translate that onto the screen.

“One of the reasons it’s interesting now is that I think the tools are beginning to be there for us. And publishers are desperate for it.

[…]

“Basically, what we need is control over all the typographic aspects – but give up the idea of control to make a static page. We want that level of control – I want that level of control – over a dynamic page. So I can say, if somebody decides to change the type size: okay, the line length should stay the same. The number of columns would change – not just making the font larger and making the leading change, which is what happens today in a website when you do that (depending on whether the browser allows you to do that or just blows the whole page up). All those factors need to be controlled together. What we need is dynamic design, we need flexible design, we need intelligent design – intelligently flexible, intelligently dynamic – in order to create good design. And the reason for that, the purpose of that, is the readers: for us, the readers. You can’t design books well if you don’t read them, and that’s true for the screen as well as for paper.

“Every publisher I’ve talked to, every editor, even most of the writers I’ve talked to, is desperate for some kind of solution here. I know writers with backlists that they have the rights to but they don’t know what to do with; they just want to say, ‘Can I put it on a Kindle somehow?’ So the marketing and the sales of books are going to change too – dramatically. But I think that what we need to do is think globally about that, think about how to design, and sell, and market books, both in printed form – for those where that’s appropriate – and in digital form. And as much as possible, for practical reasons, design it so that you actually…so the book can grow out of one file, one set of files. It’s hard! But that’s what we need. Because otherwise, again, you’re back to doing several different versions of everything.

“So in the spirit of it all being questions, I’m concluding inconclusively, and I will throw it open to questions.”

Some of the best stuff, as you can imagine, came out in the questions.

Roger Black: “John, are you saying that we need to set, basically, an extension of HTML rules for typographical things like the relationship between line breaks and leading?”

Me: “Absolutely. How you go about it is a good question, and it’s something that I’m working on right now; but it’s important to have the capability, just as it’s important to have, in browsers and the systems that support them, support for OpenType features.

“But it’s the layout and spacing controls that are the most important part. It’s hard – but not impossible. CSS3 and HTML5 are beginning to add these capabilities. Obviously, in terms of browser constraints, not everybody is going to support that, but… It may be that you use HTML-based systems to still make applications; essentially the book could be an app, if you need control that you can’t have otherwise. I suspect that we’ll do it in both formats. It’s an open question.”

[Thanks for Jill Bell for sending me a copy of the video she shot from her phone, so I could find out what we actually said. The photos above are snapshots grabbed from that video.]

Type Works: Will Powers

Published

When Will Powers died suddenly two years ago, he left a gaping hole in the community of typographers, printers, and book-designers in this country. Now we have a small book to remind us of the work that he left behind: Type Works: the printing, design and writing of Will Powers.

It’s small in extent (50 pages) but not in format: its pages are a generous nine inches square, as befits a book that’s got to show a lot of examples of the design of other books. Oddly, there’s no one named as author or editor, which will perplex book dealers and annoy librarians; it’s simply credited to Interval Press, Birchwood, Minnesota. My copy was sent to me by Cheryl Miller, Will’s wife, and the copyright is in her name. (The information page on the distributor’s website confirms that Cheryl is the book’s editor.)

This collection of essays and reminiscences by Will’s many friends and collaborators gives a kaleidoscopic picture of the man. Although by the time I first met him, he was living and working in Minneapolis, as design and production manager for the Minnesota Historical Society Press, Will had spent many years in the San Francisco Bay Area as a letterpress printer. He and Wesley Tanner printed Fine Print for several years, and Will also wrote articles and designed covers for that remarkable publication. Reading about those times now, with names of people I came to know many years later, makes me imagine an alternate history in which, when I was living in San Francisco after I got out of college in 1971, I had somehow made contact with the local printing community. But at that young age I had no idea that typography was going to be central to my life, and I didn’t meet any of those people, or stay in the Bay Area.

Type Works is a short-run book, printed by BookMobile in Minneapolis, who specialize in short-run and print-on-demand books (and who I know from experience can do a good job of it). Given the display purpose of this book, I could wish that it had a sewn binding that would lie perfectly flat, but that’s not an option in this short a run, unless you manufacture the book by hand. I also wish I could read every word on every printed example shown, but that’s just a reflection of how fascinating the texts that Will worked on (or wrote) tended to be. This is a fine presentation of examples of Will Powers’s excellent typography and book design, of the words written about him, and of a few of his own words as well. And I love the fact that the text uses Zuzana Licko’s typeface Journal, an idiosyncratic but very readable text face of the digital era.

TypeCon surges ahead

Published

TypeCon 2011 – the first one run by SOTA on an all-volunteer basis – seemed to be a successful conference, and it was held in a fascinating city: New Orleans. The single-track program was well designed to engender conversation; in fact, individual presentations seemed to be speaking back and forth to each other, even when they had not be planned with that in mind. A lot of that conversation was about web fonts, design for the screen, and new forms of publishing. That’s what I spoke about myself, in a rambling talk full of questions and explorations (“all questions; no answers!”) about the problems and possibilities of designing books for a digital age. You won’t be surprised to hear that I embraced flexible design and adaptive layout as the best way to design any extended text for a variety of screens.

Everyone enjoyed New Orleans – the food, the music, the culture – though some attendees weren’t prepared for the binary contrast between the hot, steamy outdoors and the brutal air-conditioning in the hotel and in the bars and restaurants. The hotel was in the heart of the French Quarter, however, right on Bourbon Street; a fun place to be, but definitely also a tourist bubble. Bourbon Street seemed the least changed of any part of the city that I saw, since my one previous visit back in 1988 (also for a conference, also in the summer). I’m sure this is not only because the Quarter is on high ground and Katrina’s flood waters mostly didn’t reach that far.

I couldn’t, of course, make it to everything on the program; and as I didn’t arrive until Thursday afternoon, I wasn’t there for the pre-conference Education Forum or workshops. Presentations that stood out for me were Bill Berkson’s provocative “Great Readability Scandal”; Amelia Hugill-Fontenel’s well-crafted and artfully delivered “Artifacts All Around,” about some of the typographic curiosities in the Cary Collection at RIT; Otmar Hoefer’s affectionate tour of the collection of the Klingspor-Museum in Offenbach; Veronika Burian and José Scaglione on their joint type-making venture; and the “three guys in hats” (Scott Boms, Brian Warren, and Luke Dorny) on how designers use web fonts. Particularly notable was the presentation by three guys from the Cherokee Nation, about designing type for the Cherokee syllabary; this was a real-world application of type design that really matters. (“Every font that’s made makes your culture stronger.”) I also liked the tail end of Nick Sherman’s talk, filling in at the last minute for the absent David Berlow, though I missed much of Nick’s talk because I was too busy preparing for my own, which was up next. It was also fun hearing Matthew Carter, John Downer, and Akira Kobayashi do an onstage type crit of each other’s well-known typeface designs.

The heart of the event is always just meeting and talking with people, often at the evening social gatherings. Sometimes they were just a late-night party overlooking Bourbon Street, or an expedition to go “type busking” in Jackson Square in the hot summer night. TypeCon traditionally concludes with a special Sunday-evening event, after the close of the official programming; usually it’s something type-related, such as the visits to printing museums in Boston and Los Angeles, but this time it was pure tourist indulgence: a ride on the riverboat Natchez up and down the river, with music and drinks and commentary as we viewed the city and its environs from the middle of the Mississippi. The ship was by no means ours alone; we were just one among many groups aboard. But despite the cliché’d nature of the voyage, it proved to be a relaxing and enjoyable way to end a conference, and also to get a better sense of just where we were.

I got an even better idea on Tuesday, before catching an evening flight back to Seattle, when my friend Nevenah Smith, an artist who has lived in New Orleans for more than ten years, gave me a whirlwind tour of the city’s neighborhoods. It was great to get away from the Quarter and see something more down home. Even seeing parts of the devastated Lower Ninth Ward or the flooded-out sections near Lake Pontchartrain was a welcome reality check – and encouraging, when Nevenah pointed out to me the new houses being built there by volunteers for returning locals, and the people hanging out on their front porches the way they always used to. New Orleans has been devastated, especially the poorer neighborhoods, and its people treated shabbily. There’s no reason to expect that it won’t happen again; but there’s a resilience among those who’ve stayed or come back. I had prepared for this visit by watching Spike Lee’s powerful documentary When the Levees Broke and by reading Ned Sublette’s excellent book The World That Made New Orleans; I was trying to finish Ned’s more recent Year Before the Flood before I left for TypeCon, but I’m still reading it now at home. All of these gave me a little bit of insight into the context of the city I was visiting. (Even after the fact, I would recommend them to anyone who was in New Orleans for TypeCon.)

No venue was announced for next year’s TypeCon. Perhaps you’d like to put it on.

[Photos, top to bottom: what really goes on at a type conference (hint, hint); Ed Benguiat can’t escape his own typefaces; TypeCon attendees on the Natchez riverboat.]

Flexible, adaptive, responsive

Published

For the past couple of days I’ve been devouring Ethan Marcotte’s new book, Responsive Web Design. It’s the fourth in the series of “brief books for people who make websites” published by A Book Apart (an outgrowth of A List Apart). Each one focuses on a specific subject, and is written in a direct, conversational manner with a hands-on approach for web designers.

“Responsive web design” is Marcotte’s term for what I first heard referred to as “adaptive layout” by Microsoft’s Geraldine Wade (now Banes) when she was working on the original New York Times Reader. I usually just call it “flexible layout.” (As the Times Reader app suggests, it’s not only applicable to web pages.) The essential idea is visual design that adapts itself intelligently to the size, orientation, and resolution of the digital “page” it’s displayed on. This can be done well or badly, of course, but first you’ve got to understand the importance of doing it at all.

Marcotte is cogent and persuasive about that. And he shows you exactly how to do it, step by step, even though this is not strictly speaking a “how to” book. More important, he shows you why to do it. His last chapter suggests a reversal of the notion of “graceful degradation” in onscreen design: instead of making a complex design for a big monitor and the latest, most capable software, and then figuring out how it should deal with smaller sizes or less capable systems, he suggests starting by designing a simple, uncomplicated basic design that will work on the tiniest mobile device (“mobile first”), then adding features as (and if) they seem useful in a more expansive environment. Both approaches are adaptable and responsive, but this one seems cleaner and more elegant.

Now the area that interests me most is text typography, which Marcotte doesn’t go into in any great detail. But this just means that there’s more to be learned and invented in this area.

I’m a fan of small, handy, precisely targeted books, and the Book Apart series is just that. These books are consistently designed (by Jason Santa Maria), readable, and easily portable (despite somewhat heavy coated paper). There are a few bits of sloppiness; the proofreader could have caught the glitches in the hyphenation algorithm that produced “wides-creen” and “in-teract” as word breaks, and a copyeditor might have questioned the author’s frequent use of “to better [do this]” or “to better [do that],” but these are quibbles. Responsive Web Design and its predecessors in this series are useful, well-done tools in their own right.

ATypI Reykjavík 2011: registration & program

Published

Registration has just opened for this year’s ATypI conference in Reykjavík, Iceland, September 14–18, and the preliminary program has been posted. Early-bird rates for registration will be available until August 13.

Iceland has an active local typographic and design community, and has the singular advantage of being easily reachable from both Europe and North America. (Icelandair even flies nonstop from Seattle these days, which is selfishly convenient for me.) The conference venue will be the newly built Harpa concert hall and conference center in Reykjavík, and the keynote speaker will be Icelandic calligrapher and type designer Gunnlaugur SE Briem.

Go ahead – register now!

Regional powers

Published

I’ve been looking with interest at “CSS Regions,” Adobe’s entry into the arena of flexible page design on the web. This is clearly the sanguinary bleeding edge of onscreen design today – designing intelligent layouts that will behave differently (but coherently) under different circumstances, most notably on screens or in windows of different sizes and shapes.

Adobe Labs has released an experimental WebKit-based web browser, as a platform for showing off what CSS Regions can do. The demonstrations are mostly about shapes: they include multiple columns, arbitrarily shaped text blocks, text that flows from one text block to any other text block on the page, and a couple of other, more specific tricks. In the demos, text wraps neatly around images or around other text, in a highly flexible manner.

It’s good to see these problems being tackled. But there’s something missing. As an earlier Wedmonkey article about this technology put it, “when it comes to the flow of text around images, pull quotes and other block level elements, well, web typography falls apart.” CSS Regions is clearly aimed at enabling design with these “block level elements.” But that’s only macro-level typography; what about the typography of the text that’s doing all that wrapping? We need the same level of control over text typography on the web that we’ve got today on the printed page. And not just in an inflexible page created in InDesign and turned into a static PDF.

More tools, please.

Powers of observation

Published

In an unexpected confluence of two of my areas of interest, science fiction and graphic design, I discovered that design critic Rick Poynor has been waxing lyrical, over on Design Observer, about the surrealist cover paintings done by Richard Powers for so many science-fiction paperbacks in the 1950s and 1960s. I grew up on those covers. Although I knew nothing about surrealist art, nor for that matter about book design, I remember those Powers paintings as representing the mood and style of science fiction to me. They were very far from the rocketships and spacemen that might adorn a less sophisticated cover. It wasn’t until later that I learned who he was (it was rare for an artist’s credit to be included in those books), yet his visual imagination burned its way into my own, all unknowing.

Powers’s images were almost never representational; they were dreamlike and evocative, with flowing shapes, curving lines, and polished surfaces, floating in a limitless space of the mind.

Poynor takes off from a reference in the Guardian’s science fiction issue, where the editors asked a wide range of science fiction writers to describe their favorite novel or author; Christopher Priest wrote about J.G. Ballard’s early short-story collection, The Voices of Time (left). The cover of that Berkley paperback was classic Richard Powers; so was the (different) cover of a later reprinting (also from Berkley). This provides Poynor with a perfect jumping-off point.

The image to the left is not a swipe from the Guardian, but a scan of the cover of my own lovingly tattered copy of The Voices of Time. The only time I met Ballard, on a reading tour for Empire of the Sun, I had the pleasure of getting his autograph on this book that I had kept with me since I was a youthful sf reader.

Madame Wahler’s Lucky Serif Dream Book

Published

There are always plenty of reasons to be a member of the Type Directors Club, the New York–based organization that fights a never-ending battle for truth, justice, and really great typography. But a particularly wonderful reason arrived in the mail just the other day: a little 16-page booklet called Madame Wahler’s Lucky Serif Dream Book.

This invaluable guide, written and designed by Gail Anderson and illustrated by Bonnie Clas, could set you on the road to a better life. “This book will make you a winner!” exclaims the back cover, and who could doubt it? As the introduction explains, “The Type Directors Club is the first international organization to make public a genuine and authentic guide to the connection between typography and dreams.”

The contents include a list of dream types (“To dream of ligatures denotes popularity with the opposite sex”), a typographic horoscope (“As the most sensitive sign of the zodiac, Pisces is easily devastated by poorly drawn characters”), and small ads for everything imaginable (“Miracle Open Type Necklace,” “Go Away Comic Sans Cologne,” and “PROFESSOR INA’S Tattoo Type Removal Cream”).

Remember: “Madame Wahler’s Lucky Serif Dream Book will prove itself valuable as a reference because it uses small words and lists the meanings of many popular lettering dreams.”

Reading matter

Published

The new issue of Typo has a thoughtful article about the typography of onscreen reading – entitled, sensibly enough, “Electronic reading: the future is now.” It certainly is.

The author clearly knows his stuff. According to his bio note, “Martin Pecina is a designer and typographer, enjoys reading and designs books.” An enjoyment of reading is a prerequisite for designing books, or at least doing it well. (I know that my own approach to designing a book starts with imagining how it would be to hold and read that book.) And an enjoyment of reading should also inform any design for electronic books, as Pecina points out in a rather severe critique of the current state of the art.

He doesn’t just show off bad examples – something that’s absurdly easy to do with almost any current form of e-reader – he spells out the kind of typographic decisions that need to be made in laying out a page of text, whether that page is fixed and printed or fluid and controlled by dynamic rules. Anyone working in digital book publishing today ought to read this article.

Pecina analyzes the problem by dividing it into two parts: basically, the hardware and the software. The hardware may be a “universal device” (a computer or phone that serves a number of functions, of which reading is just one) or a “specialized device” (a dedicated e-reader). He is scathing about the nature of most computer screens: “But – it is impossible to read well from a lit display. Sure, we read websites on them, even PDF documents, maybe annual reports, press releases and various corporate documents. But it’s no good for reading long passages of text.” He feels that the only reasonable future for digital books is passive display technology using e-ink and reflected light. “In terms of electronic books, the backlit display is a dead end and brutal debasement; devices with this technology will never fully replace printed books, no matter how many millions of titles for the iPad or similar devices end up being sold.”

In the long term, I’m sure, he’s quite right. The future of long-form reading may be a few high-quality printed books, supplemented by a kind of smart paper, where nanotech “ink” forms and re-forms the text as needed on a single page.

Most of the essay, however, focuses on the software used to create e-books, cataloging both what the currently available systems do and what’s needed to make them work right. He makes a distinction between a “final” document, a composed page (whether in print or in a fixed form like a PDF file), and an “unfinalized” document, where both the form and the content may continue to change. (He doesn’t give much attention to the idea of a document whose content is fixed – nobody’s going to change the words of a novel – but which might be presented in a fluid variety of forms.) And he raises serious questions about books with complicated multi-level text, such as scholarly publications, which may have footnotes and several layers of nested content. (Scholarly books would benefit most from electronic publishing, since the audience is usually small and the cost of printing proportionately high, but creating a system that can handle that kind of complexity in a flexible manner is not easy.) “Simple text,” he says, “is flexible, can easily flow from a small into a large format or from landscape into portrait orientation, all quickly and without losing a bit of its essential nature. The situation is perceptibly different for scholarly or professional texts.”

Pecina gives a nod to the two-page spread, so innate to the nature of a printed book bound at the spine. Digital books, of course, do not have any need for a spine, and therefore no need for facing pages, although some e-reading software tries to present a familiar-looking facsimile of an open book. He mentions the “scrolling” model, which we’re all used to from websites and word-processors; what he doesn’t mention is that before the codex form of the book, handwritten scrolls too were composed in pages – though not in two-page spreads. I remember how surprised I was when I learned that real-life ancient scrolls were held horizontally and read side-to-side, not held top-to-bottom the way you see in cartoons and historical movies. Perhaps a royal proclamation would be held vertically, but an actual book – the literature of the Greeks and Romans, or the religious texts of the ancient world – was held horizontally and rolled open enough to view a single, relatively narrow block of writing: a single page. Perhaps we’re coming back to an older tradition than we’ve been following for the last millennium or so.

Pecina also mentions the design problems of books with illustrations or other images, which a traditional book designer deals with in composing a page. What he doesn’t go into is the other kind of editorial design, which shares a lot of its DNA with the book: magazine design. There are books that revel in image and display type with hardly any traditional “text” content, and there are scholarly journals that are essentially books in periodical form; the boundary is very porous. Do magazines lend themselves to display on an e-ink device? How about sumptuous art or photography books? Is the dividing line the need for color? The balance between image and text? The ephemeral nature of the content?

I suspect that the problems of designing complex books for reading on a variety of screens are akin to the design problems currently being posed by magazines with digital editions. The answer requires truly dynamic layout, with all the careful thinking-through of hierarchy and if/then behavior that that implies. If such systems of design and production are sophisticated enough, they’ll be able to handle text and image of any complexity, and do so in a typographically elegant way that just seems natural to read. That’s where the future is, now.

[Image: cover of Typo 43, Spring 2011, with its witty commentary on fonts’ spotty support of Central European character sets.]

Back to the Futura

Published

A couple of weeks ago, we drove down to Portland to see a play that promised to mix science fiction and typography. How could I resist a that combination? (“Are you sure you didn’t write this play?” asked a skeptical friend of mine when I told him about it.)

The play is Futura, written by Jordan Harrison, and directed in this performance by Kip Fagan at the Portland Center Stage. (I say “this performance” because the play was having a sort of parallax début: it opened simultaneously in Portland and Los Angeles, after being workshopped in 2009 at the JAW Playwrights’ Festival in Portland.)

The opening act is a lecture on typography – and a good one. In the best science-fiction tradition, you realize, as the lecture goes on, that there’s more to the context that you thought. When the lecturer whips out a genuine piece of paper, it is clearly meant to be a shock to her students. This is a world where physical books have been superseded, and banned, replaced by an agreed-upon digital library that keeps changing, and has no grounding in solid fact. The lecturer drops acerbic references to her late husband, who seems to have been murdered, apparently by the forces of imposed order.

The first act ends [spoiler here!] when the lecturer is suddenly kidnapped, blindfolded and hustled offstage.

The trouble with Futura is that it breaks down after that. The four actors seem good; it’s the writing that lets them down. The arguments between two of the main characters in the second act are true to life, the kind of half-thought-through emotional arguments that people really make. But the play itself doesn’t rise above them, or go any deeper. The logic falls apart at the slightest touch. The metaphor, reminiscent of Fahrenheit 451 and 1984, doesn’t really offer any more insight than a sort of worried extrapolation of Google’s attempt to digitize the world’s books.

The stage sets were wonderful. (I wonder what they were like in the LA performance.) I’m not at all sorry that I went to see this play; I’m just disappointed that it wasn’t better than it was. There’s a lot to be said about books, printing, digital literature, and society; but this play didn’t go beyond its own characters’ blinkered arguments.

Still: “Futura”? How could any typographer resist?