easilyamused | John D. Berry’s blog

At TypeCon in Milwaukee at the beginning of this month, Cyrus Highsmith gave a witty, illustrated talk about spacing in text typography, which served as an introduction to his new book, Inside paragraphs: typographic fundamentals (published by Font Bureau). It startled me, because I hadn’t been aware that he’d been working on such a book, and because it dovetails with what I’ve been talking and writing about for quite some time: that typography is all about space. Appropriately enough, though without any planning on my part, my former colleagues at Microsoft had brought stacks of one of my little typography booklets, Arranging fonts: it’s all about space, which is about exactly that.

Cyrus focused on the paragraph as the basic unit of text typography, which is a sensible way of looking at it; that neatly separates what Jost Hochuli calls “microtypography” from the “macrotypography” of the page. And Cyrus can draw a lot better than I can, so his illustrations – both in the book and in his talk – make his points brilliantly and lucidly.

The book itself is small, light, and oblong – very easy to carry around and read, with long paper flaps that you can use to mark your place. Cyrus wrote it because he wanted it for the typography classes that he teaches at RISD; and because he wished that he’d had it when he was studying design. It’s probably a good introduction to the subject for graphic-design students, but even more than that, it’s a basic explanation for anyone who uses type and wonders why it sometimes looks right and sometimes doesn’t.

Categorized as books, education, publishing, typography, writing & editing |

I’ve done a number of projects with Seattle poet JT Stewart over the last few years: two chapbooks, a bunch of broadsides, promotional materials for events, and the workshop that we’ve taught together for poets who want to turn their poems into broadsides. Most recently, JT’s work was selected for a display of literary and visual works that came out of Artist Trust’s EDGE program, a “professional development program” for artists. The exhibit, called “A Celebration of Washington Artists,” is on display at the Washington State Convention Center in downtown Seattle until October 18. Most of the work on the walls is paintings, prints, photos – visual art – but interspersed among them are poster-size displays of some of the writing that has come out of the program. Since the poems of JT’s that got selected came from the chapbook Love on the Rocks – Yet Again, which I designed and produced, I created a visual display for them as part of this exhibit. Two of the four panels are the front and back covers of the chapbook (the back features a highly visual poem); the other two are poems from the body of the book, presented in a format that I thought would be eye-catching and readable on a public wall.

When I stopped by the WSCC on the first day of the exhibit, I could spot our installation immediately from the escalator. On the way back down, I caught a snapshot of someone already stopping to read the poems.

Categorized as books, culture, events, science & art, typography, writing & editing |

On Wednesday I was in Port Townsend for an “E-book Potlatch” at Copper Canyon Press. The press is housed in one of the old wooden buildings at Fort Worden, a former military base turned into a state park and cultural & arts center; Copper Canyon has been there since the 1970s, publishing some of the best in modern and international poetry. Right now they’re figuring out how to bring their backlist (and their front list) into e-book format alongside their printed books – and how to do it right. Consortium, the independent-books distributor, and the “e-book aggregator” Constellation (both part of the Perseus Books Group) sent three people to this planning meeting; according to Consortium’s Michael Cashin, Copper Canyon is on the cutting edge of creating readable e-books for poetry.

For five years in the ’90s, I was the designer for Copper Canyon’s books and collateral, and I’ve done a few projects since then, but my only current connection is as a friend and supporter of the press. Still, e-book typography is what I’ve been thinking about for the past year, so it made sense to participate in the meeting. I was impressed by the level of thinking and planning that was already going on. Both Copper Canyon and Consortium are committed to finding good ways to get books into practical e-book form right now, for immediate sale, and at the same time to developing formats that will be true to the unique demands of poetry and the future demands of technology. It’s not an easy task, but it’s well worth doing. This is an essential part of our culture.

The all-day summit was productive but exhausting. At the end of the day, Copper Canyon hosted a cook-out on the beach at Discovery Bay, where executive editor Michael Wiegers cooked up clams and prawns and salmon, and a few bottles of wine were drunk. It was one of this summer’s rare warm, sunny days, and some of the madder members of the crew ran out into the cold, cold water for a refreshing dip. That’s how the future of publishing happens.

[Photo: Michael Wiegers (left) and me on the beach at Discovery Bay. Photo by Valerie Brewster.]

