<?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>Regret the Error &#187; jmcintyre</title>
	<atom:link href="http://www.regrettheerror.com/author/jmcintyre/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.regrettheerror.com</link>
	<description>Mistakes Happen</description>
	<lastBuildDate>Mon, 19 Dec 2011 12:25:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>You Don&#8217;t Say: A primer on plagiarism</title>
		<link>http://www.regrettheerror.com/2009/07/14/you-dont-say-a-primer-on-plagiarism/</link>
		<comments>http://www.regrettheerror.com/2009/07/14/you-dont-say-a-primer-on-plagiarism/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 12:01:46 +0000</pubDate>
		<dc:creator>jmcintyre</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[You Don't Say]]></category>
		<category><![CDATA[chris anderson]]></category>
		<category><![CDATA[Plagiarism]]></category>
		<category><![CDATA[regret corrections]]></category>
		<category><![CDATA[virginia quarterly review]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=8582</guid>
		<description><![CDATA[By John E. McIntyre When Waldo Jaquith of The Virginia Quarterly Review discovered and published that Chris Anderson, the editor of Wired, had plagiarized passages from Wikipedia in his new book, Free, it provoked a lively, and sometimes alarming, discussion of plagiarism. Regret the Error has summarized the affair, and there are extensive comments on [...]]]></description>
			<content:encoded><![CDATA[<p>By John E. McIntyre</p>
<p>When Waldo Jaquith of The Virginia Quarterly Review<span style="font-style: normal;"> discovered and published that Chris Anderson, the editor of </span>Wired<span style="font-style: normal;">, had plagiarized passages from Wikipedia in his new book, </span>Free<span style="font-style: normal;">, it provoked a lively, and sometimes alarming, discussion of plagiarism. <o:p></o:p></span></p>
<p class="MsoNormal"><a href="http://www.regrettheerror.com/books/chris-anderson-admits-to-screwup-that-led-to-unattributed-passages-in-his-latest-book">Regret the Error</a> has summarized the affair, and there are <a href="http://www.vqronline.org/blog/2009/06/23/chris-anderson-free/">extensive comments</a> on the matter at the online edition of The Virginia Quarterly Review<span style="font-style: normal;">. </span><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">One reader&rsquo;s response at VQR<span style="font-style: normal;">: &ldquo;Don&rsquo;t care. Don&rsquo;t care. Don&rsquo;t care. This is more of the same garbage from academics discovering plagiarism and making a big stink where it isn&rsquo;t due. Take a fine-tooth comb to any recent publication and start googling. I bet you find a lot more than this.&rdquo; Another characterized the </span>VQR<span style="font-style: normal;"> article as a &ldquo;witchhunt.&rdquo;<o:p></o:p></span><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">While many students and even a fair number of journalists, as well as readers who &ldquo;don&rsquo;t care, don&rsquo;t care, don&rsquo;t care,&rdquo; appear to think of the Internet in general, and Wikipedia in particular, as a storehouse of ready-made prose available for the taking, there are still old-school writers and editors and teachers who see this casual copying-and-pasting as theft or cheating.<span style="">&nbsp; </span><o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">It is appalling to think that it may be necessary to restate to students and professional writers what constitutes plagiarism. But for the benefit of anyone who cut class that day, here is a short summary.<o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal"><b>Sources:</b><span style="font-weight: normal;"> Readers are entitled to know where information comes from. Sometimes footnotes or endnotes are appropriate, and citation within the text can usually be accomplished without clumsiness. Plagiarism, which cheats the reader by failing to disclose sources, comes in two forms: misappropriation of ideas and misappropriation of exact language. <o:p></o:p></span><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal"><b>Ideas:</b><span style="font-weight: normal;"> Information that is generally known and widely available from multiple sources does not require attribution. You do not need to cite a source if you write that John Wilkes Booth shot Abraham Lincoln in Ford&rsquo;s Theater on April 14, 1865. But if you write that he did so under the orders of Edwin M. Stanton, the secretary of war, you had better give the reader the source of your crackpot theory. <o:p></o:p></span><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal"><b>Language:</b><span style="font-weight: normal;"> If in recounting the laugh line in <i>Our American Cousin</i></span> &mdash; &ldquo;Well, I guess I know enough to turn you inside out, old gal &mdash; you sockdologizing old mantrap!&rdquo; &mdash; that Booth used for cover, you then write: &ldquo;The laughter and burst of applause almost covered the sound of a shot in the presidential box,&rdquo; you had better make sure that the second sentence is also within quotation marks and attributed to David Herbert Donald&rsquo;s <em>Lincoln</em><span style="font-style: normal;">.<span style="">&nbsp; </span><o:p></o:p></span><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">Chris* Anderson, in apologizing for the passages in his book lifted from Wikipedia, explained that there was a problem with the publisher in arranging for appropriate citation. But citation was not the only problem. Exact language from another source should run within quotation marks or set off in a block of type as well as being sourced by an appropriate citation. <o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">Perhaps it&rsquo;s necessary to make this even more explicit:<o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal"><b>Do not copy text from Wikipedia or any other source without indicating to the reader where it came from. <o:p></o:p></b><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">Plagiarism can be either deliberate or inadvertent. If inadvertent, it can result from carelessness &mdash; such as mixing one&rsquo;s notes from sources with one&rsquo;s draft &mdash; or from failure to understand what constitutes proper sourcing. <o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">A fellow copy editor once detected verbatim, unsourced sentences from Web sites in a reporter&rsquo;s copy. When questioned, the reporter said, &ldquo;Yes, I got that from those sources. It&rsquo;s background.&rdquo; Improbable as the explanation of innocent error was &mdash; the reporter had earned a university degree, worked at another daily newspaper, and had attended an in-house seminar on how to avoid plagiarism &mdash; the management accepted it and kept the reporter on staff. <o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">Now we have Chris** Anderson, an established editor and published writer, caught up in an embarrassment that he has described as an innocent error, for which he has apologized, and which he has pledged to correct. That is as it should be. <o:p></o:p><!--[if !supportEmptyParas]--><br />
<!--[endif]--><o:p></o:p></p>
<p class="MsoNormal">But he, and his publisher, should have known better. As should you.</p>
<p class="MsoNormal"><strong>* ** Correction July14: </strong>Chris Anderson was incorrectly referred to as &quot;Curt Anderson&quot; in the penultimate paragraph of this article. Thanks to Waldo for <a href="http://www.regrettheerror.com/books/you-dont-say-a-primer-on-plagiarism#comment-12636215">spotting this mistake</a>. <em>Update July 14:</em> A commenter <a href="http://www.regrettheerror.com/books/you-dont-say-a-primer-on-plagiarism#comment-12645175">correctly pointed out</a> that Waldo noted two occurrences of &quot;Curt&quot; in this post. Both have now been corrected.</p>
<p class="MsoNormal"><em>John McIntyre, former head of the copy desk at The Baltimore Sun, is the author of <a onclick="javascript:pageTracker._trackPageview('/outbound/article/johnemcintyre.blogspot.com');" href="http://johnemcintyre.blogspot.com/">You Don&rsquo;t Say</a>, a blog on language, usage and miscellaneous topics.</em></p>
<p class="MsoNormal"><o:p></o:p></p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2009/07/14/you-dont-say-a-primer-on-plagiarism/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>You Donâ€™t Say: Fixing the blame</title>
		<link>http://www.regrettheerror.com/2009/07/02/you-don%e2%80%99t-say-fixing-the-blame/</link>
		<comments>http://www.regrettheerror.com/2009/07/02/you-don%e2%80%99t-say-fixing-the-blame/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 12:00:37 +0000</pubDate>
		<dc:creator>jmcintyre</dc:creator>
				<category><![CDATA[You Don't Say]]></category>
		<category><![CDATA[correction policy]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=8458</guid>
		<description><![CDATA[By John E. McIntyre&#160; A reader of my column on how publications deal with corrections (&#8220;Daddy, where do corrections come from?&#34;) addressed a point that regularly bedevils editors: Should corrections identify who made the error? The issue has been described at some length in the article &#8220;Who takes the fall for errors?&#8221; by Kathy English, [...]]]></description>
			<content:encoded><![CDATA[<p>By John E. McIntyre&nbsp; </p>
<p>A reader of my column on how publications deal with corrections (<a href="http://www.regrettheerror.com/you-dont-say/you-dont-say-daddy-where-do-corrections-come-from">&ldquo;Daddy, where do corrections come from?&quot;</a>) addressed a point that regularly bedevils editors: Should corrections identify who made the error?</p>
<p>The issue has been described at some length in the article <a href="http://www.thestar.com/comment/article/653284">&ldquo;Who takes the fall for errors?&rdquo;</a> by Kathy English, the public editor of the Toronto Star. Let me summarize the two main perspectives on the issue.</p>
<p><strong>Point A:</strong> The impersonal correction, favored by many publications, considers a published article to be a collaborative effort for which the publication takes full responsibility without fixing blame. A given article may go through many hands, and error can occur at any point. It is the publication&rsquo;s fault if such errors are not identified and corrected.</p>
<p><strong>Point B:</strong> The contrary view, which received support in comments on Ms. English&rsquo;s article, is that because the reporter&rsquo;s byline is on the story, the reporter should not be embarrassed by being made to appear responsible for an error committed by someone else.</p>
<p>I am a sturdy advocate of the impersonal correction, which I justify for the following reasons.</p>
<p><strong>Item: </strong>The story is the publication&rsquo;s, not the author&rsquo;s. Put it this way. Should the subject of an article sue for libel, the writer expects the publication to assume responsibility for the defense. No reporter wants to hear an editor say, &ldquo;I see <em>you</em> have a problem with <em>your</em> story. You had better get <em>yourself</em> a lawyer.&rdquo;</p>
<p><strong>Item: </strong>The story is in fact a collective product of the publication&rsquo;s staff. Publications employ originating editors and copy editors, all of whom have the authority and responsibility to make necessary changes.</p>
<p><strong>Item:</strong> Bylines are more important to reporters than to readers. (That is why an eight-line brief rewritten from a press release will appear in print with a reporter&rsquo;s credit at the end.) A reader may register the name of a columnist, or a reporter whose beat impinges on that reader&rsquo;s particular interests, but there is little reason to think that readers take regular notice of who wrote which story.</p>
<p>There is thus little or no reason to think that readers care who makes mistakes of fact or that readers would benefit from reading corrections that assign such responsibility. <em>An article in yesterday&rsquo;s edition of the Blat mistakenly located the battle of Antietam as having taken place near Hagerstown, Maryland, instead of Sharpsburg. The writer&rsquo;s text was correct, but the error was introduced by an intern on the copy desk. The Blat regrets the error.<br />
</em><br />
The reader cares whether the <em>publication</em> is reliable.</p>
<p><strong>Item:</strong> A typical comment on Ms. English&rsquo;s article:<em> The problem in this case is that the reporter has his or her name clearly listed as writer. If THAT writer was NOT responsible, THAT fact should be noted. The reading public will always associate the article with the writer, no matter how many people are working in the background. It is only fair to exonerate the writer from blame in these cases.</em></p>
<p>Let&rsquo;s turn this one around. Should a reporter enjoy a reputation for accuracy that is the product of the editing process rather than the reporter&rsquo;s own work? I have seen text from reporters, passed along by originating editors, with errors that would make your hair stand on end. (I once saw a story sent to the copy desk in which the reporter had misspelled the name of its subject sixteen times; that all sixteen were consistently misspelled was thought to mark an improvement in the reporter&rsquo;s abilities.)</p>
<p>Anonymous copy editors, at the publications that still bother to engage copy editors, silently correct multitudes of errors. Envision this &ldquo;shirttail&rdquo; at the end of an article: <em>The writer of this article identified Ougadougou as the capital of Dahomey. It is the capital of Burkina Faso. A Blat copy editor corrected the error.</em></p>
<p>Fixing responsibility is useful in-house for evaluating the performance of writers and editors. Its utility for the reading public is questionable.</p>
<p><strong>Item: </strong>The exception: When a publication must acknowledge the commission of a plagiarism or a fabrication &mdash; the product of professional misconduct rather than ordinary carelessness or haste &mdash;&nbsp; the miscreant should be identified.</p>
<p><em>John McIntyre, former head of the copy desk at The Baltimore Sun, is the author of <a href="http://johnemcintyre.blogspot.com">You Don&rsquo;t Say</a>, a blog on language, usage and miscellaneous topics.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2009/07/02/you-don%e2%80%99t-say-fixing-the-blame/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>You Don&#8217;t Say: Daddy, where do corrections come from?</title>
		<link>http://www.regrettheerror.com/2009/06/18/you-dont-say-daddy-where-do-corrections-come-from/</link>
		<comments>http://www.regrettheerror.com/2009/06/18/you-dont-say-daddy-where-do-corrections-come-from/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 12:00:30 +0000</pubDate>
		<dc:creator>jmcintyre</dc:creator>
				<category><![CDATA[You Don't Say]]></category>
		<category><![CDATA[copy editing]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=8356</guid>
		<description><![CDATA[This post marks the debut of You Don&#8217;t Say, a new column by John McIntyre for Regret the Error. John, a newspaper copy editor for 30 years, oversaw The Baltimore Sun&#8217;s copy desk from 1995 to 2009. He has taught copy editing at Loyola of Maryland since 1995, and he has conducted workshops on writing [...]]]></description>
			<content:encoded><![CDATA[<p><em>This post marks the debut of You Don&#8217;t Say, a new column by John McIntyre for Regret the Error. John, a newspaper copy editor for 30 years, oversaw The Baltimore Sun&#8217;s copy desk from 1995 to 2009. He has taught copy editing at Loyola of Maryland since 1995, and he has conducted workshops on writing and editing at more than two dozen publications and professional organizations in the United States and Canada. On this site, John will bring a copy editor&#8217;s perspective to errors, accuracy and corrections. You can follow his blog on editing and related subjects, <a href="http://johnemcintyre.blogspot.com">You Don&#8217;t Say</a>.</em><em> He can also be found on <a href="http://www.facebook.com/jemcintyre">Facebook</a></em><em> and on Twitter as <a href="http://www.twitter.com/johnemcintyre">@johnemcintyre</a>.</em></p>
<p>By John E. McIntyre</p>
<p>Not everything that is wrong  merits public correction.</p>
<p>It would be extremely unusual,  for example, for a newspaper, magazine, or Web site to run a formal  correction for an error in grammar or English usage, or for a typographical  error, though there are exceptions, as when 24 Hours quoted a councilman  as saying that the costs of a tunnel were &ldquo;now being lowballed&rdquo;  instead of &ldquo;not being lowballed.&rdquo; Such lapses are dealt with, if  at all, in in-house newsletters or memos, of which Philip B. Corbett&rsquo;s  excellent <a href="http://topics.blogs.nytimes.com/tag/after-deadline/">After Deadline</a> at The New York Times website is an example. &nbsp;</p>
<p>Formal corrections, such as  those aggregated on this site, almost always focus on errors of fact:&nbsp;</p>
<p><b>The wrong name for a person  or organization</b> &mdash; The New York Times has admitted to getting  Procter and Gamble&rsquo;s name wrong as Proctor and Gamble more than 100  times. &nbsp;</p>
<p><b>Erroneous statistics</b>  &mdash; The Toronto Star published in May that 1,700 wind turbines  are in operation in Europe; the number is about 74,000. Also in May,  the paper estimated the cost or a new nuclear plant as $7,000 per megawatt  of installed capacity, but the correct number is $7,000 per kilowatt.  Distinguishing between mega and kilo, like the distinction  between million and billion, is a hazard for mathematically  impaired journalists.&nbsp;</p>
<p><b>Bungled photo captions</b>  &mdash; The Washington Times ran a photo of the Obama children to  illustrate an article about homicides of children in Chicago.</p>
<p><b>Recipes </b> &mdash; You might not want to attempt any published recipe until, say, five  days or a week past publication. The Hamilton Spectator ran a  recipe for a ginger cake during Celiac Awareness Month than called for  two cups of penne pasta instead of two cups of rice pasta.&nbsp; &nbsp;</p>
<p><b>Popular culture </b> &mdash; The Guardian&rsquo;s&nbsp; review of the latest Star Trek  movie referred to a character as a Klingon rather than a Romulan, and  the Los Angeles Times referred to the character as Captain Nemo  instead of Captain Nero.</p>
<p><b>Wrong word  &mdash; </b>The New York Times quoted Rep. Anthony D. Weiner as saying,  &ldquo;You&rsquo;ll forgive some of my constituents for wanting to get into  the fetal poison and bathe in Purell.&rdquo; He said &ldquo;fetal position.&rdquo; &nbsp;</p>
<p>And more, such as people who  are very much alive being reported as dead. &nbsp;</p>
<p>But not even every error of  fact winds up being corrected. When errors are identified, a responsible  editor or small group of editors will determine whether they are significant enough to merit formal notice. How many minor errors of fact pass unnoticed  is not easy to determine. But published corrections almost always follow  when a reader complains of an error.</p>
<p>Sometimes a publication decides  to run a clarification rather than a correction, in contexts in which  the published statement of fact was technically accurate but lacked  some nuance of wording or additional detail and therefore permitted  a misreading. &nbsp;</p>
<p>And in the free-for-all word  of electronic publishing, some Web sites do not commonly publish corrections  at all, instead updating the published articles with silent corrections  as the day wears on. Bloggers, or at least the responsible ones, will  authorize readers&rsquo; corrections through comments and will also apologize  for errors in comments or subsequent posts. But the practice on the  Web has not yet standardized. &nbsp;</p>
<p>One thing that the Internet  has beneficially fostered is the proliferation of apologies for plagiarisms  and fabrication. The ease of theft through copying and pasting electronic  texts is matched only by the ease of detection of such theft. And with  bloggers and other commentators quick to jump on any publication detected  in apparent jiggery-pokery &mdash; such as Maureen Dowd&rsquo;s recent appropriation  of a passage from Josh Marshall&rsquo;s Talking Points Memo &mdash; it becomes  difficult for a publication to deal quietly and privately with these  matters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2009/06/18/you-dont-say-daddy-where-do-corrections-come-from/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

