categories
archives
rss

typographic design for new reading spaces

About a decade ago, I addressed an audience of typographers at the Atypi conference in Lyon, France, with a question: why do type designers invest so little research and creative energy in the computer screen as a medium and in designing fonts for it? The usual answer was that the screen is not worthy of their detailed skills until it can match the high definition and resolution of printed matter – which won’t happen in their life time. While that remains to be seen, it was in my view not the only or even the most pressing problem.

The problem was – and is – that forms in ink on paper are quite different beasts than similar forms projected by electrons on the back of light-emitting screens. Ten years have passed, and although content that is meant for the screen these days often actually looks like it’s made for it rather than for paper, the typefaces we are supposed to read in this medium have not changed much. A case in point is Limited Language’s screen typeface, Monaco, a monospace font that works pretty well in fairly large sizes in print but is literally an eyesore when used for reading on screen.

But there’s more: how these typefaces behave in the versatile and interactive environment they live in has hardly been addressed in terms of typographic design. Yes, one can click on words and something will happen, type is twisting and turning in animated headlines, and you can change its size in webtexts for better reading. But that’s not exactly what I meant, although some of it helps. Designing typefaces that are tailored to the peculiarities of the screen is a growing concern for designers, and some are doing an excellent job making them work. But typographing texts in a way that addresses the actual potential of the medium they are published in is something else.

There have emerged new ‘reading spaces’, that are incomparable with the traditional paper ones, but still behave like they were made by Gutenberg. New portable ‘e-readers’ like Amazon’s Kindle or the iLiad are state-of-the-art gizmos that still mimic a paper page’s format, albeit of a one-page-fits-all kind. The notion that one can manipulate the appearance and behaviour of text on screen still has had no serious consequences in any generally distributed medium, including the web. The simple idea that text – not necessarily the content it carries, but its formal structure and the way it is accessed – can be laid-out in variable ways to be triggered situatively by the reader has been only marginally worked out in mainstream on-screen media, in what we could call ‘template culture’. What we see as ‘interactive text’ is mostly functional text, i.e. text that functions in verbal wayfinding within websites and on-screen forms and menus. You click a word, and a list of subcategories appears. You mouse over a word or an image, and an explanatory line or paragraph pops up.

Such ubiquitous functionality could be used for richer purposes than mere informational messages; it could be used as integral part of a text, and of the reading experience it offers. The standard hierarchies of text in print media – headline, chapeau, introduction, main text, footnotes, captions – can function in a totally different way in on-screen media. There, if need be, and if the author sees it as an interesting way of communicating, each letter could spawn an endless variety of text formats. A summary statement could give access to deeper layers of argumentation and reference within the same ‘page’. An image could morph into its own description – or vice-versa. A question or argument could become surrounded by answers or counter arguments. A text could give more or less detail, depending on the reader’s behaviour…

There are, of course experiments that explore such new functionality and new reading spaces. In 2003, I initiated a few of them with designer and Javascript maverick Joes Koppers. Usetext (usetext.com) was an attempt to make use of the specific potential of on-screen text: A short text is readable as such, but each line also functions as an interface into what’s, literally, behind the lines. I used the application for instance to write my introduction to an online story by Young-Hae Chang Heavy Industries’, ‘View and plan of Seoul’. The introduction, ‘Starbucks with Victoria’, is both an appetizer and a critique of sorts, as well as a pastiche of Chang’s signature style in a different medium. And in the web version of my editorial for Items no.1, 2009, I used another Koppers script to realize the movement of the quotes bursting out of the main text, which could only be suggested by the lay-out of the printed magazine spread.

While such experiments remain modest in scope and design, they do, in my view, give an indication of the potential of the screen as an interesting and engaging medium for reading. Readers, of course, will have to do their part: actively ‘feeling’ a text for interactive response, rather than duly clicking links. But readers won’t move a finger until designers present them with an invitation: to explore a text’s behaviour and expect it to answer in ways that are unthinkable on paper. In other words, designers should explore the medium to find reasons for readers to not print out a text they find online. Reading on screen can be a rewarding experience in stead of an eye soaring exercise.

Max Bruinsma is Editor in Chief of Items design magazine, the
Netherlands, and Editoral Director of ExperimentaDesign, Portugal.

 

13 comments

I have enjoyed Young-Hae Chang Heavy Industries for a while. It is an interesting approach to work because it’s visually powerful. Here usual work is very didactic: Hey you! it’s the ’sit back and watch my text at my pace set to the slightly pacy beat of my music’ approach to reading which is both energising and tiring. I have also seen it at the Becks digital animation display in Trafalgar Q=Square in London where, on an ambient surround screen, it became like the visual equivalent of lounge music. So far, getting less interesting. I do think working with her is interesting because so far she brings the linear approach of print to seductive technology but nothing more. I like the idea of calling text to you to make it active. But it also makes me feel a bit epileptic-type sick.