Categorized as book design, books, culture, events, onscreen design, publishing, typography |

If you’re in San Francisco on June 15, I suggest that you drop by Swissnex, 730 Montgomery, between 6:30 and 9:30 p.m. to hear Jack Stauffacher in conversation with his friends. I’ve written plenty of times about Jack, who simply calls himself a printer but in fact carries on the cultural traditions of centuries of printing and learning through his practice of the printer’s trade (and, not incidentally, his practice of talking and thinking and encouraging others to do the same in his company). If I weren’t going to be in Yerevan for Granshan 2012 next week, I’d be sorely tempted to bop down to the Bay Area for the event.

This evening marks the close of “Types We Can Make,” an exhibition at Swissnex of “new typographic works from Switzerland.”

Swissnex is conveniently located just up the street from William Stout Architectural Books, which is a dangerous place to enter if you’re a bibliophile, especially if your vulnerability is in the line of architecture, typography, or graphic design. You’ve been warned.

New: Check out this very nicely done short video of Jack talking about his creative working methods and interacting with people at last week’s event.

[Photo: Jack Stauffacher at the AIGA National Design Conference in Vancouver, B.C., October 2003.]

Categorized as book design, culture, events, printing, typography |

Last weekend I was in San Francisco for TYPO SF, the first episode of FontShop’s ongoing series of Typo conferences to be held in North America. I’ve written about it, briefly, for the Eye magazine blog, but of course there’s always more to say.

The only other Typo conference I’ve been to was Typo Berlin, back in 1999. There’s plenty of continuity, of course, starting with the fact that the overall organizers are the same (though the hands-on organizers, Michael Pieracci and Meghan Arnold, were local, and no doubt too young to have organized a type conference thirteen years ago; they certainly seemed to know what they were doing, though). Deeper continuity and context was provided on Friday afternoon by Neville Brody, who put the whole event into perspective by referring to Typo’s antecedents in the first FUSE conference, in London in 1994, and the second one, right there in San Francisco in 1998. I heard echoes of some of the themes and ideas that I remembered hearing from Neville and from Jon Wozencroft in those heady days, though perhaps with less of the stirring call to arms. (I had to leave before the end of Neville’s talk, but if there was any overt barricade-storming, I didn’t hear about it later.)

Erik Spiekermann, Jan Abrams, and Kali Nikitas took turns with the mastering of ceremonies, presenting a seamless front end; I know that both Kali and Jan took pains to find out context and interesting insights for the speakers they didn’t already know, and I think that care paid off in how well integrated it all felt to the audience.

From a speaker’s perspective, I can say that TYPO SF was very well organized. There is inevitably a divide between the speakers and the audience, more so than at a smaller professional conference like ATypI or TypeCon, but I felt it less this time than I remember feeling at Typo Berlin. There was a lot of interaction, good conversation, and sparking of fresh ideas. I know I came away from Typo SF with some new contacts and a lot of new energy.

[Photo: a snapshot taken by Chuck Byrne during my talk]

Categorized as events, typography |

Books are digital. This is not, strictly speaking, true; but it’s about to be, with a few honorable exceptions. Already today, pretty much all commercial books are produced digitally, although the end product is a physical one: ink printed on paper, then bound and marketed and sold. Already, the selling may be done as often online as in a bookstore. Already, the same books are being issued more and more in electronic form – even if, as yet, the e-books are mostly very shoddy in conception and execution.

But that will change. In order for it to change in a worthwhile way, we have to spell out just what form these books ought to take.

So what’s needed? How do we make good e-books? What should a good tool for designing and creating e-books look like and do? What should the result – the e-book itself – be capable of? And what should the experience of reading an e-book be like?

Last question first. If it’s immersive reading – a story or narrative of some kind – then you, as the reader, should be able to lose yourself in the book without thinking about what it looks like or how it’s presented. This has always been true for printed books, and it’s equally true for e-books.

But e-books present a challenge that printed books do not: the page isn’t fixed and final. At the very least, the reader will be able to make the font bigger or smaller at will, which forces text to reflow and the relative size of the screen “page” to change. That’s the minimum, and it’s a fair bet already today. But the reader many read the same book on several different devices: a phone, a laptop, a tablet, a specialized e-reader, or even the screen of a desktop computer.

