<?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; Mechanics</title>
	<atom:link href="http://selfeditingblog.com/category/mechanics/feed/" rel="self" type="application/rss+xml" />
	<link>http://selfeditingblog.com</link>
	<description>Write, Edit and Sell Your Own Novel, Screenplay, or Nonfiction Book</description>
	<lastBuildDate>Mon, 17 Oct 2011 07:22:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Snucking Threw the Poring Reign (Part 2)</title>
		<link>http://selfeditingblog.com/snucking-threw-the-poring-reign-part-2/507/</link>
		<comments>http://selfeditingblog.com/snucking-threw-the-poring-reign-part-2/507/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 00:20:28 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Mechanics]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=507</guid>
		<description><![CDATA[Snucking Threw the Poring Reign: Mechanical Errors in Writing (Part Two)
by John Robert Marlow


As mentioned in Part One, writing mechanics are dull, but essential—like checking the oil and brake fluid when you’d rather be cruising down the coast. You can’t do one without keeping an eye on the other. So let’s take a look at another batch of common mechanical errors…]]></description>
			<content:encoded><![CDATA[<p><a class="post_image_link" href="http://selfeditingblog.com/snucking-threw-the-poring-reign-part-2/507/" title="Permanent link to Snucking Threw the Poring Reign (Part 2)"><img class="post_image alignleft" src="http://selfeditingblog.com/g_SEB__post-image---Snucking_Threw_the_Poring_Reign_2.jpg" width="325" height="217" alt="Post image for Snucking Threw the Poring Reign (Part 2)" /></a>
</p><p>Snucking Threw the Poring Reign: Mechanical Errors in Writing (Part Two)<br />
by John Robert Marlow</p>
<p>As mentioned in Part One, writing mechanics are dull, but essential—like checking the oil and brake fluid when you’d rather be cruising down the coast. You can’t do one without keeping an eye on the other. So let’s take a look at another batch of common mechanical errors…</p>
<p>MORE WORD WRONGNESS</p>
<p>It’s been said that the hardest languages to learn are English and Mandarin Chinese. It’s easier when you’ve grown up with one or the other—but even native speakers find some things confuddling. Herewith, another round of confusingly similar and often misused words…</p>
<p>Farther/Further: Though frequently confused, each has its own distinct meaning: farther <em>always</em> refers to physical distance; further <em>never</em> refers to physical distance. So while the goal line on a football field may be <em>farther</em> away than ever after the quarterback is sacked in his own end zone, his goal of being named most valuable player is <em>further</em> away. </p>
<p><em>Far</em>, on the other hand, can be used in either situation: “How far is the goal line?” or “He’s a far worse player than you can possibly imagine.”</p>
<p>Effect/Affect: An <em>effect</em> is a result of some kind: “He spoke with great effect.” <em>Affect</em> denotes influence: “The audience was greatly affected by his speech.” You can even use both in the same sentence, though this can look a tad silly: “The effects of the nuclear detonation adversely affected the city.</p>
<p>Appraise/Apprise: To <em>appraise</em> something is to estimate its value or quality: “When Tiffany had her wedding ring appraised, she discovered that the diamonds were fake;” “Sergeant McGillicuddy appraised the situation on the battlefield.”</p>
<p>To <em>apprise</em> is to inform or convey information: “Tiffany was apprised of the ring’s true quality;” “Sergeant McGillicuddy apprised his superiors of the situation.” Again, you can use both, but it looks odd: “Sergeant McGillicuddy appraised the diamond, and apprised General Tiffany of its value.”</p>
<p>Adverse/averse: <em>Adverse</em> means unfavorable, hostile or harmful: weather can be adverse, as can circumstances or side effects. People are <em>never</em> adverse.</p>
<p><em>Averse</em> means unwilling, opposed, or disinclined toward. This word does apply to people, and is always followed by the word <em>to</em>, which is in turn followed by whatever it is the person finds disagreeable: “Baby Finster is averse to Brussels sprouts;” “The new CEO has an extreme aversion to honest labor.”</p>
<p>Ordinance/ordnance: <em>Ordinances</em> are official rules and regulations: “There’s a city ordinance against sleeping in the park.” <em>Ordnance</em> refers to military hardware, and is most often used to mean explosives of some sort: “There’s enough ordnance here to orbit the Washington Monument.” Wars only work with ordnance; replace that with ordinance, and all you’ve got is a city council meeting.</p>
<p>TENSE SITUATIONS</p>
<p>Most novels are written in third person, past tense: “Amos wrestled the alligator in the swamp.” A few are written in first person, past tense: “I wrestled the alligator in the swamp.” Fewer still are first person, present tense: “I wrestle the alligator in the swamp. He bites my arm off.” Screenplays are almost universally written in third person, present tense: “He wrestles the alligator in the swamp. It swallows him whole.” </p>
<p>Second person narration—in which the main character is referred to as “you”—is seldom used in English-language tales.</p>
<p>In all cases, problems arise when the writer slips from one tense into another, as in this example from character dialogue: “What the hell do you think you were doing?” </p>
<p>Here, <em>do</em> is present tense, <em>were</em> is past. So to be consistent, the sentence must read either: “What the hell do you think you’re doing?” [present tense], or “What the hell did you think you were doing?” [past tense].</p>
<p>In this example, we switch from present to past tense: “If there is [present] one thing Frankie knew [past] to do, it was [past] how to cover his own ass.” The grammar here is also in trouble, and there seems to be a word misplaced or missing. </p>
<p>What the writer <em>wanted</em> to say was this: “If there was one thing Frankie knew how to do, it was cover his ass.” Grammatically, even this could be improved—but it would likely lose “punch” in the process.</p>
<p>Things can also go the other way—from past to present: “One thing Mark couldn’t [past] stand is [present]…” (Which, of course, needs to read” “One thing Mark couldn’t stand <em>was</em>…”) Another example: “The least the devil could have [past] done was [past] to make sure that the air-conditioning is [present] working.” (This should end with &#8220;<em>was</em> working.”)</p>
<p>Occasionally, writers will mix past and future tenses: “Mrs. Branch and Prince Juniper were [past] flying to Spain tomorrow [future] to meet with the owner of a partially-constructed treehouse they were [past] interested in buying.” Or: “The test wasn’t [past] starting [present or—in this case—future] until noon.”</p>
<p>Another example: “He’ll find out eventually that she’d duped him.” <em>He’ll</em> (he will) is future, <em>she’d</em> (she had) past. This needs to read either: “He’ll find out eventually that she’s duped him,” or “He’d find out eventually that she duped him.” (And, really, each sentence would read better if it began with “Eventually.”)</p>
<p>Sometimes, a writer will bounce between tenses: “I noticed [past] that incongruously, he is [present] wearing a double-breasted wool suit in the Sahara, which appears [present] to be one of the hottest places on earth. The suit probably explains [present] why he keeps [present] the air conditioning on an icy blast. He turned [past] back to me, and seemed [past] surprised [past] I was [past] still there.” </p>
<p>There are a number of problems here, but what concerns us now is this: the entire passage should be written in past tense.</p>
<p>Some sentences are so badly mangled tense-wise that they’re either impossible to salvage, or not worth the effort: “I’m here only because a judge ordered this visit so that I could assure you someone knew what happened to you, and I could make sure you aren’t being abused.”</p>
<p>In such cases, a total rewrite is called for: “I’m here because a judge ordered this visit. He wants to assure you that the court is aware of your situation. I’ve been instructed to ask if you’re being well-treated.”</p>
<p>Be particularly careful when you use the word <em>had</em>, or any other word ending in <em>’d</em>, because it’s easier to slip up when one of these is present. “It had been a long time since she was intrigued by a guy,” for instance, should be: “It had been a long time since <em>she’d been</em> intrigued by a guy.”</p>
<p>Often—but not always—the presence of <em>had</em> in a sentence requires the use of an <em>’d</em> word, or another <em>had</em>. Seldom will the word <em>was</em> appear in the same sentence as <em>had</em>. (“She’d already told him she was a leper, and so she failed to understand his surprise when things started falling off,” would be an exception.)</p>
<p>SINGURALS AND PLINGULARS</p>
<p>It’s surprisingly easy to find yourself on the wrong end of a singular—or plural, for that matter. Singular-plural mix-ups are fairly common, and look like this:</p>
<p>“Anchovies, as I recall, was on your wish list.” And this: “Hers were one of many.” And this: “Samantha liked the architecture in this part of Dubai; lovely modern buildings, each their own signature piece.”</p>
<p>The first two are fairly simple. Because <em>anchovies</em> is plural, the writer must use <em>were</em> (which is also plural) instead of <em>was</em> (which is singular): “Anchovies, as I recall, were on your wish list.” Likewise, <em>one</em> is singular, and <em>were</em> plural—so when referring to <em>one</em> of many, the writer must use <em>was</em>: “Hers was one of many.”</p>
<p>In the first two examples, it’s immediately clear what’s being referred to: <em>anchovies</em> and <em>one</em>. Which makes it a simple matter to choose between <em>was</em> and <em>were</em>. </p>
<p>The third example is a bit more complicated: what are we really talking about here—architecture, or buildings? Neither, as it turns out; the specific word being referenced here is <em>each</em>. Because each is singular, the last part of this sentence should read: “each <em>its</em> own signature piece.”</p>
<p>How do we know that <em>each</em> is the key word here? By asking this question: “<em>What</em> is a signature piece?” Is architecture a signature piece? No, that’s too broad. Modern buildings? No again; how can “modern buildings” be “a signature piece?” What about “each?” Eureka! <em>Each</em> “modern building” is a signature piece. And because <em>each</em> is singular, we must use <em>its</em> (also singular) and not <em>their</em> (plural). </p>
<p>But, really—in this case, at least—we don’t even have to go through all of that. The answer is contained in the question: “<em>What</em> is a signature piece?” A <em>signature</em> <em>piece</em> is singular (<em>signature pieces</em> would be plural)—and so it must be referring to something else that is also singular: <em>each</em>.</p>
<p>Whatever is being <em>most directly referred to</em> determines whether the sentence should employ singular or plural words. Here, the sentence is referring to “architecture” in a general sense, and “modern buildings” in a collective and indirect sense—but “each” is clearly the main focus.</p>
<p>Think of it this way: you’re traipsing through the Alaskan wilderness. Majestic, snow-capped mountains rise in the distance. Sunlight glitters off a nearby river. Gorgeous pine trees dot the landscape. </p>
<p>It’s all quite beautiful, really—but the thing you should be concentrating on is that charging grizzly, and whether he has a buddy. Because if it’s one bear, your biographer will write” “The bear was hungry.” And if it’s two bears, he’ll write “The bears were hungry.”</p>
<p>Sometimes, the problem is a simple typo: “He detested the lack of compassion most detectives had toward the victim[s] and their families.” Occasionally, it’s hard to see how the wrongness was arrived at: “Frank spoke softly to the man, “Your eyes were scooped out like a grape.”” Even then, however, the fix is clear: ““Frank spoke softly to the man. “Your eyes were scooped out like grapes,” he said.”</p>
<p>Finally, two perilous situations that often lead writers astray. The first has to do with people (or other creatures or things) standing beside something—usually a doorway.</p>
<p>“A soldier stood on both sides of the door.” For this sentence to stand as it is, the soldier would have to be in two places at once—the left <em>and</em> right sides of the door. <em>A soldier</em> is singular; <em>both</em> is plural. </p>
<p>“A soldier stood on <em>each</em> side of the door” may be grammatically correct, but—owing to the unintended double meaning—presents the same absurd image in the reader’s mind.</p>
<p>The solution is to abandon the sentence structure entirely, and instead write something like this: “Two soldiers stood by the door.” Most readers will assume that means one soldier per side—but if you want to get specific, say: “Two soldiers flanked the door.”</p>
<p>The other situation often arises in connection with arms. (The kind attached to characters.) A typical example: “He edged out over the roof. His stomach churned. His arms were limp at his side.” </p>
<p>With two arms on one side like that, he might just lose his balance and fall off. When referring to a character’s arms (or anything else there’s more than one of) being at his <em>sides</em>, always double-check to be sure you didn’t say <em>side</em> instead.</p>
<p>TYPOS</p>
<p>We all know the typo. Fingers flying over the keyboard, we hit the wrong key (or several wrong keys). Or we forget to hit the right key (or several right keys). Occasionally, the results are amusing or embarrassing; more often they’re not. And they <em>always</em> make us look sloppy.</p>
<p>Typos are like beetles; there are so many different kinds, it’s hard to keep track. Most, though, fall into a few broad general categories: wrong letters, extra letters, missing letters; wrong words, extra words, missing words. </p>
<p>And then there was the guy who accidentally hit a macro key, and put his lonely-hearts personal ad in the middle of his manuscript.</p>
<p>Mr. Lonely Hearts aside, the trouble with typos is this: we, as authors, know how the words are <em>supposed</em> to read—and so we tend to see what <em>should</em> be on the page, rather than what’s actually there. Our cranial spell-checkers autocorrect spelling errors, fill in missing words, subtract extra ones. But, of course, this only works for us.</p>
<p>The moment someone else reads the thing, every error stands out like a spotlight, illuminating our seeming incompetence. At best, we look lazy; at worst, illiterate. In either case, the result distracts the reader and interferes with his enjoyment of the tale being told.</p>
<p>The solution is simple: first, run a spelling and grammar check. This will catch many errors, but won’t come close to catching them all. (It may also flag things that aren’t errors, or suggest some fixes that shouldn’t be made.)</p>
<p>Next, hand the finished work to someone else to read, and ask them to mark every single error they spot. Needless to say, they should have a firm grasp of the language you’re writing in, and should also be willing to take the considerable time necessary to do this. </p>
<p>Make the appropriate corrections and repeat as needed, with a new reader each time. Then take a fresh look at it yourself; often, a little time away from the story can help you to spot things you missed in a previous read.</p>
<p>Finally, finances permitting, consider sending the finished work to someone who makes his living spotting and correcting writing problems—a professional editor.</p>
<p>CONCLUSION</p>
<p>Again, not exactly pulse-pounding stuff—but stuff you can’t ignore. Because it’s hard for readers to enjoy the ride when there’s a racket under the hood, caused by a dozen untended mechanical problems. You want your story running like a well-tuned Maserati.<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: 87px">
	<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>
<div style="clear:both;height:10px;"></div>
]]></content:encoded>
			<wfw:commentRss>http://selfeditingblog.com/snucking-threw-the-poring-reign-part-2/507/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Snucking Threw the Poring Reign (Part One)</title>
		<link>http://selfeditingblog.com/snucking-threw-the-poring-reign/438/</link>
		<comments>http://selfeditingblog.com/snucking-threw-the-poring-reign/438/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 04:11:27 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Mechanics]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=438</guid>
		<description><![CDATA[Snucking Threw the Poring Reign: Mechanical Errors in Writing (Part One)
by John Robert Marlow


“Mechanical errors” have to do with the nuts and bolts of writing. If concept is your flashy car, plot the engine, characters the driver and passengers—then story mechanics are the fasteners holding your engine together. They’re not exciting, glitzy, or personable, and no one pays them any mind. Until something goes wrong. ]]></description>
			<content:encoded><![CDATA[<p><a class="post_image_link" href="http://selfeditingblog.com/snucking-threw-the-poring-reign/438/" title="Permanent link to Snucking Threw the Poring Reign (Part One)"><img class="post_image alignleft" src="http://selfeditingblog.com/g_SEB__post-image---Snucking_Threw_the_Poring_Reign_1.jpg" width="325" height="215" alt="Post image for Snucking Threw the Poring Reign (Part One)" /></a>
</p><p>Snucking Threw the Poring Reign: Mechanical Errors in Writing (Part One)<br />
by John Robert Marlow</p>
<p>&#8220;Mechanical errors&#8221; have to do with the nuts and bolts of writing. If concept is your flashy car, plot the engine, characters the driver and passengers—then story mechanics are the fasteners holding your engine together. They&#8217;re not exciting, glitzy, or personable, and no one pays them any mind. Until something goes wrong. </p>
<p>That&#8217;s when you hear an annoying clank, somewhere under the hood. Soon, it becomes difficult to hear the passengers or enjoy the scenery. Before too long, that <em>clank-clank-clank</em> is all you can think about. And if someone doesn&#8217;t climb under the hood and fix the damned thing, it will eventually stop your engine.</p>
<p>So let&#8217;s take a look at some of the more common mechanical errors&#8230;</p>
<p>WRONG WORD</p>
<p>There are two ways to use the wrong word. The first is simple inattention; we&#8217;re buzzing along, lost in the moment, and inadvertently type a real word that&#8217;s quite similar to—but not—what we intended. Common culprits include here/hear, there/their/they&#8217;re, your/you&#8217;re, through/threw, passed/past, and lightning/lightening. There&#8217;s no misunderstanding involved; somewhere between our brain and our fingers, the signal gets scrambled. </p>
<p>In other cases, the wrong (usually similar) word is employed because the writer is unclear on the word&#8217;s actual meaning. Frequently, the correct term is one not often seen in print, making an error that much more likely. A few common culprits in this category:</p>
<p>Peaked/Piqued: It&#8217;s easy to get this one wrong, and many writers do. While the phrase &#8220;peaked her interest&#8221; may seem correct, it is not; the proper phrase is &#8220;piqued her interest.&#8221; This is because her interest is not peaking, but being aroused, which is what <em>piqued</em> means. (Just to make things complicated, <em>pique</em> can also mean to arouse anger or resentment, but this usage is rarely seen.)</p>
<p>Pour/Pore: Rain pours down. People pour water, soup, tea and other liquids. One does not <em>pour</em> over a document, unless one has a fondness for runny ink. Instead, one <em>pores</em> over the document. To &#8220;pore&#8221; is to study intently. (Pore has other meanings as well; fortunately, none of them are relevant here.)</p>
<p>Reign/Rein/Rain: <em>Reign</em> is what a king, queen, or other dominant entity or force does. &#8220;The king reigned for fifty years&#8221; means the king was, well, king for half a century. A reign ends when the reigning entity is replaced. In the computer industry, IBM reigned supreme—until Microsoft came along. Ideas can also reign.</p>
<p><em>Reins</em> are straps used to control horses. When you see a carriage driver in a movie, holding a bunch of leather straps in his hands as he drives—those are reins. He who controls the horses &#8220;holds the reins.&#8221; Pulling on the reins signals a horse to stop; hence the phrase &#8220;rein him in.&#8221;</p>
<p><em>Rain</em> falls on your head from the sky. Or falls on your umbrella, if you&#8217;ve planned ahead. Most of the confusion occurs between reign and rein. For a prominent example of this, look closely at the <em>Forbes</em> magazine cover in the <em>Iron Man</em> movie—where you&#8217;ll see the words &#8220;Tony Stark takes reigns at 21.&#8221;</p>
<p>Hoard/Horde: Neither of these is oft-seen in print, making for a constant source of confusion when writing off the cuff. You can&#8217;t horde gold, nor can you be attacked by a hoard of angry editors. A <em>horde</em> of angry editors is another matter altogether, because a horde is a vast crowd or mob—usually of people, but sometimes of other creatures: <em>A horde of orcs spewed from the cave like a raging river.</em></p>
<p>A <em>hoard</em> is a great amount of something (typically inanimate) that has been gathered up and kept (and often hidden): a <em>dragon&#8217;s hoard</em> of treasure, for instance. Hoard can also mean the act of gathering up a great amount of something: <em>The dragon hoarded trespassers, thus ensuring a steady supply of knight flambé to see him through the winter.</em></p>
<p>Sneak/Sneaked/Snuck: <em>Snuck</em> is not a word. Examples of proper usage in various tenses: &#8220;We&#8217;ll sneak into the morgue tonight and say our goodbyes to Ignatius.&#8221; &#8220;I sneaked into Ignatius&#8217; house this morning, and grabbed his favorite hat.&#8221; &#8220;Ignatius sneaked into the lion&#8217;s cage last night, but he didn&#8217;t sneak out.&#8221; The past tense of <em>sneak</em> is <em>sneaked</em>. Always. </p>
<p>Some would argue that, by sheer dint of recent widespread usage, <em>snuck</em> has sneaked into the lexicon and is in fact a real word—which is sort of like saying that someone who sneaks into the final semester of medical school is a doctor. Whatever the case, it is appallingly bad form—the grammatical equivalent of saying &#8220;He ain&#8217;t got none&#8221;—and should be avoided, outside of dialogue spoken by characters with appallingly (and intentionally) bad grammar.</p>
<p>SPEAKER ATTRIBUTION</p>
<p>There are two ways to go astray here: too much, and too little. When two characters are conversing, there&#8217;s no need to use the speaking character&#8217;s name with every line of dialogue. Give the reader credit for being able to follow along for a few sentences. Identifying the speaker every third or fourth time someone speaks is a good rule of thumb.</p>
<p>In situations where more than two characters are speaking, on the other hand, you&#8217;ll almost always want to identify the speaker with each spoken line, and also let the reader know which character is being addressed. Without this, it becomes very easy to lose track of who&#8217;s saying what. When that happens, the reader backtracks and rereads to clarify—and that&#8217;s always bad.</p>
<p>Sometimes you&#8217;ll do this with one character saying another&#8217;s name to get his attention. (&#8220;Go to hell, Bartholomew.&#8221;) More often, you&#8217;ll drop a clue into narration. (&#8220;&#8221;Hildegard glared at Ignatius. &#8220;Well I guess he&#8217;ll see you there,&#8221; she said.&#8221;)</p>
<p>Timing is another important aspect of speaker attribution. One of the most common mistakes is giving a character a lengthy bit of dialogue, and identifying the speaker at the end of it. (&#8220;&#8221;Four score and seven years ago, our fathers brought blahdeblahblahblah,&#8221; said Lincoln.&#8221;) </p>
<p>The problem here is that the reader is unable to place the line(s) into context and character voice until the entire passage has been spoken. This, in turn, cuts them loose from the story, leaving them to wonder &#8220;Who&#8217;s saying this?&#8221; when they should be carried along in the moment.</p>
<p>The solution is simple: move the attribution forward. (&#8220;Four score and seven years ago,&#8221; said Lincoln, &#8220;our fathers blahdeblahblahblah.&#8221;) Problem solved.</p>
<p>FLIPPERS</p>
<p>&#8220;Flippers&#8221; are sentences that are (more or less) written backward. Because portions of the sentence are presented in a less-than-ideal sequence, they have to be &#8220;flipped&#8221; in order to read well. Most sentences can be put together in more than one way. There may even be several grammatically correct options. But there is only one best way to say what needs to be said.</p>
<p>With occasional exceptions,  sentences should be constructed like this: who-what-how. Character first, followed by what they&#8217;re doing, followed (if at all; most of the time this isn&#8217;t needed) by the way in which they&#8217;re doing it. &#8220;John opened the door slowly,&#8221; not &#8220;Slowly, John opened the door.&#8221; The first reads smoothly; the second forces the reader to break rhythm, so to speak—which is why I didn&#8217;t just say &#8220;Smoothly, the first reads.&#8221; </p>
<p>Put another way: if someone asked you how you went to the lottery office to cash in your million-dollar ticket, would you say, &#8220;Quickly, I went?&#8221; (If so, you <em>really</em> need to be reading this.) Of course not. Why? Because it&#8217;s backward. Instead, you&#8217;d say &#8220;I went quickly.&#8221;</p>
<p>Let&#8217;s look at all three possibilities&#8221; &#8220;Quickly, I went to the lottery office&#8221; (how-who-what) is an awkward mess with a built-in pause, and is difficult to read. &#8220;I went quickly to the lottery office&#8221; (who-how-what) is better, but unnecessarily awkward. &#8220;I went to the lottery office quickly&#8221; (who-what-how) is smooth, easy to read, and has the kind of structure we&#8217;ve all been conditioned to expect. The first two sentences are flippers; the third is what you&#8217;re looking for.</p>
<p>If you want to drive your reader (or editor) bonko in the shortest possible amount of time, write like this: &#8220;Slowly, he got out of bed. Leisurely, he dressed for work. Jauntily, he walked to the car. Casually, he started the engine. Happily, he smiled.&#8221; (This is also a great way to increase the price of a line edit or polish, because it ensures that every sentence will have to be restructured.)</p>
<p>There are exceptions to this, and it is perfectly possible to write a smooth-flowing how-who-what sentence that doesn&#8217;t need to be flipped—but even seasoned pros use this technique sparingly, because a string of them gets really annoying, really fast. Unpublished writers, on the other hand, are frequent flippers. </p>
<p>APOSTROPHE NOW</p>
<p>Apostrophes are often misused. It&#8217;s hard to tell whether this results from inattention or misunderstanding, but here&#8217;s the rule: with few exceptions, apostrophes signify contractions and possessives—and nothing else.</p>
<p>Contractions are shortened words: that&#8217;s for that is, wouldn&#8217;t for would not, could&#8217;ve for could have, you&#8217;re for you are, that sort of thing. By far the most troublesome word in this category is <em>it&#8217;s</em>, a shortening of <em>it is</em>. The confusion likely stems from the fact that, unlike other contractions, it&#8217;s looks like a possessive.</p>
<p>Possessives are words that signify possession. Some of these—his, her, their—sport no apostrophe. Others do: John&#8217;s, Marie&#8217;s, Smith&#8217;s, Jones&#8217;, building&#8217;s, truck&#8217;s (&#8220;The fire truck&#8217;s front end was buried in the building&#8217;s north side, where John Jones&#8217; office used to be&#8221;). </p>
<p><em>Its</em> is a possessive with no apostrophe: &#8220;The fire truck was on its side.&#8221; &#8220;The fire truck was on <em>it&#8217;s</em> side&#8221; makes no sense; what this actually says (because <em>it&#8217;s</em> is a contraction) is that the fire truck was on it is side. It&#8217;s and its are so commonly misused that it&#8217;s worth the effort to do a search on your finished work, and eyeball every instance of each word.</p>
<p>Further confusion arises when the word being designated as possessive already ends with an <em>s</em>. Is it Jones&#8217; or Jones&#8217;s, fortress&#8217; or fortress&#8217;s? A simple apostrophe after the <em>s</em> is better form, and makes for an easier read. (Technically, you can do the same with words ending in <em>z</em>, but that tends to look silly without a concluding <em>s</em>.) </p>
<p>Exceptions are debatable, and typically relate to things that aren&#8217;t really words: 1940&#8242;s—which can also be written as 1940s. The latter avoids the appearance of being a possessive. </p>
<p>&#8220;There were two hundred Jones&#8217;s in the phone book&#8221; doesn&#8217;t look good (but does look like a possessive, which it&#8217;s not)—but then neither does &#8220;Joneses.&#8221; In this case, consider using Miller instead of Jones, and the problem goes away. Or, if you&#8217;re stuck on Jones, rearrange the sentence: &#8220;There were two hundred listings in the phone book under Jones.&#8221;</p>
<p>CONCLUSION</p>
<p>Mechanical errors can pile up quickly, and often escape automated spell-checks. Fortunately, they are among the easiest problems to fix—once you know what to look for. So grab your toolbox and climb under the hood.<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: 87px">
	<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>
<div style="clear:both;height:10px;"></div>
]]></content:encoded>
			<wfw:commentRss>http://selfeditingblog.com/snucking-threw-the-poring-reign/438/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Repeat Offenders</title>
		<link>http://selfeditingblog.com/repeat-offenders/366/</link>
		<comments>http://selfeditingblog.com/repeat-offenders/366/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 01:28:47 +0000</pubDate>
		<dc:creator>John Robert Marlow</dc:creator>
				<category><![CDATA[Mechanics]]></category>

		<guid isPermaLink="false">http://www.selfeditingblog.com/?p=366</guid>
		<description><![CDATA[Repeat Offenders: Why Repetition is Bad Bad Bad
by John Robert Marlow


PETE &#038; REPETE

There’s an old joke that goes like this:

“Pete and Repete sat on a fence. Pete fell off. Who was left?”

“Repete”

“Pete and Repete sat on a fence. Pete fell off. Who was left…?”

The joke continues until the guy answering the question wises up. Too many budding authors never do.]]></description>
			<content:encoded><![CDATA[<p><a class="post_image_link" href="http://selfeditingblog.com/repeat-offenders/366/" title="Permanent link to Repeat Offenders"><img class="post_image alignleft" src="http://selfeditingblog.com/g_SEB__post-image---Repeat_Offenders.jpg" width="286" height="325" alt="Post image for Repeat Offenders" /></a>
</p><p>Repeat Offenders: Why Repetition is Bad Bad Bad<br />
by John Robert Marlow</p>
<p>PETE &#038; REPETE</p>
<p>There’s an old joke that goes like this: </p>
<p>“Pete and Repete sat on a fence. Pete fell off. Who was left?”</p>
<p>“Repete”</p>
<p>“Pete and Repete sat on a fence. Pete fell off. Who was left…?”</p>
<p>The joke continues until the guy answering the question wises up. Too many budding authors never do. I see this again and again and again. And again. The basic issue comes down to this: writers are expected—by agents, managers, editors, readers; everyone who matters, really—to have large vocabularies. Repetition indicates that the writer in question either: a) doesn’t know any better, or; b) can’t be bothered getting it right. The first screams “amateur;” the second, “lazy.” Neither is a word you want applied to you. Repetition can be deadly in any one of several, all-too-common forms:</p>
<p>REPEATING WORDS</p>
<p>As a general rule, avoid using the same word (or similar words) multiple times in quick succession, as this makes for a poor read. Word repetition creeps up on the best of writers, who often don’t notice while lost in the throes of creative passion. Professional writers do, however, notice on their next pass—and correct the problem before anyone else sees the manuscript. Amateurs don’t notice, or correct. </p>
<p>Often, a word will repeat twice in the same sentence, or in adjacent sentences. Occasionally—as with the sentence you just read—this is okay. But writers who are unaware of repetition tend to do it a lot, and most instances are not okay.  </p>
<p>A few simple examples: “She was whisked off in an unmarked car, which took her to the airport. Twenty minutes later, they were off to Belize.” “He pulled his gun, stuck Harry’s gun in his belt, and crept down the hall.” “Joan cried and ran to him and threw her arms around him.” In each of these sentences, one word repeats too often—<em>off</em>, <em>gun</em>, and <em>and</em>—and must be changed, even if that means restructuring the sentence. (Notice my artful use of the word <em>and</em>, three times in a row.)</p>
<p>A slightly more complex example: “Joan’s father thanked the police department and the public on his and his family’s behalf.” Here, <em>his</em> is the more obvious problem, but <em>and</em> is also a repeat—if lesser—offender. A simpler phrasing would be: “Joan’s father thanked the police and the public on the family’s behalf.” Because Joan’s father is a member of the family, the same meaning is conveyed.</p>
<p>This sentence has three repeaters: “Tears welled up in Bixby’s eyes and he averted his eyes to avoid O’Shea’s sympathetic gaze. O’Shea gazed out the window.”</p>
<p>Other instances are (or should be) more obvious: “The trail of blood suddenly stopped in a pool of blood at the edge of the road.”  A quick fix: “The blood-trail stopped at the roadside, where it formed a small pool.” Another example: “Joan called Madge and said she was back and safe and sorry she’d missed their appointment.” (Note the non-artful employment of the word <em>and</em> in this sentence.)</p>
<p>As an editor, it’s common to see the same word used two or three times in quick succession. Every now and then, I’ll see one word used five, six, even seven times in the space of three, perhaps four sentences. More often than not, that word is <em>he</em>,  <em>him</em>, <em>his</em>, <em>she</em>, <em>her</em>, or <em>hers</em>. Keep a sharp eye on him, her, and the rest of the gang.</p>
<p>REPEATING NAMES</p>
<p>Names are among the most common repeat offenders. Frequently, this occurs when a character’s name is used in dialogue, and then in narration—or vice versa. For example: ““Linda, wake up.” Linda heard the voice, as if in a dream.”</p>
<p>Occasionally, it happens when the writer is trying to sort out the choreography of a scene—as in the following sequence (the Sailors and the Skippers are rival gangs):</p>
<p>“Then one of the Sailors pointed toward Brother Sam. Two Skippers walked toward Brother Sam, the other one joined several other Sailors, who immediately circled him. Uncle Nathan and Peter quickly flanked Brother Sam.</p>
<p>Nick and Gordon were making their way to Brother Sam from the other side of the room, as the two Skippers reached Brother Sam and said something. Brother Sam waved off Nick and Gordon. Everyone, including several Skippers at the dance, breathed a sigh of relief.  </p>
<p>Brother Sam said something to Peter and Uncle Nathan. They nodded. Then Brother Sam quickly followed the two Skippers out of the auditorium.”</p>
<p>All told, that’s two Uncle Nathans, two Peters, two Nick and Gordons, three Sailors, four Skippers, and eight Brother Sams. Instead of clarifying events, such repetition tends to confuse matters. </p>
<p>At other times, an author will simply repeat the character&#8217;s name, every time that character is referred to (even if he&#8217;s the only guy in the scene)&#8211;so instead of mixing things up a bit and saying John, he, him, and his, the writer will say John, John, John, and John&#8217;s. For the reader&#8211;to say nothing of the editor&#8211;that way lay madness.</p>
<p>THE DREADED DOUBLE</p>
<p>The worst repeating-word offender is the “double,” in which the same word appears twice in a row. That makes it screamingly obvious&#8211;which, in the eyes of editors and agents, makes the writer that much less attentive for missing it. Often, doubles happen where sentences join, like this:</p>
<p>Bill handed the crocodile to Bob. Bob screamed when it bit his arm off at the shoulder. Shouldering his backpack, Bill bent down and picked Bob’s arm up off the street. The street was slippery, and Bill fell on his ass. His ass was sore where he hit the sidewalk. The sidewalk was slick because it had been raining. Rainwater rushed like a raging river along the street beside Bob and the crocodile. The crocodile bit Bob’s other arm off at the elbow, and fell into the water. The water swept the beast down the street and into the sewer, along with Bob’s arm.</p>
<p>Okay, I made that up—but I cannot tell you how many times I’ve seen the double in action, albeit in slightly less absurd scenes.</p>
<p>“Doubles” can also occur in the middle of a sentence: “He told me that that was the only way I’d ever see my children again.” Grammatically correct, but awkward. The same precise meaning is conveyed by the following sentence: “He told me that was the only way I’d ever see my children again.” (Come to think of it, the word “ever” could also be cut from this sentence, though its inclusion arguably makes the moment stronger.) As long as the set-up for this line adequately explains just what “the only way” is, all should be well.</p>
<p>Sometimes a character name will lead you into (or close to) a double. I found the following two sentences in the same manuscript: “She turned to Turner.” And “Turner turned toward the sound of the explosion.” Now, if the guy’s name had been Finnegan—no problemo. Something to think about when you use search-and-replace to change a character name throughout the manuscript.</p>
<p>Overall, the “double” is the easiest type of repetition to spot and correct. Writers who fail to catch these most likely sent the manuscript out the moment they typed “The End,” without bothering to read and “proof” it from start to finish.</p>
<p>Exceptions: Few and far between. “Doubles” are sometimes employed for comedic effect. Occasionally, when used in dialogue, they’ll indicate a character who habitually stutters (Ken in <em>A Fish Called Wanda</em>), or who is now stuttering under extreme stress (most often fear or grief). Very occasionally, a passage will be unclear or read awkwardly if repetition is completely eliminated. Rarely, “doubles” will result from an unavoidable sentence structure—one that cannot be changed without becoming awkward. Be aware, though, that this almost never happens, and should not be used as an excuse to leave a double in place. Always, <em>always</em> try to eliminate doubles.</p>
<p>DISTANT REPLAYS</p>
<p>Repetition can also be a problem when a word repeats pages, even chapters after its last occurrence. The more unusual the word, the less frequently it should occur. No one’s going to notice that you used the word “man” or “woman” two pages ago—but throw in “hermaphrodite” on page 26, and you can be sure that readers who see “hermaphrodite” on page 347 will remember having seen it before. The same is true of repeating phrases.</p>
<p>REPEATING PHRASES</p>
<p>Pretty much the same logic applies here. Sometimes, our own favorite phrases—ones we use in daily conversation—will creep into the writing. Which is fine, so long as they’re appropriate and well-placed. But what often happens is this: we’ll use the same phrase two, three, or more times without realizing that we’re repeating ourselves. Or we’ll think up a cool phrase and put it in, not realizing that we’ve already used it. </p>
<p>To the reader, this looks—at best—like lazy writing. At worst, it comes off like the ramblings of an old-timer who can’t remember what he told you two minutes ago—and so proceeds to tell you the same thing all over again.</p>
<p>Exceptions must have a purpose, and usually appear in dialogue. Perhaps the character repeating himself really is an addled old codger, and you’re illustrating this point by having him repeat himself. Or maybe he’s an ass who repeats instructions because he’s treating a subordinate like an idiot. Or he’s talking to someone who has trouble remembering things. <em>Or</em> (and I hope you’ve noticed that I’ve now begun three consecutive sentences with the same word)—my favorite—a character repeats a phrase he’s used before, tipping off the reader (or another character, or both) that he’s the same guy who used this phrase earlier.</p>
<p>This last technique was employed to good effect in the 2003 film <em>The Italian Job</em>—with a twist: here (spoiler coming), Stella’s conning Steve, who doesn’t know her but did know (and murdered) her father. Without even thinking about it, Stella uses a turn of phrase often employed by her father. Steve picks up on this, immediately realizing that she’s somehow connected to the man he murdered—and that Stella means him no good.</p>
<p>Phrases can be repeated for comedic, ironic, or dramatic effect. The film <em>A Perfect Murder</em> makes wonderful use of the ironic turnaround: lines like “What if there were no tomorrow?” and “That’s not happiness to see me” are each voiced by Steven and Emily (to each other, at different times) in emotionally charged scenes dripping with tension. The movie <em>300</em> has a magnificent turnaround line (three, actually) involving Queen Gorgo and Theron.</p>
<p>In <em>Strange Days</em>, Mace calls Lenny paranoid for thinking he’s being followed. Later, when their car is burning rubber to escape a hail of machine gun fire, Lenny says: “Oh no we’re not being followed, Lenny. Don’t be so paranoid, Lenny.”</p>
<p>Each of these exceptions has one thing in common: in every case, the repetition is intentional.</p>
<p>PARROTED DIALOGUE: THE “WILLIAM SHATNER MOMENT”</p>
<p>Dialogue is “parroted” when one character says something, and another immediately and unnecessarily repeats all or part of what was just said. The effect is, at best, comedic. Which is fine if: a) you’re writing comedy, and; b) the repetition is both intentional and funny. Probably ninety nine percent of the time, that’s not the case. </p>
<p>When <em>Star Trek</em>’s Captain Kirk (played by William Shatner) did this in the television series, it was intended to be dramatic. Today, it seems unintentionally comedic—a sort of so-bad-it’s-funny moment. Still, we groan rather than laugh. </p>
<p>Too many writers insert this kind of thing into their work without a second thought. Unfortunately, the technique is so overused it’s become a joke—literally: in the film <em>The Long Kiss Goodnight</em>, we see the following exchange:</p>
<p>Henessey: We found a note that’s in her handwriting.<br />
Nathan: She saw a note?<br />
Henessey: Who are you, William Shatner?</p>
<p>Here, it’s funny—and intended to be so. More often—almost always, in fact—it marks the writer as a novice, and swiftly becomes annoying.</p>
<p>Exception: When done—and done well—for comedic effect.</p>
<p>HE SAID, SHE SAID</p>
<p>One of the most common repeat offenders is the “He Said, She Said Syndrome,” in which every (or nearly every) line of dialogue is followed by “he said,” “she said,” or “[character name] said.” I once counted 34 of these in a row. Take it from an editor: few things get old faster than this. </p>
<p>Which does <em>not</em> mean that you should start substituting words like chortled, snorted, barked, and spat for said—but that’s a topic for another day. </p>
<p>INTENTIONAL REPETITION</p>
<p>Intentional repetition—whether of words, phrases, or whole passages—rarely works. I recall one writer who repeated entire paragraphs and conversations, with two different characters, in different places. His intention was to demonstrate an uncanny similarity in the lives of two strangers destined to meet. The effect was a distracting read during which I wondered why he’d take up so much space (in the first of an unpublished trilogy of phone book-sized manuscripts) with such obvious repetition&#8211;while at the same time marveling at what an unbelievable coincidence it was that the same exact events and conversations were taking place in the lives of two perfect strangers.</p>
<p>Any time you’re thinking of repeating something intentionally, ask yourself why. Then ask yourself whether the repetition has the intended effect. <em>Then</em> show it to someone else and ask them (without explaining your intended effect beforehand), because you’re biased. </p>
<p>For exceptions, see those listed under Repeating Phrases, above.</p>
<p>CONCLUSION</p>
<p>Repetition is, well, repetitive. As an author, you’re expected to have a lot to say. You’re also expected to have an unusually large vocabulary with which to say it. Repetition flies in the face of both expectations. It’s like having two noses, when you should have only one: it makes you look bad bad bad.</p>
<p>So give your writing a facelift, and dump those doubles—along with your other repeats.<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: 87px">
	<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>
<div style="clear:both;height:10px;"></div>
]]></content:encoded>
			<wfw:commentRss>http://selfeditingblog.com/repeat-offenders/366/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

