a book is not a text: the noise made by people 09.23.2005, 6:13 PM
posted by dan visel
Momus – a.k.a. Nick Currie, electronic folk musician, Wired columnist, and inveterate blogger – has posted an interesting short video on his blog, Click Opera. He's teaching a class on electronic music composition & narrative for Benneton's Fabrica in Venice. His video encourages students to listen for the environmental sounds that they can make with electronic instruments: not the sounds that they're designed to make, but the incidental noises that they make – the clicking of keys on a Powerbook, for example – that we usually ignore as being just that, incidental. We ignore the fact that these noises are made directly by people, without the machine's intercession.
Momus's remarks put me in mind of something said by Jerome McGann at the Transliteracies conference in Santa Barbara last June – maybe the most important thing that was said at the conference, even if it didn't warrant much attention at the time. What we tend to forget when talking about reading, he said, was that books – even regular old print books – are full of metadata. (Everybody was talking about metadata in June, like they were talking about XML a couple of years ago – it was the buzzword that everyone knew they needed to have an opinion about. If not, they swung the word about feverishly in the hopes of hitting something.) McGann qualified his remarks by referring to Ezra Pound's idea of melopoeia, phanopoeia, and logopoeia – specific qualities in language that make it evocative:
. . . you can still charge words with meaning mainly in three ways, called phanopoeia, melopoeia, logopoeia. You can use a word to throw a visual image on to the reader's imagination, or you charge it by sound, or you use groups of words to do this.
(The ABC of Reading, p.37) In other words, words aren't always just words: when used well, they refer beyond themselves. This process of referring, McGann was claiming, is a sort of metadata, even if technologists don't think about it this way: the way in which words are used provides the attuned reader with information about their composition beyond the meaning of the words themselves.
But thinking about McGann's comments in terms of book design might suggest wider implications for the future of the book. Let's take a quick excursion to the past of the book. Once it was true that you couldn't judge a book by its cover. Fifty years ago, master book designer Jan Tschichold opined about book jackets:
A jacket is not an actual part of the book. The essential portion is the inner book, the block of pages . . . [U]nless he is a collector of book jackets as samples of graphic art, the genuine reader discards it before he begins.
("Jacket and Wrapper," in The Form of the Book: Essays on the Morality of Good Design) Tschichold's statement seems bizarre today: nobody throws away book jackets, especially not collectors. Why? Because today we take it for granted that we judge books by their covers. The cover has been subsumed into our idea of the book: it's a signifying part of the book. By looking at a cover, you, the prospective book-buyer, can immediately tell if a recently-published piece of fiction is meant to be capital-L Literature, Nora Roberts-style fluff, or somewhere in between. Contextual details like the cover are increasingly important.
Where does the electronic book fit into this, if at all? Apologists for the electronic book are constantly about the need for an ideal device as the be-all and end-all: when we have e-Ink or e-Paper and a well-designed device which can be unrolled like a scroll, electronic books will suddenly take off. This isn't true, and I think it has something to do with the way people read books, something that hasn't been taken into account by soi-disant futurists, and something like what Jerome McGann was gesturing at. A book is not a text. It's more than a text. It's a text and a collection of information around that text, some of which we consciously recognize and some of which we don't.
A few days ago, I excoriated Project Gutenberg's version of Tristram Shandy. This is why: a library of texts is not the same thing as a library of books. A quick example: download, if you wish, the plain text or HTML version of Tristram Shandy, which you can get here. Look at the opening pages of the HTML version. Recognizing that this particular book needs to be more than plain old seven-bit ASCII, they've included scans of the engravings that appear in the book (some by William Hogarth, like this; a nice explication of this quality of the book can be found here). What's interesting to me about these illustrations that Project Gutenberg is how poorly done these are. These are – let's not beat around the bush – bad scans. The contrast is off; things that should be square look rectangular. The Greek on the title page is illegible.
Let's go back to Momus listening to the unintentional noises made by humans using machines: what we have here is the debris of another noisy computer, the noise of a key that we weren't supposed to notice. Something about the way these scans is dated in a very particular way – half of the internet looked like this in 1997, before everyone learned to use Photoshop properly. Which is when, in fact, this particular document was constructed. In this ugliness we have, unintentionally, humanity. John Ruskin (not a name often conjured with when talking about the future) declared that one of the hallmarks of the Gothic as an architectural style was a perceived "savageness": it was not smoothed off like his Victorian contemporaries would have liked. But "savageness", for him, was no reproach: instead, it was a trace of the labor that went into it, a trace of the work's humanity. Perfection, for him, was inhumane: humanity
. . . was not intended to work with the accuracy of tools, to be precise and perfect in all their actions. If you will have that precision out of them, and make their fingers measure degrees like cog-wheels, and their arms strike curves like compasses, you must unhumanize them . .
(The Stones of Venice) What we have here is, I think, something similar. While Project Gutenberg is probably ashamed of the quality of these graphics, there's something to be appreciated here. This is a text on its way to becoming a book; it unintentionally reveals its human origins, the labor of the anonymous worker who scanned in the illustrations. It's a step in the right direction, but there's a great distance still to go.
Posted by dan visel on September 23, 2005 6:13 PM
tags: Transliteracies, book, design_curmudgeonry, digital_literature, ezrapound, gutenberg, jeromemcgann, johnruskin, logopoeia, mcgann, melopoeia, momus, phanopoeia, ruskin, text, tschichold
ben vershbow on September 23, 2005 7:03 PM:
Here here. Robert Bringhurst's insistence on the humanity of typographic fonts echoes Ruskin. What is encouraging is that one can imagine an earlier point in history when it seemed that typography would steal the spirit of the handwritten word. But over time, we came to recognize the savageness that lived in printed lines.Today, the electronic page seems similarly inhuman. But if we are open, and perhaps do not look at things head on, but rather around the side, we begin to perceive the human mark. Can you grab those Gutenberg scans? We should put them up.