<?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: Google Creates Gadget That Allows Instant Website Translation</title>
	<atom:link href="http://www.gadgetreview.com/2009/10/google-creates-gadget-that-allows-instant-website-translation.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.gadgetreview.com/2009/10/google-creates-gadget-that-allows-instant-website-translation.html</link>
	<description>Your Source for Gadget News, Reviews and Deals</description>
	<lastBuildDate>Sun, 12 Feb 2012 08:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Jim Making Sense</title>
		<link>http://www.gadgetreview.com/2009/10/google-creates-gadget-that-allows-instant-website-translation.html/comment-page-1#comment-853171</link>
		<dc:creator>Jim Making Sense</dc:creator>
		<pubDate>Fri, 02 Oct 2009 11:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.gadgetreview.com/?p=37268#comment-853171</guid>
		<description>Adding this semi-automatic translation is an interesting feature, but how does the translation actually read to a speaker of that language?
Presumably the translation is handled by the same engine as Google Translate. I recently blogged about this kind of &lt;a href=&quot;http://www.worldaccent.com/blog/2009/09/war-of-worlds-machine-translation.html&quot; rel=&quot;nofollow&quot;&gt;machine translation at &quot;Making Sense&quot; (worldaccent.com/blog)&lt;/a&gt; and, more importantly, its dangers. It can be great for getting the gist of something, but is also often way off beam. Google state this quite openly, but it&#039;s worth thinking over.
If a user runs your website through Google translate, they know its at their own risk. If you have &quot;provided&quot; a translation, aren&#039;t you more responsible for what it says? As Bing Translator warns you every time you use it: &quot;Automatic translation can help you understand the gist of the translated text but is no substitute for a professional human translator.&quot;
And, unless you speak the target language, how do you know if your website is being rendered in perfect prose or as unintelligible gibberish? If you care about what &quot;you&quot; are saying in translation, you&#039;re still best off sticking to a human translator.</description>
		<content:encoded><![CDATA[<p>Adding this semi-automatic translation is an interesting feature, but how does the translation actually read to a speaker of that language? </p>
<p>Presumably the translation is handled by the same engine as Google Translate. I recently blogged about this kind of <a href="http://www.worldaccent.com/blog/2009/09/war-of-worlds-machine-translation.html" rel="nofollow">machine translation at &#8220;Making Sense&#8221; (worldaccent.com/blog)</a> and, more importantly, its dangers. It can be great for getting the gist of something, but is also often way off beam. Google state this quite openly, but it&#8217;s worth thinking over.</p>
<p>If a user runs your website through Google translate, they know its at their own risk. If you have &#8220;provided&#8221; a translation, aren&#8217;t you more responsible for what it says? As Bing Translator warns you every time you use it: &#8220;Automatic translation can help you understand the gist of the translated text but is no substitute for a professional human translator.&#8221;</p>
<p>And, unless you speak the target language, how do you know if your website is being rendered in perfect prose or as unintelligible gibberish? If you care about what &#8220;you&#8221; are saying in translation, you&#8217;re still best off sticking to a human translator.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

