Wednesday, February 03, 2010

Compulsion at Yale Rep

NOTE: This is a review of a play that officially opens tomorrow. The play, a co-production of the Yale Repertory Theatre, the Public Theater (in New York), and the Berkeley Repertory Theatre, is scheduled to tour nationally. Because the performance I attended was technically a preview of the show’s world premiere run, it is possible—likely—that changes will be made (gawd, I hope so) before tomorrow’s opening or at least before it reaches a stage near you, wherever you are.

Oy! Where to begin
Okay, I may as well tell you what the play is about, first. Meyer Levin’s book, Compulsion, the title of which was borrowed for this unrelated play, was the first nonfiction true crime novel (about the Leopold and Loeb murder case), the precursor to Truman Capote’s In Cold Blood, according to the Wikipedia article on Levin.

Levin was a journalist and a prolific writer. One of the defining moments of his life was his witnessing, as a war correspondent, the liberation of concentration camps in Europe at the end of the Second World War. Today we would say that the behavior portrayed in the play was the manifestation of post-traumatic stress disorder, but that diagnosis wasn’t around in the 1950s.

The doppelgänger Levin created for himself in his writing was Sid Silver. The playwright, Rinne Groff, collated a set of events in Levin’s life, as recounted in books by Levin; by Levin’s wife, Tereska Torres; by Lawrence Graver; and by Ralph Melnick (see the Wikipedia link), and gave them to the character Sid Silver. So the play is ostensibly a dramatization of the nonfiction novel (form invented by Levin) of Levin’s life, told through the alter ego Levin invented, using a title Levin applied to a book about something else altogether. Nicely recursive, don’t you think? Derivative, too.

The outline
The play is about Levin’s obsession (not really a compulsion, I think) to bring The Diary of Anne Frank to the United States, first as a book and then as a drama. Anne Frank became the medium through which he understood his purpose in the world. Because of ideological and artistic differences with others (Otto Frank among them), he entered into a series of legal battles the narration of which constitutes the heart of the play. Well, what’s wrong with that? I’m not saying there wasn’t conflict or dramatic tension, but I am saying the play consisted almost entirely of exposition. Levin’s story—Groff’s synthesis of Levin’s story—would have made an interesting magazine article. In a good piece of journalism in the New Yorker or Harper’s, I expect exposition. In a play I want more.

The production
Three actors cover seven main and a few incidental roles. In addition, a crew of three puppeteers handle the ghosts of Anne Frank, Otto Frank, and Miep Gies, as well as the play-within-a-play roles consisting of an assortment of actors playing Anne Frank, Otto Frank, and Miep Gies. There’s that recursion thing again, a trick Groff seems fond of.

The play dragged. A third to a half of the scenes could be cut. In particular, the last three scenes were merely maudlin and added nothing to the play—not even a graceful denouement. If the playwright and director have any mercy, these scenes will be gone before the New Haven run is over. But the script has other problems aside from length. At the start of the second act, we’re treated to one of the characters entering the set, walking to the front of the stage to face the audience, and addressing the audience directly with superfluous narration of biographical details we don’t need to know. The whole show is so ponderously expository that it’s a wonder the actors could spit out the lines most of the time.

Moving on…
Hannah Cabell, as the publisher Miss Mermin and as Sid Silver’s wife (based on Levin’s wife, Tereska Torres) was superb.

Stephen Barker Turner, playing a variety of publishing executives and lawyers, who somehow all looked and acted alike, as well as Silver’s friend Mr. Matzliach, did the best he could. Mr. Thomas, Mr. Harris, and Mr. Ferris were all stereotyped WASPs, and Turner played them all pretty much the same way—as flat as they were written. I wasn’t the only one who was confused. At one point Silver called Ferris Harris and was corrected, garnering a chuckle from the audience. I honestly couldn’t tell if the error and correction were in the script or a fluffed line and an quick save.

