<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>Comments on: How should MediaBugs handle reports about grammar, spelling, and writing?</title>
	<atom:link href="http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/</link>
	<description>Fix the news</description>
	<lastBuildDate>Tue, 23 Sep 2014 03:33:05 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: Lora Kolodny</title>
		<link>http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/comment-page-1/#comment-54</link>
		<dc:creator><![CDATA[Lora Kolodny]]></dc:creator>
		<pubDate>Sat, 15 May 2010 02:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediabugs.org/blog/?p=105#comment-54</guid>
		<description><![CDATA[Hear hear JB! A separate section or even site, maybe a partnership with another blog that&#039;s already strong on style and grammar (and hopefully, advancing literacy and language education) makes sense to me. Like Language Log? 

http://languagelog.ldc.upenn.edu/nll/]]></description>
		<content:encoded><![CDATA[<p>Hear hear JB! A separate section or even site, maybe a partnership with another blog that&#8217;s already strong on style and grammar (and hopefully, advancing literacy and language education) makes sense to me. Like Language Log? </p>
<p><a href="http://languagelog.ldc.upenn.edu/nll/" rel="nofollow">http://languagelog.ldc.upenn.edu/nll/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/comment-page-1/#comment-39</link>
		<dc:creator><![CDATA[JB]]></dc:creator>
		<pubDate>Thu, 29 Apr 2010 15:05:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediabugs.org/blog/?p=105#comment-39</guid>
		<description><![CDATA[I agree that Media Bugs is most useful as a clearing house for real factual errors. However, if people continue to report significant numbers of grammatical errors, I would consider finding a home for them on the site. Perhaps you could treat them in a more fun, lighthearted way, in a place distinct from the real error reports. You could try it and ditch it if it doesn&#039;t work out.

Not sure what kind of reporting numbers you&#039;re seeing early. But I imagine that grammatical errors are naturally easier for people to spot. They&#039;re sort of a low-hanging fruit for your error-reporting users. If you can find an appropriate way to manage grammatical errors on the site, maybe you&#039;ll better engage the early users that are reporting them. They&#039;ll become stronger advocates for the site.

Nobody uses a new service in exactly the ways its creators anticipate. Adapting to actual usage patterns rather than desired user patterns is often a key to success.]]></description>
		<content:encoded><![CDATA[<p>I agree that Media Bugs is most useful as a clearing house for real factual errors. However, if people continue to report significant numbers of grammatical errors, I would consider finding a home for them on the site. Perhaps you could treat them in a more fun, lighthearted way, in a place distinct from the real error reports. You could try it and ditch it if it doesn&#8217;t work out.</p>
<p>Not sure what kind of reporting numbers you&#8217;re seeing early. But I imagine that grammatical errors are naturally easier for people to spot. They&#8217;re sort of a low-hanging fruit for your error-reporting users. If you can find an appropriate way to manage grammatical errors on the site, maybe you&#8217;ll better engage the early users that are reporting them. They&#8217;ll become stronger advocates for the site.</p>
<p>Nobody uses a new service in exactly the ways its creators anticipate. Adapting to actual usage patterns rather than desired user patterns is often a key to success.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/comment-page-1/#comment-34</link>
		<dc:creator><![CDATA[Anon]]></dc:creator>
		<pubDate>Fri, 23 Apr 2010 18:21:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediabugs.org/blog/?p=105#comment-34</guid>
		<description><![CDATA[Please, factual errors only.  I mean, one of the bug reports takes issue with a single inelegant word choice in a college newspaper article, written by a freshman.  Who cares?]]></description>
		<content:encoded><![CDATA[<p>Please, factual errors only.  I mean, one of the bug reports takes issue with a single inelegant word choice in a college newspaper article, written by a freshman.  Who cares?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Silverman</title>
		<link>http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/comment-page-1/#comment-32</link>
		<dc:creator><![CDATA[Craig Silverman]]></dc:creator>
		<pubDate>Fri, 23 Apr 2010 00:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediabugs.org/blog/?p=105#comment-32</guid>
		<description><![CDATA[I agree with Lora. MediaBugs should focus on factual errors. Of course, typos or poor grammar can result in factual errors -- but a misplaced comma or inelegant sentence isn&#039;t the kind of thing this project should focus on, IMO.]]></description>
		<content:encoded><![CDATA[<p>I agree with Lora. MediaBugs should focus on factual errors. Of course, typos or poor grammar can result in factual errors &#8212; but a misplaced comma or inelegant sentence isn&#8217;t the kind of thing this project should focus on, IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lora Kolodny</title>
		<link>http://mediabugs.org/blog/2010/04/22/grammar-and-copyediting/comment-page-1/#comment-31</link>
		<dc:creator><![CDATA[Lora Kolodny]]></dc:creator>
		<pubDate>Fri, 23 Apr 2010 00:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediabugs.org/blog/?p=105#comment-31</guid>
		<description><![CDATA[As a journalist who started during the advent of online news, I would value MediaBugs more for dealing strictly with facts, not grammar and word choice. If there is an exceptional grammatical error in the news that leads to profound factual misunderstanding, that might be a worthwhile error to address, here. But at least, I&#039;d hope Media Bugs would create some sort of filter for correctable errors in the grammar category, and just ignore gripes about word choice that are a matter of opinion. Keep facts and discussion about them front and center, please. Let the grammarians go and occupy or gripe to sites meant to serve the purpose of advancing good style, syntax and the like. And let MediaBugs serve the purpose of advancing new journalism so that it can be thought of as good journalism itself, not just the stepchild of legacy, investigative and feature writers or producers who mattered.]]></description>
		<content:encoded><![CDATA[<p>As a journalist who started during the advent of online news, I would value MediaBugs more for dealing strictly with facts, not grammar and word choice. If there is an exceptional grammatical error in the news that leads to profound factual misunderstanding, that might be a worthwhile error to address, here. But at least, I&#8217;d hope Media Bugs would create some sort of filter for correctable errors in the grammar category, and just ignore gripes about word choice that are a matter of opinion. Keep facts and discussion about them front and center, please. Let the grammarians go and occupy or gripe to sites meant to serve the purpose of advancing good style, syntax and the like. And let MediaBugs serve the purpose of advancing new journalism so that it can be thought of as good journalism itself, not just the stepchild of legacy, investigative and feature writers or producers who mattered.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
