<?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: Lessons learned from localization Part 3: Test and then test some more</title>
	<atom:link href="http://www.klocwork.com/blog/2012/10/lessons-learned-from-localization-part-3-test-and-then-test-some-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klocwork.com/blog/general-coding/lessons-learned-from-localization-part-3-test-and-then-test-some-more/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=lessons-learned-from-localization-part-3-test-and-then-test-some-more</link>
	<description>&#62;kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis.</description>
	<lastBuildDate>Tue, 30 Apr 2013 13:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: NRDtech London area Data Center services.</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-from-localization-part-3-test-and-then-test-some-more/comment-page-1/#comment-8881</link>
		<dc:creator>NRDtech London area Data Center services.</dc:creator>
		<pubDate>Thu, 01 Nov 2012 05:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1531#comment-8881</guid>
		<description>Wow, wonderful weblog layout! How long have you been blogging for? you make running a blog look easy. The overall glance of your web site is fantastic, as smartly as the content!</description>
		<content:encoded><![CDATA[<p>Wow, wonderful weblog layout! How long have you been blogging for? you make running a blog look easy. The overall glance of your web site is fantastic, as smartly as the content!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patti Murphy</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-from-localization-part-3-test-and-then-test-some-more/comment-page-1/#comment-8757</link>
		<dc:creator>Patti Murphy</dc:creator>
		<pubDate>Fri, 12 Oct 2012 20:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1531#comment-8757</guid>
		<description>Hi Curri,

As Jonathan pointed out, we don&#039;t rely on Google Translate to verify our translation. That&#039;s where #3 comes in -- We had native speakers AND product experts validate our translation and work with our localized product. 

Our test team uses Google Translate to get the gist of the general meaning of error messages when testing features in our localized product.

Relying entirely on Google Translate for localization would be foolhardy indeed.</description>
		<content:encoded><![CDATA[<p>Hi Curri,</p>
<p>As Jonathan pointed out, we don&#8217;t rely on Google Translate to verify our translation. That&#8217;s where #3 comes in &#8212; We had native speakers AND product experts validate our translation and work with our localized product. </p>
<p>Our test team uses Google Translate to get the gist of the general meaning of error messages when testing features in our localized product.</p>
<p>Relying entirely on Google Translate for localization would be foolhardy indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curri Barcelo</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-from-localization-part-3-test-and-then-test-some-more/comment-page-1/#comment-8755</link>
		<dc:creator>Curri Barcelo</dc:creator>
		<pubDate>Fri, 12 Oct 2012 19:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1531#comment-8755</guid>
		<description>&quot;4. Side-by-side monitors and Google Translate are your friends&quot; -&gt; How about using native speakers of the localised language? :) Maybe Google Translate will help you a bit if the product is localised into Spanish, but I doubt the translations you would get from Google Translate would be accurate if the language is Russian, or Farsi, or one of those for which Google hasn&#039;t had much time to work on.

Then you have those examples in which Google will tell you that the word used in your product is correct, but then a native person will read it and start laughing. For example, it is quite common to see in sites and some games the word &quot;espalda&quot; on a button used to go to the previous page or section or menu. This would be incorrect.. &quot;Espalda&quot; is the back, as in a part of the body. The correct word here would be &quot;Atrás&quot; or &quot;Anterior&quot;. So, how will you know that &quot;Espalda&quot; is the wrong word by using Google Translator? Try putting &quot;Back&quot; on GT and let&#039;s see what you get ;)

This is why is so important to always use native experienced testers for your localised products.</description>
		<content:encoded><![CDATA[<p>&#8220;4. Side-by-side monitors and Google Translate are your friends&#8221; -&gt; How about using native speakers of the localised language? :) Maybe Google Translate will help you a bit if the product is localised into Spanish, but I doubt the translations you would get from Google Translate would be accurate if the language is Russian, or Farsi, or one of those for which Google hasn&#8217;t had much time to work on.</p>
<p>Then you have those examples in which Google will tell you that the word used in your product is correct, but then a native person will read it and start laughing. For example, it is quite common to see in sites and some games the word &#8220;espalda&#8221; on a button used to go to the previous page or section or menu. This would be incorrect.. &#8220;Espalda&#8221; is the back, as in a part of the body. The correct word here would be &#8220;Atrás&#8221; or &#8220;Anterior&#8221;. So, how will you know that &#8220;Espalda&#8221; is the wrong word by using Google Translator? Try putting &#8220;Back&#8221; on GT and let&#8217;s see what you get ;)</p>
<p>This is why is so important to always use native experienced testers for your localised products.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