Mandy Patinkin played Levin aka Silver. I always liked Patinkin in Chicago Hope. And the choice to play the Silver character is completely consistent with everything else I’ve seen him do. But…I dunno. Maybe he was just having a bad night. Or maybe the script, staging, and direction were really that bad. At best, I’d characterize his performance as uneven. He was on stage for nearly the entire play, and that’s a lot of material to master. Still, um, well, he’s a professional actor and I’m an amateur reviewer; so maybe he was just coming from somewhere I don’t understand at all. Or maybe he rose from his sick bed to be a trouper. Or something.

There were moments when I couldn’t tell if Patinkin was pausing for effect or had gone up on his line. If the pause was for effect, the effect wasn’t one I could identify. His rants, his moments of contrition, even his amorous moments with his wife (everyone keeps their clothes on in this one, for a change) all seemed rote, formulaic, phoned in. But I readily acknowledge that Patinkin may have signed on to the project despite a weak script and that he may be making the best of a bad situation. So I don’t want to lay the blame on him.

The puppeteers did everything that was asked of them and did so pretty well. This was straightforward marionette work consistent with the plodding expository nature of the script. No imagination was called for or in evidence.

The set is worth noting. I’ve seen great plays, okay plays, and stinkers at Yale Rep; but one saving grace of even the worst of them has always been the set design. With the resources of the Yale School of Drama, Yale School of Architecture, and Yale School of Art to draw on, the Rep is a showcase for brilliant, imaginative designers. As noted above, though, Compulsion is a co-production of three theaters, with a name star. I suspect this had something to do with the choice of Eugene Lee as the scenic designer. Lee “has been the production designer at Saturday Night Live since 1974,” according to the program notes, and “was recently inducted into the Theatre Hall of Fame in New York.” Uh-huh. Yawn. I think the set was a castoff from SNL, or else it was sketched on a napkin and faxed in. Blecch.

Don’t feel compelled to see this one. But read other reviews after the show actually opens. Maybe it will get better.

Tuesday, January 26, 2010

Sending a query to a literary agent?

  1. Ensure that the agent you are querying is legitimate. The Preditors & Editors site should be one place you check. It is not a comprehensive list of all legitimate agents, but it is a valuable resource for information on the snakes in the grass pretending they are agents.

    The main rule to keep in mind is that if the supposed agent asks you for money, directly or indirectly, you should run the other direction.

  2. Take a look at this great checklist from agent Janet Reid.

Wednesday, January 06, 2010

Typesetting myths you should have gotten over by now

Having worked with and studied type for half a century, I have seen fads come and go. I have seen a lot of badly designed experiments by psychology undergraduates passed off as “research” into type readability. And I have seen a lot of opinion on the part of graphic design instructors passed off as fact.

But in the Dark Ages of my youth, type was set by compositors. Since the advent of desktop publishing thirty-odd years ago, people with no training in typography have been putting themselves out as experts. And that has caused the sewers to overflow, releasing all sorts of stuff into the mainstream. With the more recent advent of digital book printing, all sorts of people are typesetting their own books—or trying to. And when they dip their nets into that mainstream looking for tips on how to do the job right, they often come up with—well, you get the idea.

