<?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: Back Translation: Out of Date in the Advanced Localization Community?</title>
	<atom:link href="http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/</link>
	<description>global-scale localization.  thought leadership, news and information</description>
	<lastBuildDate>Thu, 17 Sep 2009 22:56:32 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Radek Pletka</title>
		<link>http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/comment-page-1/#comment-85</link>
		<dc:creator>Radek Pletka</dc:creator>
		<pubDate>Thu, 06 Aug 2009 16:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.translatemyworld.com/LocalizationBestPractices/?p=262#comment-85</guid>
		<description>Back translation is usually needed only because the customer didn&#039;t spend enough money to get it translated right at the first place. Buying translation is like a buying a car - you usually get what you paid for. When you pay for for beaten up Ford Escort and expect to have a ride like in a new Mercedes, you usually have a problem. And paying for another crappy Ford Escort to take you back will not fix it (smile).
I love cheap translators. Those guys are working hard every day to educate customers that you get what you pay for.
And I need educated customers, who learned the hard way that if you need quality, you HAVE TO PAY FOR IT.
If you need good translation, you need to find good translators, pay them well and than you can be assured you get a good product. It is not so difficult to find good translators, those are the ones, who are not cheap and who are also always busy (smile).
Offer them a little bit more and I am sure they will be able to squeeze you in (at least this is the way how I do it)

Sincerely

Radek Pletka</description>
		<content:encoded><![CDATA[<p>Back translation is usually needed only because the customer didn&#8217;t spend enough money to get it translated right at the first place. Buying translation is like a buying a car &#8211; you usually get what you paid for. When you pay for for beaten up Ford Escort and expect to have a ride like in a new Mercedes, you usually have a problem. And paying for another crappy Ford Escort to take you back will not fix it (smile).<br />
I love cheap translators. Those guys are working hard every day to educate customers that you get what you pay for.<br />
And I need educated customers, who learned the hard way that if you need quality, you HAVE TO PAY FOR IT.<br />
If you need good translation, you need to find good translators, pay them well and than you can be assured you get a good product. It is not so difficult to find good translators, those are the ones, who are not cheap and who are also always busy (smile).<br />
Offer them a little bit more and I am sure they will be able to squeeze you in (at least this is the way how I do it)</p>
<p>Sincerely</p>
<p>Radek Pletka</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Roland</title>
		<link>http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/comment-page-1/#comment-84</link>
		<dc:creator>Tom Roland</dc:creator>
		<pubDate>Wed, 05 Aug 2009 18:58:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.translatemyworld.com/LocalizationBestPractices/?p=262#comment-84</guid>
		<description>Thanks for this post. Very interesting. But I don&#039;t think you fully answered your question, “Is there a more efficient way of managing these risks than have back translation performed?” Yes, the approach you recommend is a good one and will go a long way toward achieving better translation quality. But if the consequences of one incorrect translation are high enough (as is sometimes the case with pharmaceuticals, to cite your example), then the stakes may be high enough to warrant back translation of at least some materials, as a component of the &quot;full localization strategy.&quot;

PS: As a translator and therefore nit-picker of words, I must point out that you meant to write &quot;there&quot; instead of &quot;their&quot; in your second heading. 
Cheers, 
Tom</description>
		<content:encoded><![CDATA[<p>Thanks for this post. Very interesting. But I don&#8217;t think you fully answered your question, “Is there a more efficient way of managing these risks than have back translation performed?” Yes, the approach you recommend is a good one and will go a long way toward achieving better translation quality. But if the consequences of one incorrect translation are high enough (as is sometimes the case with pharmaceuticals, to cite your example), then the stakes may be high enough to warrant back translation of at least some materials, as a component of the &#8220;full localization strategy.&#8221;</p>
<p>PS: As a translator and therefore nit-picker of words, I must point out that you meant to write &#8220;there&#8221; instead of &#8220;their&#8221; in your second heading.<br />
Cheers,<br />
Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lost in Translation</title>
		<link>http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/comment-page-1/#comment-78</link>
		<dc:creator>Lost in Translation</dc:creator>
		<pubDate>Thu, 30 Jul 2009 09:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.translatemyworld.com/LocalizationBestPractices/?p=262#comment-78</guid>
		<description>Back translation is a ******** (editor deleted expletive) money-making racket by vendors (usually in the medical space). Why not just export the source and target segments and send it to the reviewer to QA?

Don&#039;t forget the (French) Toyota MR2 story....:)</description>
		<content:encoded><![CDATA[<p>Back translation is a ******** (editor deleted expletive) money-making racket by vendors (usually in the medical space). Why not just export the source and target segments and send it to the reviewer to QA?</p>
<p>Don&#8217;t forget the (French) Toyota MR2 story&#8230;.:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JLibbey</title>
		<link>http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/comment-page-1/#comment-75</link>
		<dc:creator>JLibbey</dc:creator>
		<pubDate>Wed, 29 Jul 2009 20:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.translatemyworld.com/LocalizationBestPractices/?p=262#comment-75</guid>
		<description>The anecdote about the Chevy Nova is incorrect.  Unfortunately, people keep spreading it around.

http://en.wikipedia.org/wiki/Chevrolet_Nova#Urban_legend
http://answers.yahoo.com/question/index?qid=1006033030982</description>
		<content:encoded><![CDATA[<p>The anecdote about the Chevy Nova is incorrect.  Unfortunately, people keep spreading it around.</p>
<p><a href="http://en.wikipedia.org/wiki/Chevrolet_Nova#Urban_legend" rel="nofollow">http://en.wikipedia.org/wiki/Chevrolet_Nova#Urban_legend</a><br />
<a href="http://answers.yahoo.com/question/index?qid=1006033030982" rel="nofollow">http://answers.yahoo.com/question/index?qid=1006033030982</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirti Vashee</title>
		<link>http://www.translatemyworld.com/LocalizationBestPractices/2009/07/back-translation-out-of-date-in-the-advanced-localization-community/comment-page-1/#comment-74</link>
		<dc:creator>Kirti Vashee</dc:creator>
		<pubDate>Wed, 29 Jul 2009 19:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.translatemyworld.com/LocalizationBestPractices/?p=262#comment-74</guid>
		<description>I think it would be much more useful to do multiple translations of the same source doc as this would reveal issues that exist in the source language that could contribute to worse translations.

This practice is particularly useless and pointless in evaluating MT  since you are guaranteed to get source that deteriorates every time it  is passed through the engine. It would provide no real idea or insight on the actual quality of the MT engine.

With MT this is almost an equivalent of making fun of a handicapped person</description>
		<content:encoded><![CDATA[<p>I think it would be much more useful to do multiple translations of the same source doc as this would reveal issues that exist in the source language that could contribute to worse translations.</p>
<p>This practice is particularly useless and pointless in evaluating MT  since you are guaranteed to get source that deteriorates every time it  is passed through the engine. It would provide no real idea or insight on the actual quality of the MT engine.</p>
<p>With MT this is almost an equivalent of making fun of a handicapped person</p>
]]></content:encoded>
	</item>
</channel>
</rss>