For a real system of flexible layout in e-books and e-periodicals that might be viewed on any number of different screens at different times, what’s needed is a rules-based system of adaptive layout. I like to think of this as “page H&J”: the same kind of rules-based decision-making on how to arrange the elements on a page as normal H&J uses to determine line endings.

The requirements for this are easy to describe – maybe not so easy to implement. We need both design & production tools and the reading software & hardware that the result will be displayed on.

A constraints-based system of adaptive layout

The interesting problems always come when you have two requirements that can’t both be met at the same time. (For example: this picture is supposed to stay next to that column of text, but the screen is so small that there isn’t room for both. What to do?) That’s when you need a well-thought-out hierarchy of rules to tell the system which requirement takes precedence. It can get quite complicated. And the rules might be quite different for, say, a novel, a textbook on statistics, or an illustrated travel guide.

OpenType layout support. This means support for the OpenType features that are built into fonts. There are quite a few possible features, and you might not think of them as “layout”; they affect the layout, of course, in small ways (what John Hudson has called “character-level layout”), but they’re basically typographic. Common OpenType layout features include different styles of numerals (lining or oldstyle, tabular or proportional), kerning, tracking, ligatures, small-caps, contextual alternates, and the infinitely malleable “stylistic sets.” In complex scripts like Arabic, Thai, or Devanagari, there are OpenType features that are essential to composing the characters correctly. None of these features are things that a reader has to think about, or ought to, but the book designer should be able to program them into the book so that they’re used automatically.

Grid-based layout. It seems very obvious that the layout grid, which was developed as a tool for designing printed books, is the logical way to think about a computer screen. But it hasn’t been used as much as you’d imagine. Now that we’re designing for screens of varying sizes and shapes, using a grid as the basis of positioning elements on the screen makes it possible to position them appropriately on different screens. The grid units need to be small enough and flexible enough to use with small text type, where slight adjustments of position make a world of difference in readability.

Media query. This is the name used for the question that a program sends to the device: What kind of device are you? What is the resolution of your screen? How big is that screen? What kind of rendering system does it use for text? With that information, the program can decide how to lay out the page for that screen. (Of course, the device has to give back an accurate answer.)

Keep & break controls. These are rules for determining what elements have to stay together and what elements can be broken apart, as the page is laid out. This means being able to insist that, say, a subhead must stay with the following paragraph on the page (keep); if there isn’t room, then they’ll both get moved to the next page. It also means that you could specify that it’s OK to break that paragraph at the bottom of the page (break), as long as at least two lines stay with the subhead.

Element query. I’ve made up this term, but it’s equivalent to media query on a page level. The various elements that interact on a page – paragraphs, columns, images, headings, notes, captions, whatever – need a way of knowing what other elements are on the page, and what constraints govern them.

H&J. That stands for “hyphenation and justification,” which is what a typesetting program does to determine where to put the break at the end of a line, and whether and how to hyphenate any incomplete words. Without hyphenation, you can’t have justified margins (well, you can, but the text will be hard to read, because it will be full of gaping holes between words – or, even more distracting, extra spaces between letters). Even unjustified text needs hyphenation some of the time, though it’s more forgiving. When a reader increases the size of the font, it effectively makes the lines shorter; if the text is justified, those gaps will get bigger and more frequent. But there are rules for deciding where and how to break the line, and a proper H&J system (such as the one built into InDesign) is quite sophisticated. That’s exactly what we need built into e-book readers.

In digital typesetting systems, the rules of H&J determine which words should be included on a line, which words should be run down to the next line, and whether it’s OK to break a word at the end of the line – and if so, where. A system like InDesign’s paragraph composer can do this in the context of the whole paragraph, not just that one line. A human typesetter makes these decisions while composing the page, but when the font or size might be changed at any moment by the reader, these decisions need to be built into the software. In “page H&J,” where the size and orientation of the page itself might change, the whole process of page layout needs to be intelligent and flexible.

Up until now, in the digital work flow, the software’s composition engine has been used in the creation of the published document; the human reader is reading a static page. But now, with flexible layout and multiple reading devices, the composition engine needs to be built into the reading device, because that’s where the final page composition is going to take place.