Naturally, I’d much rather see self-publishing authors avail themselves of my services or those of another professional compositor than do it themselves. But if you are a diehard DIYer, here are a few suggestions from a grumpy old typesetter on Internet myths you should ignore:
  • Don’t hyphenate; it slows reading and reduces comprehension.

    FALSE. If you are publishing an edition specifically for groups with impaired reading ability, you should avoid hyphenation. For normal readers (the large majority of the reading public for trade fiction and nonfiction alike), a moderate amount of hyphenation improves readability when compared with the alternative of having letters and words badly and unevenly spaced. You do want to avoid having more than two consecutive hyphens or, in narrow columns, three consecutive hyphens, but there is no reason to turn hyphenation off altogether.

  • Don’t justify text; it forces uneven word spacing.

    FALSE. Using modern page layout software such as InDesign, you can keep word spacing within an acceptable range, minimize (but not necessarily eliminate) hyphenation, and retain conventional justified text. Readability research confirms that normal readers continue reading longer and retain more of what they read when text is justified normally than when it is set ragged right.

    But note: Hyphenation is not available in HTML, so justified text looks terrible on the Web. For online use, such as here, stick with ragged right.

  • Tight type looks better than loose type.

    FALSE. Tight type increases reader fatigue and slows reading. If you look at books set on Linotype (hot metal) machines from half a century ago, you’ll see that the standard setting (governed by the mechanical limitations of the technology) was considerably more open than the default kerning values for modern digital fonts. Stay with the default or, if you want to be kind to your readers (especially at smaller point sizes), open the type up by a fraction. This is a good trick for situations where an old-fashioned appearance is desirable too.

  • You can typeset a perfectly fine book using Microsoft Word.

    FALSE. You can reproduce the Sistine Chapel using a paint-by-numbers kit, but it’s going to take a long time and you’re not going to fool anyone. Word is a word processing program, not a typesetting program.

  • All you have to do is import your Word document into InDesign and you’re done.

    FALSE. Composition remains an art that requires human intervention to produce good results. Learn to look at a page critically and to apply adjustments that improve the reader’s experience. Watch for ladders, rivers, pigeonholes, tight and loose lines, bad breaks, widows, orphans, and unbalanced spreads. Eliminating all of those at the same time is what separates the pros from the wannabes.

Thursday, December 17, 2009

Finding a printer

Full disclosure
I purchase printing and binding services as an agent for my clients. I pass through the exact amount I am charged. I do not charge a markup or receive a commission. This is just a service I provide, at no cost, to help ensure that my publishing clients receive finished goods whose quality reflects all the hard work that went into designing them and get them at a fair price. So what follows does not reflect any financial interest on my part.

What is a high-quality book?
In discussions on various LinkedIn groups (and in other venues as well), I regularly see people with a variety of backgrounds endorsing the “high quality” of books produced by one printer or another, one subsidy press or another. These statements don’t mean a lot to me, because I don’t know how knowledgeable these individuals are about printing and binding production values.

I’ve had printing company reps proud of their companies’ work send me sample books that ranged from bad to godawful. So I have reason to suspect the judgment of authors who tout the great quality they got from a vendor.

I’m picky. Here are some of the things I look for.
  • I expect good backup. What does that mean? It means that if I hold a leaf of the book up to a light, the type on the back of the leaf should align with the type on the front. The left and right margins should be exactly even and the top line of type should be exactly even. I should not see the type on the back misaligned from the type on the front by even a millimeter.

  • I expect black ink to be black, not gray, and I expect it to be that same black throughout the book. The type should not vary in density from page to page or from the front of the book to the back. There should not be reflective glare from the type (seen when toner is applied improperly in digital printing).

  • If there are halftones, I expect good tonal range and contrast. If there is line art, I expect good sharpness.

  • I expect precise folding. What does that mean? It means that if I riffle the pages (like an animator’s flip book or like a deck of cards), the top margin should not waver up and down but should remain constant throughout the book. I’m not talking about pages where the margin is designed to be different, such as chapter pages. I’m just talking about the work of the folder operator.

  • I expect the book to be trimmed square and to size. The dimensions of the front cover should match the dimensions of the back cover and both should be within a very close tolerance of the design size.

  • I expect the cover (for a perfect bound book) to be properly aligned, with the spine centered, all live copy within the safety margin, and bleeds intact (no white showing).

  • I expect the cover to be glued properly, with no excess glue squeezed out and with the cover glued evenly onto the edge of the first and last pages. Looking at the top and bottom of the spine, I expect the glue layer to be even from the front to the back of the book and the top to the bottom.

  • I expect coatings and laminations to be applied properly, with no peeling or curling.

  • I expect a printer that services small publishers to screen submitted files for suitability and to advise customers when the files have significant problems (such as poorly prepared images or low-quality typesetting). “We print whatever the client sends us” is not an appropriate policy for companies serving the self-publishing market.