/Alistair Johns 28/03/2009

 

Anj Rau is quite interesting here… she’s a writer of hyper fiction and she reminds us of the ‘active reader’ as thought out in Roland Barthes’ concept of the readerly and writerly text. “Hypertext (fictional or non-fictional) is said to activate the reader who has to realize the text in reading it.”

So we are activated. And of course, there is a playful lure in this technology… But whilst it’s ‘interesting and engaging’ - yes – and it might get us not to print out – a good thing I guess – but how will it change the way info sinks in. Playing with reading, being teased by it, is it too distracting?

/Ruth Ellery 28/03/2009

 

what i think is most important is that you offer it to others to use. Experimentation needs to be fed back to your site though, so we can see how others further your project Max?

/John R 28/03/2009

 

Ruth - I think the idea that everything is ‘distracting’ etc. is too often used. Remember (or not!) that Plato made massive objections to writing - that it was inhuman, outside the mind, destroys memory etc. If we keep in mind what this new way of setting text makes possible, new ways of writing and thinking overall may be instigated. Plato might have been right about memory, but he didn’t see what the need ‘not to remember’ might allow.

/Alistair Johns 31/03/2009

 

READ THIS WORD by Vito Acconci (1969)

READ THIS WORD THEN READ THIS WORD READ THIS WORD NEXT READ THIS WORD NOW
SEE ONE WORD SEE ONE WORD NEXT SEE ONE WORD NOW AND THEN SEE ONE WORD AGAIN
LOOK AT THREE WORDS HERE LOOK AT THREE WORDS NOW LOOK AT THREE WORDS NOW TOO
TAKE IN FIVE WORDS AGAIN TAKE IN FIVE WORDS SO TAKE IN FIVE WORDS DO IT NOW
SEE THESE WORDS AT A GLANCE SEE THESE WORDS AT THIS GLANCE AT THIS GLANCE
HOLD THIS LINE IN VIEW HOLD THIS LINE IN ANOTHER VIEW AND IN A THIRD VIEW
SPOT SEVEN LINES AT ONCE THEN TWICE THEN THRICE THEN A FOURTH TIME A FIFTH A
SIXTH A SEVENTH AN EIGHTH

We thought this would be a brilliant piece to try and explore using Max’s Usetext tools.

You can also read further on Acconci here: Craig Dworkin (ed.), Language to Cover a Page: The Early Writings of Vito Acconci Vito Acconci (MIT, 2006) http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&tid=10781

/Colin + Monika (Limited Language) 05/04/2009

 

Vito Acconci’s piece is brilliant indeed, and looks like it’s made for ‘Usetext’. So, of course, I made a usetext version of it - thanks C+M to challenge me ;-) Interesting here is another aspect of using a medium like this, or translating a text that seems to be written as one flow of words (capitalized letters, actually) to a medium that paces the reading in a different way. I had to decide where the line breaks will be, and thus my version is an interpretation as much as it is a transcription.
As for the distractive aspect of reading within such dynamic interfaces, I’d say that the reader has to adjust to taking in more information than they usually do; the visual aspect (the movement, the interplay of layering words and letters, the appearance and disappearance of words…), which in printed text is normally non-existent, disregarded or at least non-essential, here affects the meaning of the text much more directly. So it needs to be read as well as the verbal content. In my view, the interplay of the dynamic elements works very well in Acconci’s text.
This points to another important challenge the kind of dynamic reading media I am advocating poses to writers: to write with the medium in mind. Acconci’s piece is a rare example of a text that can be fruitfully adapted to Usetext, but it’s pretty hard to write effectively in this way, as I’ve found out myself ;-)

/Max Bruinsma 10/04/2009

 

MB - That’s actually great. It’s not distracting, as I thought it might be. I tell you why… because it’s sexily slow. I haven’t said that about typography before. I’ll go now…

/Ruth Ellery 10/04/2009

 

Thank you for your experiments: I’m excited by them, & interested in them. Certainly I’ve thought of recent projects (architecture & design) of Acconci Studio’s as places to play with & change & revise. I don’t know if, at the time of my early work, my poetry, I was ready to think that way: I’m glad you did it for me. (Coincidentally, lately, I’ve been doing something like this myself: for some recent art auctions, I’ve taken blown-up versions of some of my early poems & played with them, made them more graphic – took them, in other words, as raw material, which is what I’m glad to see that you have done, too.)

http://www.acconci.com/

/Vito Acconci 13/04/2009

 