It’s easy to create a document with static pages that are designed specifically for a particular output device – a Kindle 3, for instance, with its 6-inch e-ink screen, or a 10-inch iPad. I’ve done it myself in InDesign and turned the result into a targeted PDF. But if that’s your model, and you want to target more than one device, you’ll have to produce a new set of static pages for each different screen size and each different device. Wouldn’t it be better to have a flexible system for intelligently and elegantly adapting to the size, resolution, and rendering methods of any device at all?

[Photo: a 17th-century Mexican handbook, about the size of a hand-held device, from the collection of the Biblioteca Palafoxiana, displayed during Typ09 in Mexico City. With ink show-through from the back of the page, which will probably not be a feature of e-books.]

Categorized as book design, books, editorial design, onscreen design, publishing, tech, typography |

’Tis the season for backwards apostrophes. The web, and the pages of magazines, are full of variations on the phrase ’tis the season, half of which have the apostrophe backwards (like the example at left) – presumably because someone just typed an apostrophe on the keyboard and their software helpfully turned it into a single open quotation mark. But that ain’t an apostrophe. The apostrophe, like the comma, only faces one way. Pay attention, please, and get it right!

(Not sure how to get the right glyph? Copy and paste it from someplace else. If your software is giving you an open single quote, just type an apostrophe at the end of the word, where it’ll face the right way; then delete that and paste it at the front.)

[Images: from the holiday-season home page of lee.com – hardly the only high-profile retailer to make this mistake.]

Categorized as advertising, foibles, typography |

Two intelligent blog posts appeared today covering the new iBooks software and its choice of fonts; both of them included a link to my 2001 review of one of the new type choices: Iowan Old Style. I’m pleased to see John Downer’s Iowan Old Style get its due at last; I’m even more pleased to see iBooks expand its typographic palette in the direction of actual text typefaces. (Now about actual typography…)

Glenn Fleishman’s essay for Boing Boing is insightful and mindful of the cyclical development of typographic technology; he also mentions the current problems with trying to incorporate web fonts in e-books. Yves Peters in the FontFeed has more to say about the history of the typeface designs, and his illustrations cleverly show the fonts in all three of iBooks’ screen views or “themes.”

What I don’t understand is why Apple chose to drop three of the previous iBooks fonts (Cochin, Baskerville – really Monotype Baskerville – and Verdana). None of them were ideal for books onscreen, but why reduce the choices instead of simply adding to them?

And now the newly introduced Seravek is the only sans serif font available for reading in iBooks. It’s a nicely designed humanist sans, but it doesn’t have to be the only sans, humanist or otherwise, on the system. And the small eyes of Seravek’s e and a tend to visually close up under some circumstances.

[Image: one of the illustrations from Yves Peters’ review, showing Iowan Old Style. In the FontFeed original, you can click on any of the three sections to see the full page in that view.]

Categorized as book design, books, fonts, onscreen design, typography |

Thomas Phinney wrote a thoughtful blog post last week about “The Impact of Steve Jobs on Typography”: about how the Mac pioneered proportional fonts on the screen, and how the combination of Aldus PageMaker and the LaserWriter created desktop publishing; and about a host of later improvements and developments: “Being able to see what fonts look like on screen. Showing proportional fonts on screen. Scaling the same font outlines for screen as for print. Putting a ‘font’ menu in applications, and having all applications share a pool of fonts installed at the system level (instead of associated with some specific printer).” Jobs was famously attentive to details; more to the point, he was famously attentive to the details of design. His flare and care for industrial design made Apple’s products desirable – and usable.

Which is why I’ve always been disappointed that Apple doesn’t bring that same level of perfectionism to its use of type. The graphic design, both in Apple’s marketing and in its products themselves, is always careful and clean; but the choices of fonts have been erratic, and they’re not always used consistently. Just looking at a current page of the Apple website, about Mac products, I see both their corporate font, Myriad, and the current Mac user-interface font, Lucida Grande. Both are well-designed humanist sans-serif typefaces, and either one works well; they actually play together better than you would think, but it’s still subtly jarring to see two competing sans serifs on the same page. But that’s not all.

Ever since the introduction of the iPhone, Apple has been moving toward using versions of Helvetica on screen. I’ve written before about the problem with reading numbers in Helvetica. The same repetition of shapes that makes Helvetica look consistent and “modern” (or at least retro-modern) creates ambiguity and makes it all too easy to mistake one number or letter for another. As Thomas Phinney said in a comment on his own post, “I love iOS, but I am still horrified that it uses Helvetica as a UI font.”