Four tiers of printers
There are roughly four tiers, in my mind, of book manufacturing:
  1. Non-specialists. These are printers for whom book manufacturing is an occasional job. The category includes the local Docutech center, accustomed to printing and binding documents that businesses distribute internally or to customers. It includes local job printers who send the printed pages out to a local custom bindery. It includes larger commercial printers who do that or perhaps have a small finishing department. It includes printers who solicit book business to fill holes in their schedule but really aren’t equipped for it; the shoddiness of their books is obvious.

  2. POD. The major players in the print-on-demand market are like talking dogs: it isn’t that they’re good at it; the remarkable thing is that they do it at all. For the most part, their employees do not come from the book manufacturing industry; they are trained on the job, and they measure their success by how fast and cheaply they can fill an order for a single book. Book quality is passable, and it meets the needs of the POD market.

  3. “Good” book manufacturers. This group includes many companies whose names are bandied about, with enthusiastic recommendations, on self-publishing mailing lists and websites. These are good, solid printers who produce acceptable books you might find on the shelves of any bookstore. Most people will be insensitive to defects. Problems I’ve seen include less-than-perfect backup, mediocre folding, some quality control issues in cover application, and—probably the biggest problem—a willingness to print completely unacceptable files. They are within ethical boundaries to simply print what’s sent to them. Nonetheless, if they are going to cater to amateurs, I think they should either push back when they receive garbage or they should fix the problems and charge for the service. At the very least, they should flag such jobs internally so that when someone like me asks for samples they refrain from sending out those books.

    Another feature of this group is that their digital short-run books and their offset books are easily told apart.

  4. “Excellent” book manufacturers. This group includes some of the largest book manufacturers in the country (as well as some smaller ones and some that are not in the country). While their bread-and-butter customers are large publishers, they are efficient enough that they can also happily serve the independent designer market (not sure how well they handle amateurs, though). Quality ranges from perfect to near-perfect, and only a technical examination can distinguish their offset work from their digital work. In my experience, prices in this category are actually lower than in the “good” category (I don’t know why, but I also don’t ask why).
That said, were I to have a job very different from past jobs, in terms of paper, page size, binding type, or quantity, I would certainly get bids from printers in both the “good” and “excellent” categories. It may be that one of the “good” printers has a sweet spot that enables it to come in with a low price. So far that hasn’t happened, but I’m not oblivious to the possibility.

Saturday, December 12, 2009

Interesting software QA test case

Hold those cynical thoughts for a minute. There really is such a thing as software quality assurance testing, an activity that employs a great many skilled and intelligent people. Despite the annoying flaws we users complain about in commercial software, it wouldn’t be on the market at all without the diligent and unsung work of QA departments everywhere.

Part of what QA departments do is a type of automated testing in which a script runs a piece of software through its paces, entering all sorts of rule-breaking text strings in input fields and seeing whether the software handles the rule-breaking gracefully. These test strings comprise all the weird cases analysts can think of—trying to type 100 characters into a field that is 30 characters long, using non-Latin characters into a field that expects Latin characters, typing letters into a number field, and so forth.

My serendipitous test case
My post yesterday is titled “<Redacted>.” Note that it begins and ends with angle brackets. Angle brackets have a special status in markup languages that derive from SGML, such as HTML, XHTML, and the others that the Web is built on. Angle brackets signal to the markup language interpreter that what is between them is a tag, information the software uses to decide, at the simplest level, how to display what follows (until a closing tag is encountered).

As a consequence of this special status, if I want you to see an angle bracket in the displayed text, I have to use a workaround. The workaround is to put in a character code (called an HTML entity) that will be interpreted as a mathematical less than or greater than symbol. Knowing this, what I typed into the Title field for yesterday’s post was &lt;Redacted&gt; (and I just applied a similar trick to make that come out right). So far so good.

