<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Self Editing Blog &#187; Style</title>
	<atom:link href="http://www.selfeditingblog.com/category/style/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.selfeditingblog.com</link>
	<description>Edit Your Own Novel, Screenplay, or Nonfiction Book</description>
	<lastBuildDate>Sun, 25 Apr 2010 20:31:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Just Do It</title>
		<link>http://www.selfeditingblog.com/just-do-it/531/</link>
		<comments>http://www.selfeditingblog.com/just-do-it/531/#comments</comments>
		<pubDate>Sun, 03 Jan 2010 01:12:45 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Style]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=531</guid>
		<description><![CDATA[   Just Do It: False Starts, Late Deaths, and Appearances by John Robert Marlow
PUSSYFOOTING AROUND
There are several things wrong with this sentence: &#8220;Frank was visibly upset when he
started to cross what appeared to be a street.&#8221; Strictly speaking, there may be nothing
grammatically incorrect here. Stylistically, though, it&#8217;s a ...]]></description>
			<content:encoded><![CDATA[<div id="attachment_531" class="wp-caption aligncenter" style="width: 530px">   <a href="http://www.selfeditingblog.com/just-do-it/531/" title="Just Do It: False Starts, Late Deaths, and Appearances by John Robert Marlow" width="520" height="212" /></a><p class="wp-caption-text">Just Do It: False Starts, Late Deaths, and Appearances by John Robert Marlow</p></div>
<p>PUSSYFOOTING AROUND</p>
<p>There are several things wrong with this sentence: &#8220;Frank was visibly upset when he<br />
started to cross what appeared to be a street.&#8221; Strictly speaking, there may be nothing<br />
grammatically incorrect here. Stylistically, though, it&#8217;s a train wreck—and would be even<br />
if Frank hadn&#8217;t died fifty pages back. Simply put, the sentence pussyfoots around, wasting<br />
time and space. This post will help you to avoid doing the same&#8230;</p>
<p>FALSE STARTS</p>
<p>Some authors feel the need to precede a great many physical actions with the word<br />
&#8220;started&#8221; or &#8220;began.&#8221; Instead of saying the character walked across the room (or street),<br />
or raised a glass in toast, they&#8217;ll say he <em>started</em> to walk across the room, or<br />
<em>began</em> to lift the glass. In most cases, this is not an occasional eccentricity;<br />
writers who do this once tend to continue the practice throughout the entire story.</p>
<p>If a character lifts a glass or walks across a room, say he lifts the glass or walks across the<br />
room; don&#8217;t bog the story down by saying he started to lift the glass or began to cross the<br />
room. Both are long-winded, unnecessary and distracting ways of saying the same thing.<br />
Have your characters take Nike&#8217;s advice and just do it. </p>
<p>Exceptions include situations where you&#8217;re setting up the choreography for a subsequent<br />
action or action scene or sequence. In such cases, it may be very important to know, for<br />
example, that Bob has <em>started</em> to cross the street. but has not yet reached<br />
the other side, when the Bugatti Veyron screams around the curve doing two-fifty. </p>
<p>Or that, say, Rain Man is only halfway across the intersection when the DON&#8217;T WALK sign<br />
starts flashing. (Note that the word <em>starts</em> is appropriate here because it&#8217;s tied<br />
to action: the sign wasn&#8217;t flashing when Rain Man stepped into the street—and when it<br />
starts to flash, he stops walking. Note also that it&#8217;s okay to switch tenses in the previous<br />
sentence.)</p>
<p>GHOSTS</p>
<p>Somewhat like their namesakes, literary &#8220;ghosts&#8221; are phantoms of departed scenes and<br />
characters which linger on to haunt your pages. Changing something in one scene often<br />
affects events in other scenes. When we fail to realize this, or neglect to track down and<br />
alter all of the other scenes that need to &#8220;match&#8221; the one we just changed, we create a<br />
ghost. </p>
<p>In the course of my editing, I&#8217;ve seen lost or sold items reappearing in their owners&#8217;<br />
possession, individual scenes and entire subplots that have absolutely no remaining<br />
connection to anything else in the story, characters who appear to be doing something<br />
important in one scene but are present nowhere else, a party taking place in a home that<br />
burned to the ground in a previous chapter, and deceased characters who carry on as if<br />
nothing had happened—driving to the post office, playing baseball, making love. </p>
<p>Each of the individual scenes made perfect sense at some stage in the story&#8217;s history.<br />
Later changes turned them into ghosts. If not hunted down and excised—or<br />
exorcised—such ghosts can result in a story that appears to have been hastily or sloppily<br />
constructed.</p>
<p>When revising or rewriting, give some thought to both the overall and specific effects of<br />
the changes you&#8217;re making. Ask yourself what <em>else</em> must be added, altered,<br />
or deleted to &#8220;match&#8221; what you&#8217;re doing now and bring the rest of the story into line with<br />
the new changes. </p>
<p>Sometimes the answer will be obvious: if Andre is now killed by a pack of wild vampire-<br />
rabbits on page forty-nine, he won&#8217;t be having dinner with Priscilla on page eighty-two—<br />
unless he has exceptionally large ears, and Priscilla is on the menu. </p>
<p>Other slips may be less obvious. As a general rule, the more tightly woven your plot<br />
becomes, the greater the chance that any one particular change will ripple outward into<br />
other scenes. Perhaps the ultimate expression of this can be found in the film<br />
<em>Memento</em>, where—because the scene order runs backward instead of<br />
forward—the deletion or significant alteration of any single scene would cause the entire<br />
plot to collapse.</p>
<p>Working with an outline makes it easier and faster to spot most ghosts, but doesn&#8217;t get<br />
you out of a final ghost-hunt: after you&#8217;re done with the final revision, you must reread<br />
the whole thing one more time, killing any ghosts you find along the way. Better they<br />
meet their end at your hands than spook an agent or publisher into viewing your work as<br />
shoddy.</p>
<p>There are no exceptions here: all ghosts must go.</p>
<p>TRUE APPEARANCES</p>
<p>Like false starts, this habit is tough to categorize. Authors subject to this compulsion tend<br />
to precede their descriptions with &#8220;seemed&#8221; or &#8220;appeared.&#8221; For example: &#8220;On the table<br />
was what appeared [or seemed] to be a bowl of fruit.&#8221; </p>
<p>Now, if the object turns out to be something other than a bowl of fruit—say, a cleverly<br />
disguised surveillance device containing cameras, microphones, heat sensors and motion<br />
detectors—this is perfectly acceptable. </p>
<p>But when (as is usually the case) it really is just a bowl of fruit on the table, this phrasing<br />
becomes unnecessarily long and convoluted—a distracting affectation that makes for an<br />
awkward read and takes up far too much space saying, essentially, nothing. </p>
<p>Like the false start, this issue tends to be habitual: an author who does it once will usually<br />
do it dozens, if not scores of times over the course of a manuscript or screenplay.</p>
<p>When describing ordinary objects or events that are exactly what they seem to be,<br />
describe them as just that; do not tell the reader that they <em>seem</em> or<br />
<em>appear</em> to be exactly what they are. </p>
<p>When you look at a table with a bowl of fruit sitting on it, you don&#8217;t think to yourself,<br />
&#8220;Hmmm. That <em>seems</em> to be a bowl of fruit sitting there on the table.&#8221; You<br />
think: &#8220;Bowl of fruit.&#8221; So does your reader. And so, too, should your characters.</p>
<p>Exceptions include things or events that are not what they appear or seem to be. (&#8221;On<br />
the table was what appeared to be a bowl of fruit. On closer inspection, Henrietta found<br />
it to be a cleverly disguised surveillance device.&#8221;) Also things that are unlikely to be what<br />
they seem to be, even if they turn out to be exactly that. (&#8221;On the table was what<br />
appeared to be a dead alien.&#8221;) In such exceptional cases, you are in effect voicing the<br />
character&#8217;s skepticism. </p>
<p>A third and rarer exception would be a character who, for whatever reason, doubts that<br />
things are as they appear to be. This could be due to a psychological problem, previous<br />
experience, unfamiliar surroundings, etc. In this case, also, you&#8217;re conveying the<br />
character&#8217;s skepticism.</p>
<p>VISIBLIES</p>
<p>It&#8217;s a medical fact that one in every twenty authors will at some point come down with a<br />
case of the visiblies. Writers with this malady find themselves writing things like &#8220;Sarah<br />
was visibly upset&#8221; and &#8220;Jimmy was visibly shaken.&#8221; Why not simply &#8220;Sarah was upset,&#8221;<br />
or &#8220;Jimmy was shaken?&#8221; Because unless otherwise informed, readers will expect the<br />
reaction to be visible; adding the word <em>visibly</em> becomes redundant<br />
and—particularly with screenplays—marks the writer as unnecessarily wordy. (Some<br />
directors and actors might even consider such additions to be infringing on their turf,<br />
telling them how to do their jobs.)</p>
<p>Exceptions include situations where, say, a particular character who has been presented<br />
as stoic, expressionless, or adept at concealing his emotions becomes visibly upset or<br />
shaken—because now, rather than repeating old information, the word <em>visibly</em><br />
is conveying new information about something that runs counter to reader expectations.</p>
<p>CONCLUSION</p>
<p>While stylistic liberties may be taken by accomplished writers and talented beginners, the<br />
habits mentioned here are awkward, distracting, and unprofessional. Ghosts, on the other<br />
hand, can crop up on anyone—but professionals banish them before sending out their<br />
material.<br />
<HR align=center width=400></p>
<p>Author <a target="_blank" href="http://www.selfeditingblog.com/author/">John Robert Marlow</a> is available for professional editing, development, and consultation. If you&#8217;d like help taking your work to the next level, <a href="http://www.selfeditingblog.com/contact/">contact John here</a>. <div class="wp-caption alignright" style="width: 97px"><a href="http://www.selfeditingblog.com/author/"><img alt="JRM" src="http://www.selfeditingblog.com/g_authorshot (100h).jpg" width="87" height="100" /></a><p class="wp-caption-text">JRM</p></div></p>
<p>copyright &copy; by John Robert Marlow<br />
all rights reserved</p>
]]></content:encoded>
			<wfw:commentRss>http://www.selfeditingblog.com/just-do-it/531/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Blah, Blah, Blah</title>
		<link>http://www.selfeditingblog.com/blah-blah-blah/525/</link>
		<comments>http://www.selfeditingblog.com/blah-blah-blah/525/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 09:55:17 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Style]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=525</guid>
		<description><![CDATA[   Blah, Blah, Blah: Overdescription, Exposition, and Stage Direction by John Robert Marlow
THE BLAHS
Have you ever attended a lecture, or sat in a classroom, or watched a video where the speaker droned endlessly on about what should have been an interesting topic? After a while, the eyes and ...]]></description>
			<content:encoded><![CDATA[<div id="attachment_525" class="wp-caption aligncenter" style="width: 530px">   <a href="http://www.selfeditingblog.com/snucking-threw-the-poring-reign/525/" title="Blah, Blah, Blah: Overdescription, Exposition, and Stage Direction by John Robert Marlow" width="520" height="212" /></a><p class="wp-caption-text">Blah, Blah, Blah: Overdescription, Exposition, and Stage Direction by John Robert Marlow</p></div>
<p>THE BLAHS</p>
<p>Have you ever attended a lecture, or sat in a classroom, or watched a video where the speaker droned endlessly on about what <em>should</em> have been an interesting topic? After a while, the eyes and ears glaze over, and all you really hear is “Blah blah blah…” Don’t let that happen to your writing…</p>
<p>OVERDESCRIPTION</p>
<p>Overdescription is a common malady. The primary symptom is a tendency to OD on description, going into endless detail about things that ultimately don&#8217;t matter. The author may “see the movie in his head,” even if he’s writing a book. </p>
<p>Driven by a desire to convey this vision to the reader in its purest form, the writer mistakes quantity for quality—and embarks upon a frenzied attempt to describe every factual detail of each scene, no matter how small.</p>
<p>From the color and style of clothing worn by each character to the year, make, model, color, and general condition of their cars, to the wallpaper, floorboards, carpet, furnishings, knick-knacks, architecture, temperature and humidity of each room, to ongoing descriptions of every street, sidewalk, building, lamppost, passerby and blade of grass—it’s all there in excruciating detail; a frenzied minutiae. Some writers do this nonstop, from first page to last. Others suffer from occasional bouts of descriptitus.</p>
<p>Instead of ODing on overdescription, realize that your purpose is <em>not</em> simply to record people, places, and events. A camera can do that—better, cheaper, and faster than any writer who ever lived. But that is not the function of the writer.</p>
<p>The writer’s purpose is to <em>convey emotion</em>. You can write description thick as a phone book, and fail to make a real impression. Facts—alone—are devoid of emotional content. A tree falls in the forest. So what? A tree falls toward a tent occupied by someone we care about—that’s an emotional event. </p>
<p>We don’t need to know who made the tent, or what color it is. Nor do we need to know how many leaves are on the tree. What we need to know is this: that tree is about to kill someone we don’t want to die. That’s it.</p>
<p>What you want to focus on is <em>emotional content</em>. Not: Is this room well- or dimly-lit? Rather: Is this room cheery or depressing? Inviting or forbidding? How do the bare facts relate to human emotions? You can say (as part of your description) that a room is dimly-lit, but you must also set a mood. This doesn’t mean you have to say “The room was cheery;” instead, you use words that evoke an image of cheeriness in the mind of your reader.</p>
<p>Consider: you can factually describe a room without conveying a shred of emotion. You can also describe a room emotionally, without conveying any factual description at all. The best writers blend fact with emotion. </p>
<p>But when you come right down to it, the emotional description can stand alone; the factual description cannot. Because when you’re telling a story—fiction or nonfiction—emotional involvement is what keeps people going.</p>
<p>You are not a recording device; you are a chronicler of emotional journeys.</p>
<p>EXPOSITION</p>
<p>Expository writing is what happens when an author needs to get information across to the reader, but can’t figure out how to work it into the story. What happens is this: the information is clumsily dropped into dialogue or narration, creating an “infodump;” critical details that appear out of nowhere, and exist for the sole purpose of transmitting information from author to reader.</p>
<p>Writers who do this believe that readers will simply absorb the information and move on. What actually happens is similar to the effect described in <a href="http://selfeditingblog.com/hey-look-at-me/427/">Hey, Look at Me! Intrusive, Chatty, and Explanatory Writing</a>. </p>
<p>Instead of guiding the reader experience, the author is now inserting himself between reader and story—redirecting the reader’s attention to his own kludgy attempt to graft out-of-place information onto what should be a smooth-flowing narrative. The writer’s intentions are good; his technique, not so much.</p>
<p>There are two solutions to this problem: integrate the information into the story in such a way that it seems “organic” to the tale being told—or drop the information entirely. </p>
<p>Excellent examples of technical information smoothly presented include <em>The Terminator</em> (where Reese must educate Sarah on the nature of the threat they face) and <em>The Matrix</em> (where Morpheus and his crew must educate Neo about “the desert of the real”). Note that the same technique is employed in both of these stories: the mentor relationship. A character unfamiliar with the territory is guided by one who is; as the student learns, so too does the audience. </p>
<p>In <em>True Lies</em>, a humorous approach is taken. Taken hostage by terrorists and dragged before a stolen nuclear warhead, secret agent Harry Tasker is ordered to identify the device for a camera. His response? “I know what this is&#8230; This is an espresso machine… No, no wait. It&#8217;s a snow cone maker… Is it a water heater?” Finally, when his wife’s life is threatened, he spills the technical details. The wife—who had no idea he was a spy—punches him.</p>
<p>STAGE DIRECTION</p>
<p>Narration describing character action—that’s stage direction. The term originated with playwrights, who had to tell the actors what do via instructions—<em>directions</em>—written into the play. Today, stage direction also appears in books and screenplays. It’s rare to find too little stage direction in either format, but extremely common to find too much.</p>
<p>There are two basic ways to go wrong here. Sitting behind door number one, typing away, is the writer who’s not quite sure what his characters should be doing. Instinct tells him that ten pages of pure, uninterrupted dialogue isn’t working; something more is needed. </p>
<p>And so he gives his characters something—<em>anything</em>—to do: gaze out the window; arch, furrow, or scrunch their brows;, smile, frown, giggle, titter, scowl—or (ever popular) eat. The problem is always the same: the actions being described are inconsequential or meaningless, and exist for one reason only: to provide filler for a scene that is missing something.</p>
<p>Inevitably, this leads to passages brimming with information that is both irrelevant and distracting: instead of having two “talking heads” chatting for ten pages, the reader must slog through a conversation that is constantly interrupted by long thoughtful gazes, arched brows, slurped soup, and masticated meat.</p>
<p>Sitting behind Door Number Two is the author who applies overdescription to stage direction—detailing every slightest motion, gesture, breath, shifting glance, and sigh of one (or every) character. The end result is the same: a choppy, distracting read.</p>
<p>Ideally, everything means something, and nothing means nothing. And while that ideal cannot always be achieved, you can strive to minimize meaningless character actions. Look to see what can be eliminated, but also what might be recast and given meaning. </p>
<p>In <em>The Usual Suspects</em>, Verbal stares ahead during his interrogation. At another point, he gazes up toward his interrogator. Neither action seems particularly significant; both turn out to be crucial. Stage direction is both necessary and inevitable. Your job is to make it count.</p>
<p>CONCLUSION</p>
<p>Of the many sins a competent writer might commit, the worst by far is boring the reader. Technical perfection does little good if the reader’s mind wanders from the story. Even a mild case of the blahs can be damaging. Severe cases can be fatal. Overdescription, exposition, and stage direction are leading causes. Guard against them, always.<br />
<HR align=center width=400></p>
<p>Author <a target="_blank" href="http://www.selfeditingblog.com/author/">John Robert Marlow</a> is available for professional editing, development, and consultation. If you&#8217;d like help taking your work to the next level, <a href="http://www.selfeditingblog.com/contact/">contact John here</a>. <div class="wp-caption alignright" style="width: 97px"><a href="http://www.selfeditingblog.com/author/"><img alt="JRM" src="http://www.selfeditingblog.com/g_authorshot (100h).jpg" width="87" height="100" /></a><p class="wp-caption-text">JRM</p></div></p>
<p>copyright &copy; by John Robert Marlow<br />
all rights reserved</p>
]]></content:encoded>
			<wfw:commentRss>http://www.selfeditingblog.com/blah-blah-blah/525/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hey, Look at Me!</title>
		<link>http://www.selfeditingblog.com/hey-look-at-me/427/</link>
		<comments>http://www.selfeditingblog.com/hey-look-at-me/427/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 04:32:32 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Style]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=427</guid>
		<description><![CDATA[   Hey, Look at Me! Intrusive, Chatty, and Explanatory Writing by John Robert Marlow
Authors have a single, overriding function: to connect reader and story. At our best, we immerse the reader so thoroughly in the world of our story that the “real” world disappears and, for a time, ...]]></description>
			<content:encoded><![CDATA[<div id="attachment_427" class="wp-caption aligncenter" style="width: 530px">   <a href="http://www.selfeditingblog.com/hey-look-at-me/427/" title="Hey, Look at Me! Intrusive, Chatty, and Explanatory Writing by John Robert Marlow" width="520" height="212" /></a><p class="wp-caption-text">Hey, Look at Me! Intrusive, Chatty, and Explanatory Writing by John Robert Marlow</p></div>
<p>Authors have a single, overriding function: to connect reader and story. At our best, we immerse the reader so thoroughly in the world of our story that the “real” world disappears and, for a time, there is nothing <em>but</em> the story. That’s the kind of experience readers hope for and deserve. It’s a zen-like state that is not easily achieved. </p>
<p>It becomes impossible when a brightly-dressed, cymbal-banging acrobat starts jumping around in front of the reader, yelling “Hey, look at me!” Yet many authors unknowingly engage in the literary equivalent of this practice by inserting themselves between reader and story—usually in one of the following ways.</p>
<p>YOU THERE!</p>
<p>The word “you,” well-behaved under normal circumstances, becomes suspect any time it appears outside of dialogue or first-person narration. When properly employed—<em>You dunderhead</em>, he thought—all is well. But problems arise when “you” refers to someone outside the world of the story.</p>
<p>The most common transgressor here is the phrase “You never know” (or “You never knew”). Another common phrase begins: “You’d think…” When phrases like this are presented as narration or internal monologue (the character’s own thoughts laid out for the reader) the word <em>you</em> often refers to the reader.</p>
<p>A few other examples, all from narration: “Life never handed out what you expected;” “It was like giving up your lunch money. But when Uncle Noonan tells you to do something, you just flat do it;” “What else could you say?;” “It was the kind of thing you’d find in a junk shop;” “…when you least expected it.” (Notice the tense issues here as well.)</p>
<p>When you come across something like this in your own writing, ask yourself: Does <em>you</em> clearly refer to a character within the story? If the answer is no, you have a problem, because that means <em>you</em> refers to the reader—and here you are talking to him (or her) in the middle of the story. </p>
<p>It’s the rough equivalent of a film director leaning into frame in the middle of a movie and saying “You never know”—or whatever your particular line happens to be—to the audience. Like you, he doesn’t belong in the story. </p>
<p>And, short of a nearby gunshot, nothing tears the reader out of the story more swiftly or destructively. </p>
<p>As a side note, passages that address the reader often have mixed or incorrect tenses as well, so be sure to keep an eye out for these.</p>
<p>Exceptions: First person narration, and some comedies. Keep in mind that letters, sound recordings, and videos which address a nonspecific “you” are usually fine, even when the story is being told in the third person. (These are, in a sense, addressing the character doing the reading, listening, or watching.)</p>
<p>Screenplays are another exception; here, it is permissible—but often inadvisable—to address the reader directly.</p>
<p>GETTING CHATTY</p>
<p>Though not quite as bad as addressing the reader, “getting chatty” also takes a toll on reader immersion and enjoyment. Here, the author writes narration as if speaking to the reader, but without actually resorting to the word <em>you</em>. For example: “He was drinking coffee from one of those big cafeteria roasters.”</p>
<p>When describing something in the third person, you don’t say things like “one of those;” rather, you describe the thing as what it is, outside of shared observations and experiences. (“He was drinking coffee from a big, cafeteria-style roaster.”) </p>
<p>Because you-the-author are not present in the story, you have no shared observations or experiences to draw upon. You are (or should be) invisible; the reader should share observations and experiences with the characters, because this draws them deeper into the story. Being chatted up by the author, on the other hand, pulls them out of the story.</p>
<p>Another chatty passage: “It was a familiar smell, they knew it, every homicide has its smell, but no one ever quite gets used to it.” Here, the use of <em>no one</em> makes this chatty. It’s important to understand why:</p>
<p>This is not internal monologue, so we’re not reading the thoughts of any particular character. Nor is it dialogue. Just as clearly, it’s not directed at any particular character within the story. That makes it narration—but it’s not written like third-person narration; instead, it’s written as though the author were speaking to someone. </p>
<p>Obviously, the author isn’t speaking to anyone inside the story. Therefore, he must be addressing someone <em>out</em>side the story. That leaves but one possibility: the reader. And ten out of ten publishers surveyed agree—you can’t do that, for reasons stated above.</p>
<p>Now, if the passage is changed to read “It was a familiar odor. Every homicide had its smell, but Malone never quite got used to it”—the chattiness issue disappears, because it’s now clear <em>who</em> is being referred to: Malone. The more generalized “no one,” on the other hand, includes the reader—and is therefore chatty.</p>
<p>A different example: </p>
<p>“You said to bring him back in chains.”<br />
Well, that’s not quite what she’d said, or at least meant, but…</p>
<p>Just who is saying <em>well</em> here? Obviously, it’s <em>intended</em> to be the character&#8217;s train of thought—but it <em>reads</em> like the author, chatting with the reader. Again, be on the lookout for tense issues when reviewing these passages.</p>
<p>Exceptions include first-person narration, some comedies, and screenplays.</p>
<p>AUTHOR COMMENTARIES</p>
<p>Occasionally, an author feels the need to explain something that is somehow not obvious from a reading of the story itself. Avoid the temptation to do this with comments inserted in parentheses, brackets, or footnotes. </p>
<p>Think of the reader’s thought process: <em>Oh, a note. Who put this here? The author.</em> Suddenly, your audience is thinking about you, and not the story.</p>
<p>Instead, weave the information into the tale in such a way that it <em>is</em> obvious (but not obviously expository) when reading the story. If this is not possible (which almost never happens), put the information in a foreword, introduction, author’s note, afterword, or appendix. Don’t “break the read&#8221; by sticking it in the middle of your tale.</p>
<p>CONCLUSION<br />
Your job is to get the reader into the story, and keep him there until the very last page—entranced by a spell woven with words. Anything that calls attention to the author, or reminds the reader that there is, in fact, an author—breaks that spell. </p>
<p>It is as if you were making love to your wife or husband, and the person who introduced you suddenly barged into the room shouting, “Aren’t you glad I brought you two together?”</p>
<p>Go over all of your writing with an eye toward author intrusion, and delete or rephrase as needed. Not just where author presence is clear (addressing the reader or inserting comments)—but also where it may be open to interpretation (getting chatty).</p>
<p>Absent one of the exceptions mentioned above—or instances where you’re being intentionally unclear for other reasons—the reader should always be absolutely clear on who is being addressed, and by whom. The reader should <em>not</em> be directly addressed, chatted up, or given notes.<br />
<HR align=center width=400></p>
<p>Author <a target="_blank" href="http://www.selfeditingblog.com/author/">John Robert Marlow</a> is available for professional editing, development, and consultation. If you&#8217;d like help taking your work to the next level, <a href="http://www.selfeditingblog.com/contact/">contact John here</a>. <div class="wp-caption alignright" style="width: 97px"><a href="http://www.selfeditingblog.com/author/"><img alt="JRM" src="http://www.selfeditingblog.com/g_authorshot (100h).jpg" width="87" height="100" /></a><p class="wp-caption-text">JRM</p></div></p>
<p>copyright &copy; by John Robert Marlow<br />
all rights reserved</p>
]]></content:encoded>
			<wfw:commentRss>http://www.selfeditingblog.com/hey-look-at-me/427/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Bouncing Eyeballs</title>
		<link>http://www.selfeditingblog.com/bouncing-eyeballs/335/</link>
		<comments>http://www.selfeditingblog.com/bouncing-eyeballs/335/#comments</comments>
		<pubDate>Sat, 04 Jul 2009 18:38:35 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Style]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=335</guid>
		<description><![CDATA[Bouncing Eyeballs and Other Unintended Meanings by John Robert Marlow
LITERAL VS. FIGURATIVE
Unintended meanings are mood-killers. This is as true on the page as is it is in life: you say one thing, your listener hears another, and trouble soon follows. They heard every word you said, and accurately too—but they ...]]></description>
			<content:encoded><![CDATA[<div id="attachment_336" class="wp-caption aligncenter" style="width: 530px"><a href="http://selfeditingblog.com/bouncing-eyeballs/335/" title="Bouncing Eyeballs and Other Unintended Meanings by John Robert Marlow" width="520" height="212" /></a><p class="wp-caption-text">Bouncing Eyeballs and Other Unintended Meanings by John Robert Marlow</p></div>
<p>LITERAL VS. FIGURATIVE</p>
<p>Unintended meanings are mood-killers. This is as true on the page as is it is in life: you say one thing, your listener hears another, and trouble soon follows. They heard every word you said, and accurately too—but they took those words to mean something very different from what you intended. </p>
<p>Consider the following passage:</p>
<p>“His eyes bounced between Teddy, Mandy, the girl, the geologist, then back to Franklin.” Read literally, this tells us that “his eyes” are flying around the room, bouncing between characters like a pinball between posts. And while it’s true that very few readers are going to take this figure-of-speech sentence literally, many will nonetheless read it the wrong way. When they do, one of two things will happen: they will stop, go back, and read it again to clarify—or they will laugh. The first reaction is never good; it “breaks” the read and kills momentum. In a work not intended to be comedic, the second reaction is also not-good.</p>
<p>When I first read this bit (an actual line from one of the manuscripts I’ve edited, though the names have been changed to protect the innocent), it conjured up images of John Anderton in the film <em>Minority Report</em>, chasing his freshly-dropped eyeballs as they bounced down the corridor at Precrime. Aiding and abetting this impression was the fact that, in this particular manuscript, one of the first murder victims had his eyeballs scooped from his head—making a literal sentence about bouncing eyeballs somewhat more credible than might otherwise be the case.</p>
<p>Another zinger: “Judy’s eyebrows jumped like she was impressed, then walked toward the front door and stopped at the fish tank.” That’s one lively pair of eyebrows. It is of course Judy doing the walking. So here again, we have a perfect example of grammar gone slightly askew, and completely changing the sentence’s intended meaning&#8211;so much so that, in this instance, there is no multiple choice: the unintended meaning&#8211;walking eyebrows&#8211;is the only one present. &#8220;Judy raised her eyebrows as if impressed, then walked toward the front door and stopped at the fish tank,&#8221; on the other hand, would at least be clear, if poorly constructed.</p>
<p>DANGEROUS SITUATIONS</p>
<p>You might expect such unintended meanings to be rare, but this is not so. Most manuscripts have at least a few—admittedly less bizarre—multiple-choice sentences. The vast majority are unique to the stories in which they appear. Still, when you’ve read enough manuscripts, you begin to notice that certain. grammatically dangerous situations lend themselves to particular variants of this problem.</p>
<p>One that pops up consistently goes something like this: Our heroes—call them Dick and Gwendolyn—are trapped in an old warehouse, where they’re hunted by armed thugs. Dick ambushes Thug One and takes his gun. Telling Gwendolyn to stay put, Dick moves forward, gun at the ready. Suddenly, Thugs Two and Three appear. The next line is:</p>
<p>Dick shot Gwendolyn a glance.</p>
<p>Tense scene, mounting suspense, edge-of-the-seat reading and then—<em>Dick shot Gwendolyn?</em> Of course not but, thanks to unfortunate grammar, that’s the way it reads. And that’s your reader’s first impression. It doesn’t matter how skillful you’ve been to this point, or how much suspense, drama, and reader involvement you’ve managed to create—it’s all gone, right there. Shot to hell, you might say, along with poor Gwendolyn. The good news is, the heroine will recover. The bad news is, the writer may not. </p>
<p>Quick tip: when you’ve got characters running around with projectile weapons, thinking they may have to shoot someone, never—<em>ever</em>—use the word “shot” unless someone has in fact fired a gun (or crossbow, or whatever). In different circumstances, this phrasing is perfectly acceptable; here, it is not.</p>
<p>MUDDLED MEANINGS</p>
<p>Unintended meanings are not always so dramatic but, dramatic or otherwise, they <em>do</em> always interfere with a clear, smooth-flowing read. This holds true for both fiction and nonfiction. </p>
<p>In this example, we have a character kneading a small, pliable object: “Now the size and shape of a pistachio, or tiny football, he achieved what he wanted and gently laid it to rest inside a wooden cigar box.” Read literally, this says that <em>he</em>—meaning our character—has somehow become the size of a pistachio.</p>
<p>More often, unintended meanings are mundane, and lead readers astray on such simple matters as choreography (specific physical actions and the order in which they occur), or which character performed a specific action or spoke a particular line of dialogue:</p>
<p>“O’Rourke was dead, shot in the head by an off duty cop fleeing the scene of a robbery.” It’s clear that O&#8217;Rourke is dead—but was he shot while he (O&#8217;Rourke) was fleeing the scene of a robbery, or was he shot by a cop who was himself fleeing the scene of a robbery? Even without crooked cops (which this story had), the meaning is not quite clear. Also unclear is whether the person fleeing the scene of the robbery actually committed that robbery. </p>
<p>The addition of a single word would clarify this: “O’Rourke was dead, shot in the head by an off duty cop <em>while</em> fleeing the scene of a robbery.” (To get the opposite meaning, add two words: “O’Rourke was dead, shot in the head by an off duty cop <em>who was</em> fleeing the scene of a robbery.” Still, the phrasing itself—a cop <em>fleeing</em> a crime scene—runs sufficiently against expectations as to warrant rephrasing, or the addition of a second, clarifying sentence. Even though the meaning is technically clear, the reader may <em>think</em> he’s misread it.)</p>
<p>Another example: “I pulled into the trees, trying to get Frank’s car out of sight and then turned around so I could see whoever came down the road and waited.” This reads as if the narrator is hoping to see someone who comes down the road and waits, but is meant to tell us that the narrator is waiting to see someone who comes down the road. The unfortunate addition of the phrase “Frank’s car” introduces a point of possible confusion here: is the narrator looking at Frank’s car and trying to ensure that he himself cannot be seen by anyone who’s already in (or might get into) Frank’s car—or is he himself driving Frank’s car? A third point of confusion: is the narrator turning around, or is he turning a car around?</p>
<p>“It’s a friend of hers, her son, punk kid.” Is it a friend of hers, or a friend of her son’s? And who’s the punk kid—her son, or her friend’s son?</p>
<p>““He really does look much healthier again,” she said as they walked into the market.” In this scene, two women are walking together—but which is speaking? Because the speaker is not identified, the line could be read as having been spoken by either character. </p>
<p>As writers, we’re expected to have an exceptional facility with language. With few exceptions (political speechwriting and a few ex-presidents come to mind), we are in the business of making ourselves perfectly clear. Unintended ambiguity—“multiple choice sentences” that can be read in more than one way—do a disservice to both reader and writer. </p>
<p>Exceptions are few: situations where a character is deliberately employing multiple meanings (think of Klaatu in the remake of <em>The Day the Earth Stood Still</em>, saying “I’m a friend to the earth”), or where you as author are doing the same for purposes of deception, comedic effect, etc.</p>
<p>CONCLUSION</p>
<p>Unintended meanings are the antithesis of good writing. The reader is taken out of the moment, plucked from the world of the story like Dorothy from Kansas, or Neo from the Matrix. What should have been dramatic is now confusing or&#8211;worse&#8211;comedic. The spell we’ve worked so hard to weave is now broken; the reader who a moment ago didn’t know the real world existed, now marveling at our ineptitude. </p>
<p>Multiple meanings creep into our work—and, often, remain there—for the same reason typos do: we as authors know how the sentence is <em>supposed</em> to read, and so that’s the way we read it, regardless of what’s actually on the page. For us, only one meaning is possible. For someone unfamiliar with the work (and with what was going through our heads when we wrote it), the meaning of each sentence is conveyed by the words of which it is composed—and nothing else.</p>
<p>So as you write, keep this question in the back of your mind: Is there any possible way to misread this sentence? If the answer is yes, rephrase it. When the manuscript is complete, proof it with the same question in mind. Then have someone else do the same. Hunt these sentences down without hesitation, pity, or remorse. </p>
<p>Then kill them—before they kill you.<br />
<HR align=center width=400></p>
<p>Author <a target="_blank" href="http://www.selfeditingblog.com/author/">John Robert Marlow</a> is available for professional editing, development, and consultation. If you&#8217;d like help taking your work to the next level, <a href="http://www.selfeditingblog.com/contact/">contact John here</a>. <div class="wp-caption alignright" style="width: 97px"><a href="http://www.selfeditingblog.com/author/"><img alt="JRM" src="http://www.selfeditingblog.com/g_authorshot (100h).jpg" width="87" height="100" /></a><p class="wp-caption-text">JRM</p></div></p>
<p>copyright &copy; by John Robert Marlow<br />
all rights reserved</p>
]]></content:encoded>
			<wfw:commentRss>http://www.selfeditingblog.com/bouncing-eyeballs/335/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