Categorized as advertising, foibles, fonts, onscreen design, typography |

By all accounts, this year’s ATypI conference was a notable success. People kept coming up to me and telling me how much they were enjoying the event, how impressive the venue was, how well everything was organized, how intelligent the talks were, how much they liked the food. I kept telling them that I couldn’t take any credit for these things, that it was the organizers, both local and from ATypI, who had brought all this together. But it was certainly gratifying to hear.

The venue was spectacular: a brand-new building, Harpa, built right on the edge of the waterfront in the harbor of Reykjavík, which houses the national symphony as well as serving as a state-of-the-art conference center. Harpa’s irregular geometry and fishnet-over-glass windows all around highlighted the location and gave us a light, airy interior to inhabit and meet in. Its various meeting spaces were easy to configure for both talks and meals. And when the weather got bad – Sunday saw a good bit of wind and rain – it was satisfying to sit snug in Harpa and gaze out at the wind-whipped harbor.

There were fewer attendees than usual this year (no doubt a reflection of the dismal economy, and of the fact that while Reykjavík is easily accessible from both North America and Europe, it’s not exactly local to anyone but the Icelanders). But those who came were excited and stimulated, and came away talking about ideas.

How often do you have a head of state opening a typography conference? The President of Iceland, H.E. Ólafur Ragnar Grímsson, not only welcomed ATypI to Iceland but gave a twenty-minute talk about the Icelandic language and its typography – an intelligent, eloquent commentary that set a high standard and neatly prefaced our keynote speaker, Gunnlaugur SE Briem. Briem spoke wittily about type, letters, and language. Together, they kicked off the main conference brilliantly.

The theme of the Icelandic letter “eth” (ð, the voiced “th” sound found in English too) led naturally to a rich track of talks on other special characters, and on a wide range of non-Latin writing systems as well. We heard about the typography of Indic, Korean, Arabic, Mongolian, Chinese, and Khmer scripts, not to mention Danish, Irish, German, and Turkish letters within the Latin alphabet. The number of presentations on Indic typography on Sunday was particularly appreciated; and there was talk of making a proposal in a few years for holding an ATypI conference somewhere in India.

The structure this year seemed to work quite well: two preliminary days of workshops and technical and educational items, in two parallel tracks, followed by the official opening on Thursday night and then a single main track of programming on Friday, Saturday, and most of Sunday. This allowed for specialization in the preliminary days, but a common experience during the main conference – and no running around trying to switch from one track to another, or worrying about coordinating the timing between multiple simultaneous talks. Our program structure is partly determined by the venue, but I think we’ll try to repeat this success in the future.

Saturday night we clambered into city buses for a short ride out of town to a penthouse restaurant with wide views in all directions, where the restaurant’s staff were quickly accommodating when they discovered that we had more people for dinner than we had planned. That was followed by a crowded party back in town at the Icelandic Design Centre, and the usual dispersal to the bars of downtown Reykjavík.

The city is so small that it was easy to keep running into each other; at one point, one of the pleasant local bars was entirely filled with typographers. This also meant that no matter where you were staying, it wasn’t more than a walk away from the conference venue. So not only did Harpa provide excellent spaces for talking and mingling, but the city itself contributed to this lively interpersonal dynamic. Reykjavík is a very cozy capital.

For a flavor of the event, check out write-ups by Roger Black on his blog (“We are all one culture, here on Œŧħ. We’ve just taken different glyphs”) and by Dan Reynolds on ilovetypography (“Font editors & a book steal the show”), and scan the photos from various attendees on Flickr. (I’d be happy to hear of other reports that I’ve missed.) And take a look at the impressionistic, kaleidoscopic videos put together by a group of young Icelandic filmmakers who were roaming the conference, cameras in hand.

[Photos, top to bottom: the exterior of Harpa, with pool in front; the interior of Harpa, looking out; the bar before Saturday’s gala dinner; Thomas Phinney and Dawn Shaikh, at the pub; Mark Barratt and Dave Crossland, suitably out of focus, at another pub; Nick Sherman’s sartorial splendor (what, no hoodie?); and one of the images from the Typographer’s Guide to Iceland.]

Categorized as architecture, education, events, fonts, type designers, typography |