But as you know, a blog post is more than a simple HTML web page. When I click the Publish Post button, my browser sends information to a server that triggers software to assign a URL-friendly name to the post and store what I’ve typed in a database. That database has rules for how text is stored. Other software extracts text from the database and sends an HTML page to your browser so you can read the post. Other software extracts the information in another way to supply your RSS feed reader. When you view my post, either as a web page on my domain or in your feed reader or in your email or…wherever, other software has intervened to process the text.

So there are lots of places where my angle brackets have to be interpreted and processed.

Complicating matters is that a lot of low-level text processing takes place inside software modules that are freely distributed to programmers. These modules may be written in a programming language different from that of the surrounding program, and the programmer who uses them may not fully understand all that goes on inside them. For example, if I want to build a web form that asks for a phone number, I may search around for a Javascript program that validates entries to assure they are legitimate phone numbers. I don’t have to know how that works; I only need to know how to use it.

Back to <Redacted>
Typically, Blogger creates a URL for blog posts based on the post title. It strips out punctuation and words such as a, an, the, and a few others. For example, my post titled “Do you have the willies?” became http://www.ampersandvirgule.com/2009/12/do-you-have-willies.html. For yesterday’s post, though, Blogger looked at the post title and threw up its hands (wise move), basing the post URL on the first line of the post body, instead: http://www.ampersandvirgule.com/2009/12/you-may-have-seen-story-other-day-about.html. So far so good.

But the post title gets reported in many other interfaces. It has variously shown up as:
  • <Redacted> [correct]
  • &lt;Redacted&gt; [user-unfriendly but not wrong]
  • Untitled Entry [uninformative, but a sign of recognition there was a problem]
  • [blank]
My humble suggestion to software QA professionals everywhere is that this is a test case they may want to add to their battery.

Friday, December 11, 2009

<Redacted>

You may have seen the story the other day about the US Transportation Security Administration manual that was posted on the agency’s website several months ago. It was a PDF in which sensitive material was blocked out with black rectangles placed over the text. If one has only a user’s eye view of software (if you’re a manager, in other words) and can’t be bothered learning anything about what the software does and how it works, this may seem like a reasonable way to secure the information. You can’t see it, so it isn’t there, right?

As Alexander Pope put it, “A little learning is a dangerous thing.”

The fact, as anyone who has bothered to learn anything about PDFs knows, is that the text was always there, merely covered, and the simple expedient of choosing the text selection tool in the Acrobat or Adobe Reader toolbar allowed any user to select and copy the full text of the document. Oops!

A couple of months ago, before this news story surfaced, I was typesetting a manuscript in which the author attacked an advertisement for a weight-loss remedy. To dramatize the fact that he was saying some rather nasty things about the advertised product, he chose to use black rectangles to block out the product’s name (rather than use a more traditional editorial device such as underscored spaces: _______). But, as with the TSA functionaries, the author had left the product name in the manuscript and applied a black highlight, rendering the name invisible to the eye but not to the cursor.

When I typeset the passage, I used a similar technique (applying a character style that rendered the word as a solid black rectangle). But before doing so, I replaced the product name with “<redacted>.” This text is not visible in the printed book. But should the author decide to produce an e-book later, in PDF or any other format, the product name will not be inadvertently revealed.

This is not rocket science. It’s just responsible tool use. Top-down management often presumes that anything a manager doesn’t already know isn’t important for anyone else to know either and that therefore training for subordinates is unnecessary. The TSA is disciplining five people who believed that.

Thursday, December 10, 2009

If one of those bottles should happen to fall...

According to Poynter Online, Nielsen is shutting down Kirkus Reviews and Editor & Publisher. Kirkus Reviews was one of the very few remaining pre-publication book review journals and was one of two or three relied on by librarians in planning their new book purchases.

The rationale for producing bound galleys or advance reading copies (ARCs) of books, with its built-in delay of four months before publishing the finished book, is looking weaker by the day.