<?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: Language barriers and bugs</title>
	<atom:link href="http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/</link>
	<description>Jesse Ruderman on Firefox, security, and more</description>
	<lastBuildDate>Fri, 09 Sep 2011 05:56:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Gen Kanai</title>
		<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/comment-page-1/#comment-5570</link>
		<dc:creator>Gen Kanai</dc:creator>
		<pubDate>Tue, 21 Jul 2009 06:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=491#comment-5570</guid>
		<description>The Mozilla community in Japan handles it like this: 

There&#039;s a Japanese language bugzilla http://bugzilla.mozilla.gr.jp/ where Japanese Mozilla users file bugs in Japanese.  Other Japanese users test/confirm the bugs, and Masayuki Nakano (who works on i18n issues primarily) takes the confirmed bugs and moves them over to the main English-language Bugzilla.  It works pretty well, but perhaps the negatives would be that it takes time for a bug found in the Japanese community to get filed in the US Bugzilla, and perhaps that this particular process needs to have someone pretty fluent in the codebase (in this case, Masayuki) who can answer questions up front and determine which bugs are relevant to be filed in the English Bugzilla.</description>
		<content:encoded><![CDATA[<p>The Mozilla community in Japan handles it like this: </p>
<p>There&#8217;s a Japanese language bugzilla <a href="http://bugzilla.mozilla.gr.jp/" rel="nofollow">http://bugzilla.mozilla.gr.jp/</a> where Japanese Mozilla users file bugs in Japanese.  Other Japanese users test/confirm the bugs, and Masayuki Nakano (who works on i18n issues primarily) takes the confirmed bugs and moves them over to the main English-language Bugzilla.  It works pretty well, but perhaps the negatives would be that it takes time for a bug found in the Japanese community to get filed in the US Bugzilla, and perhaps that this particular process needs to have someone pretty fluent in the codebase (in this case, Masayuki) who can answer questions up front and determine which bugs are relevant to be filed in the English Bugzilla.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/comment-page-1/#comment-5569</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Tue, 21 Jul 2009 06:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=491#comment-5569</guid>
		<description>The truth is that for a bug to be noticed, it is not enough to just file it.  When one does that, no one notices it, or pays any attention.  Especially if the bug is not written in very good English or is about a feature that is not easy to test for English speakers (e.g. Arabic writing).</description>
		<content:encoded><![CDATA[<p>The truth is that for a bug to be noticed, it is not enough to just file it.  When one does that, no one notices it, or pays any attention.  Especially if the bug is not written in very good English or is about a feature that is not easy to test for English speakers (e.g. Arabic writing).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Mozilla finds crash bugs at Mozilla Security Blog</title>
		<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/comment-page-1/#comment-5568</link>
		<dc:creator>How Mozilla finds crash bugs at Mozilla Security Blog</dc:creator>
		<pubDate>Tue, 21 Jul 2009 01:53:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=491#comment-5568</guid>
		<description>[...] bugs requires substantial effort from users, and requires both English-language and technical skills, so we prefer not to rely exclusively on user-reported bugs. Luckily, crashes [...]</description>
		<content:encoded><![CDATA[<p>[...] bugs requires substantial effort from users, and requires both English-language and technical skills, so we prefer not to rely exclusively on user-reported bugs. Luckily, crashes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Axel Hecht</title>
		<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/comment-page-1/#comment-5566</link>
		<dc:creator>Axel Hecht</dc:creator>
		<pubDate>Sun, 19 Jul 2009 20:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=491#comment-5566</guid>
		<description>I&#039;m hoping that some intl bugs get earlier discovery when we have localized builds on a nightly update channel. That&#039;ll make it more interesting for local geeks to follow our development more closely and might make it more obvious to them to file a bug &#039;cause it&#039;s less of a &quot;someone else probably caught that one already&quot;.

Regarding getting bugs on file, the machine-translation piece might help us at least for some languages. Making filing bugs more obvious might be good enough, and to encourage users to file bugs in their language. To make them useful for our developers, cloning the bug with a MT of the original report might be a good start.

I&#039;m not sure if we need a localized UI for that, too. I usually think that when people claim they need to get the UI translated to be able to do ABC, the UI is likely too complex for people of that technical skill in English, too. So we might get more bang for the buck making that process more user friendly than trying to get a cumbersome process in many languages.</description>
		<content:encoded><![CDATA[<p>I&#8217;m hoping that some intl bugs get earlier discovery when we have localized builds on a nightly update channel. That&#8217;ll make it more interesting for local geeks to follow our development more closely and might make it more obvious to them to file a bug &#8217;cause it&#8217;s less of a &#8220;someone else probably caught that one already&#8221;.</p>
<p>Regarding getting bugs on file, the machine-translation piece might help us at least for some languages. Making filing bugs more obvious might be good enough, and to encourage users to file bugs in their language. To make them useful for our developers, cloning the bug with a MT of the original report might be a good start.</p>
<p>I&#8217;m not sure if we need a localized UI for that, too. I usually think that when people claim they need to get the UI translated to be able to do ABC, the UI is likely too complex for people of that technical skill in English, too. So we might get more bang for the buck making that process more user friendly than trying to get a cumbersome process in many languages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/comment-page-1/#comment-5563</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sat, 18 Jul 2009 23:45:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=491#comment-5563</guid>
		<description>The Windows 7 team recently published a blog post about this: See the section titled “Understanding feedback from around the world” on http://blogs.msdn.com/e7/archive/2009/07/07/engineering-windows-7-for-a-global-market.aspx. In short, bugs can be submitted in any language, and machine translation is used to get a sense of the bug reports for triage.</description>
		<content:encoded><![CDATA[<p>The Windows 7 team recently published a blog post about this: See the section titled “Understanding feedback from around the world” on <a href="http://blogs.msdn.com/e7/archive/2009/07/07/engineering-windows-7-for-a-global-market.aspx" rel="nofollow">http://blogs.msdn.com/e7/archive/2009/07/07/engineering-windows-7-for-a-global-market.aspx</a>. In short, bugs can be submitted in any language, and machine translation is used to get a sense of the bug reports for triage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D.J. Capelis</title>
		<link>http://www.squarefree.com/2009/07/18/language-barriers-and-bugs/comment-page-1/#comment-5562</link>
		<dc:creator>D.J. Capelis</dc:creator>
		<pubDate>Sat, 18 Jul 2009 18:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=491#comment-5562</guid>
		<description>(Sorry by the way, for the mangled grammar and terribly composed sentences in the last comment.  I just got up.)</description>
		<content:encoded><![CDATA[<p>(Sorry by the way, for the mangled grammar and terribly composed sentences in the last comment.  I just got up.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

