Tag Archives: layout

The performance of a text

Originally published on The Editors’ Weekly, the national blog of Editors Canada

If someone says “How about some music,” and you say “Sure – Beethoven’s fifth?” do you think they’ll be happy if you just hand them a printed copy of the score?

A musical score is intended to be performed, and you don’t have a performance without musicians and a conductor – and the stage and lighting crew. And any two performances will be different, at least slightly and sometimes significantly.

A novel or a short story – or a nonfiction book or article – is, on the other hand, a finished work. You sit down, you read it, you get the same thing every time. Right?

Ha, no.

We’re all editors here, so we know how many pairs of eyes and hands have worked on a text before it’s published. But we might casually assume that once the wording is finalized and all the errors are fixed, the text is done and all printed versions are fungible.

Even though we know it’s not true.

We know it’s not true because we know that reading a nicely laid-out print magazine version of an article is a different experience than reading a text flow of it on a website. We know, if we’re proofreading, what a difference some seemingly small things can make – misalignments, for instance, or bad breaks.

And we also know it’s not true because when we’re shopping for books, if there are several different editions of the same work, we will choose carefully between them. Just as we may choose between a performance of Beethoven’s 5th that is fast-paced and percussive and one that is more stately and smooth, we may likewise choose carefully between two editions of, say, Jane Eyre. One of them might be on pulp paper in a casewrap hardcover with a photo on the cover and a small, tight type face with narrow margins and no paragraph indents, while the other might be a trade paperback with a stylish minimalist cover, creamy, durable paper, and well-set type in a graceful face. You’ll get the same story, sure, but you won’t get the same feeling from reading it – about the story or about yourself.

A book is a performance of a text. So is a magazine layout of an article. So is this website’s presentation of this article you’re reading now.

Different performances differ in so many details. If it’s a website, are there pictures? How wide is the text column? Is it cluttered with ads? What font is it in? If it’s a book, does it feel cheap or luxurious? Is it light or heavy, soft or hard? What does the cover look like? Do you like the type face? Is it easy to read in low light? Do the pages turn easily? And, for heaven’s sake, how does it smell?

Does all this seem peripheral to the actual text? Tell me this, then: if you’re buying an audiobook, does it matter whether it’s read by Benedict Cumberbatch or Tom Waits? Helen Mirren or Siri? You’re getting the same story, right?

Sure you are. But a different performance. And the difference between type faces in which you read Sherlock Holmes stories can be as affecting as the difference between Jeremy Brett’s Sherlock and Basil Rathbone’s. The difference in page layout, paper, and binding can make as much difference as the set design of a production of a play. The page is a stage – or a concert hall.

Well Begun Is Nearly Done: Desktop publishing workflow at warp speed

Presented at the 32nd annual Editors’ Association of Canada conference, Vancouver, May 29, 2011

It’s a long time ago, in a galaxy far, far away. The three humans, two droids, and one wookiee on the Millennium Falcon are being attacked by Imperial cruisers. They can escape by jumping into hyperspace. But the pilot, Han Solo, is taking time getting coordinates from the navi-computer. As laser blasts hit, Luke Skywalker shouts, “Are you kidding? At the rate they’re gaining…”

And Solo replies, “Traveling through hyperspace isn’t like dusting crops, boy! Without precise calculations we could fly right through a star or bounce too close to a supernova and that’d end your trip real quick, wouldn’t it?”

 

It’s this week, in an office all too close to home. A project is on a tight deadline. You have the workflow and the people lined up, but you’re taking time making sure that everything is set up the right way in the layout… and the source file… As the telephone is ringing off its hook, your project manager shouts, “Are you kidding? We don’t have time for niceties like that! Just make it happen!”

And you reply, “Desktop publishing isn’t like using a typewriter. Without setting it up the right way, we could get nailed and waste hours redoing everything when the client wants to change some element of the look late in the game. And you know they will. And that would take us way over time and budget, wouldn’t it?”

 

You’ve probably heard your mother or teacher or some similar person say, “Well begun is half done.”

Well, when it comes to desktop publishing, well begun is really a lot more than half done. Continue reading