Showing posts with label ambiguity. Show all posts
Showing posts with label ambiguity. Show all posts

Wednesday, March 7, 2012

Bad Ambiguity Strikes Again

I love the restaurant review book Eating Las Vegas by John Curtas, Max Jacobson, and Al Mancini. I think I'd keep buying the annual editions even if I never went to Las Vegas again, just to stay in touch with their views on restaurant trends.

I wish the book had been more thoroughly edited, though. Here's a line that doesn't work for me at all. It's a one-phrase review tucked into page 142 of a section called "Cheap Eats." The note about the  restaurant says:

Popular with locals who wouldn't know real Spanish tapas if they bit them on their Iberico.

(Iberico is a Spanish ham, in case you don't know, and "tapas" are small-plate dishes like appetizers.)

What bugs me: I can't parse the "if they bit them" bit. Normally that phrase would be used like this:

"You stupid editors wouldn't know a good short story if it bit you!"

In the second example, the short story is obviously biting the editor. And that works. But the original text is about food. How do you eat food? Quite often, by biting it. So "if they bit them" can be interpreted both ways: if the tapas bit the locals (the traditional joke sense), or if the locals bit the tapas (the literal sense). 

I suppose you could say that since both interpretations could work, there's no problem, but I disagree. I say that since both interpretations work, the writer has to clarify which one he (meaning John, Al, or Max) means. Which is a lot of work to put into a one-phrase dismissal of a restaurant, and might make the phrase less sharp and amusing. But I'd rather have a slightly less sharp line than one that makes readers wrinkle their brows and wonder what the author's talking about.

Friday, March 2, 2012

A Subtle Ambiguity Problem

A co-worker of mine found out about an ambiguity problem in one of her pieces the hardest way I can imagine, and long after it was too late. She said I could blog about it, and I'm glad, because I'd never experienced this problem.

My co-worker used to write and sell poetry. A publisher wanted to add one of her pieces to a CD of spoken poems. She agreed, but was horrified months later when she found out one of her poems had been critically misunderstood.

Her poem included the phrase "tear up," and she meant that in the sense of tears forming in one's eyes. So when she read her poem aloud, she always pronounced it TEER UP. Everyone involved in the audio publishing interpreted her phrase as meaning "rip up," which, she later recognized, was a defensible (but incorrect) interpretation of her poem. So the speaker on the CD pronounced the words TARE UP. 

Obviously, that pronunciation changed the meaning of her poem, and in her view, ruined it.

Today, audio books and audio magazines abound. At least two stories we've published in On The Premises have appeared in audio magazines. So remember, if how your story is read aloud matters to you, discuss it with editors of those magazines in advance, and look for places where a defensible but incorrect pronunciation would wreck your story.

Friday, February 10, 2012

The Bad Kind of Ambiguity

A problem I run into all the time with both my own writing and other people's is that some text can be read more than one way, and sometimes the various ways have different meanings. This kind of ambiguous writing can be easy to spot, as in the following example:

Susan told Kelly she didn't know where her shoes were.

You can see the problem. Whose shoes are we talking about, Susan's or Kelly's? On top of that, who is the first "she" referring to? You could mean:

Susan told Kelly that Kelly didn't know where Susan's shoes were. 

(As some strange kind of insult, I assume. "You're so dumb, you don't know where my shoes are!")

Most writers can spot these kinds of mistakes and fix them almost as soon as they're written. But here's a subtler one I ran across on Slate, a news/opinion site:

We disparage things we don't approve of as phony.

Here's the article I saw it in if you're interested.

I can tell the author's trying to say that if we disapprove of something, we call it phony. But can you see the other way to read it? Try this:

"If we don't approve of the level of phoniness in something, we disparage it."

I know the author doesn't mean us to read the sentence that way. But you'd be surprised how many times I run into contest entries that contain a sentence that could be read more than one way. When that happens, I can guarantee you the author doesn't want anyone reading the sentence the other way.

I can also guarantee that if you have enough readers, some small percentage of them will read it the wrong way.

Here's how I'd revise the Slate sentence: 

If we disapprove of something, we disparage it as phony.

So, when you're writing, read over your material once in a while and try to deliberately misunderstand it. If you find you've written something that's easy to draw unintended conclusions about, consider rewriting it to make your intention clearer.