<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Google’s Nexus One muzzles the foul-mouthed</title>
	<atom:link href="http://blogs.reuters.com/mediafile/2010/01/22/google%E2%80%99s-nexus-one-muzzles-the-foul-mouthed/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.reuters.com/mediafile/2010/01/22/google%e2%80%99s-nexus-one-muzzles-the-foul-mouthed/</link>
	<description>Where media and technology meet</description>
	<lastBuildDate>Thu, 23 May 2013 00:00:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: rk808</title>
		<link>http://blogs.reuters.com/mediafile/2010/01/22/google%e2%80%99s-nexus-one-muzzles-the-foul-mouthed/comment-page-1/#comment-372396</link>
		<dc:creator>rk808</dc:creator>
		<pubDate>Mon, 25 Jan 2010 19:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/mediafile/?p=20575#comment-372396</guid>
		<description>Sounds like the Stallone movie &quot;Demolition Man&quot; where Stallone is brought back to life in the future and any foul language will cost you credits.  Be Well!</description>
		<content:encoded><![CDATA[<p>Sounds like the Stallone movie &#8220;Demolition Man&#8221; where Stallone is brought back to life in the future and any foul language will cost you credits.  Be Well!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy-Chappell</title>
		<link>http://blogs.reuters.com/mediafile/2010/01/22/google%e2%80%99s-nexus-one-muzzles-the-foul-mouthed/comment-page-1/#comment-372382</link>
		<dc:creator>Jeremy-Chappell</dc:creator>
		<pubDate>Mon, 25 Jan 2010 13:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/mediafile/?p=20575#comment-372382</guid>
		<description>Err, I don&#039;t like to point of the #### obvious but, you&#039;re talking about technology that WILL make mistakes, now consider: You want to use the word &quot;duck&quot;, Google&#039;s speech recognition could get you into a LOT of trouble. The use of &quot;####&quot; makes a lot of sense, firstly no offensive word is sent, and secondly you&#039;ll see the error (the &#039;#&#039; character stands out in text) and have a chance to correct it. If you mean to swear then the &#039;#&#039;s are enough to indicate to most people that was your intention. Seems like the ONLY option they could have taken.

Now can you tell me you&#039;ve never either misspoken and used a swear word (often without even being aware of it) or misheard a word and thought it was profanity? Spoken language has this problem, technology or not. I don&#039;t see the restriction can ever be relaxed. Unless you want something like Microsoft&#039;s &quot;Clippy&quot; asking: &quot;It sounds like you swearing like a sailor, do you want any help with that?&quot; (I can only imagine the response, but that&#039;s a lot of hash-marks)</description>
		<content:encoded><![CDATA[<p>Err, I don&#8217;t like to point of the #### obvious but, you&#8217;re talking about technology that WILL make mistakes, now consider: You want to use the word &#8220;duck&#8221;, Google&#8217;s speech recognition could get you into a LOT of trouble. The use of &#8220;####&#8221; makes a lot of sense, firstly no offensive word is sent, and secondly you&#8217;ll see the error (the &#8216;#&#8217; character stands out in text) and have a chance to correct it. If you mean to swear then the &#8216;#&#8217;s are enough to indicate to most people that was your intention. Seems like the ONLY option they could have taken.</p>
<p>Now can you tell me you&#8217;ve never either misspoken and used a swear word (often without even being aware of it) or misheard a word and thought it was profanity? Spoken language has this problem, technology or not. I don&#8217;t see the restriction can ever be relaxed. Unless you want something like Microsoft&#8217;s &#8220;Clippy&#8221; asking: &#8220;It sounds like you swearing like a sailor, do you want any help with that?&#8221; (I can only imagine the response, but that&#8217;s a lot of hash-marks)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mathiastck</title>
		<link>http://blogs.reuters.com/mediafile/2010/01/22/google%e2%80%99s-nexus-one-muzzles-the-foul-mouthed/comment-page-1/#comment-372322</link>
		<dc:creator>mathiastck</dc:creator>
		<pubDate>Sun, 24 Jan 2010 20:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/mediafile/?p=20575#comment-372322</guid>
		<description>####!</description>
		<content:encoded><![CDATA[<p>####!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