Thanks for the compliment, mr. A.! I must admit that I was a bit shy to do this, because obviously, I had to enter into the very structure of the text, which is something one is not supposed to do with poetry. Transposing Acconci’s text to Usetext, there appears an altogether new poem at the first level – seven lines (as Acconci suggests himself in his text, so I felt I may render it this way…). In a sense, I did take the lines and words as raw material, but at the same time tried to stay as close as possible to what I saw as the essence of the poem. But there’s no way around the fact that my edit is an interpretation. That’s of course also the fun of it ;-)
As for the slowness, that’s an interesting aspect. Varying the pace is a potentially very effective way of enhancing the reading experience, and a means to guide the reader’s interpretation (an extension of typographic enhancements such as bold or italics). I’ll ask the author of the javascript, Joes Koppers if he can add a slider to the interface so you can define the speed and movement of a line as it comes into view…

/Max Bruinsma 13/04/2009

 

I think the slider idea is interesting because it gets away from the issue of reading to another’s pace (already brought up with Young-Hae Chang Heavy Industries.

/Alistair Johns 13/04/2009

 

Max, one practical answer to your question ‘why do type designers invest so little research and creative energy in the computer screen as a medium and in designing fonts for it?’ is that both the technologists and the intellectual property interests involved have been opposed to solving issues with the embedding of fonts. Although font embedding formed part of the CSS2 standard, published in 1992, it seems to have taken an inordinate amount of time to get Microsoft’s Embedded Open Type format accepted as a standard – and for it to be incorporated into browsers rendering engines. More problematic still, however, is that the various type foundries’ End User Licence Agreements prohibit any form of font embedding – and there is still widespread concern about security and ‘revenue protection’ issues amongst type designers. Few have taken the approach of Jos Buivenga of making fonts available in EOT format (and Buivenga is something of an exception anyway, since he has put his designs into the public domain). From what I understand, Microsoft’s WEFT tool – which is required to convert fonts to EOT format - is also extremely difficult to use.

I also tend to disagree with your thesis ‘that forms in ink on paper are quite different beasts than similar forms projected by electrons on the back of light-emitting screens’. That may have been the case once, with low resolution displays - and it may still be true for certain applications (like mobile phones – but the iPhone seems to be redefining that area too). Developments like ClearType also moved on-screen rendering forward within existing resolutions. I can hardly see the pixels any more on my MacBook screen – and since I started needing reading glasses, small type on screen is as nonsensical as small type on the back of a shampoo bottle. At ‘readable’ sizes, type on screen has a recognisable integrity and continuity of form with type off screen. I’m sure, too, that higher and higher resolution displays will wipe away this distinction altogether.

Finally, it’s also worth adding that the overcoming of technical challenges for non-Latin scripts seems to be changing the way designers are now creating Latin types. The need to support extensive glyph substitution necessary for, say, Arabic, means that Western type designers are able to exploit extensive glyph substitution in their fonts - the work of Ale Paul with scripts is a good example. This is harnessing the power of computers without submitting to their limitations. And it is interesting to me that, again, Middle Eastern graphic design is going through this fantastic creative period, having effectively missed out the pixellation, ‘screen type isn’t print type’, stage altogether.

/james souttar 18/04/2009

 

Thanks James for your comments,

Here is some of Ale Paul’s workshop photos for anyone who is interested: http://www.flickr.com/photos/17849178@N00/page2/

Talking of type forms on screen being different/similar to ones on paper: I’m not sure I agree with your point that higher and higher resolution screens will wipe away distinctions. Marshall McLuhan suggested there was a difference between ‘light-on’ and ‘light-through’ technology, the latter of which mesmerises us (stained glass windows, tv and now the computer screen are light-through. Can resolution resolve this?

Also, I am quite interested in this issue of type as an interface. There is a difference on screen to print: for, when we think of printed type as an interface this operates at the how it facilitates communication between people. But when we think of screen type like this, it’s also an interface between spaces (as different layers of text reveal and hide themselves) and different temporal modes (this issue of how fast or how slow).

/Monika (Limited Language) 21/04/2009

 

In November 2009 we released the book ‘Limited Language: Rewriting Design: Responding to a feedback culture’ which re-engaged with this original post.

For more on the book as a whole: http://bit.ly/bookcomments

Monika + Colin

/colin 15/11/2009

 

write a comment

we encourage people to recycle your comments in their own research as we may collage them into our own writing with the aim to publish the resulting articles (any post eventually used will be credited). We encourage comments to be 200 words or more.

line and paragraph breaks automatic. e-mail address will never be displayed. html allowed: <a href=""> <b> <blockquote cite=""> <em> <i> <strike> <strong>