<?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: Should CLI debug output and error messages be localized in a GUI application?</title>
	<atom:link href="http://blog.peijnik.at/2009/06/02/should-cli-debug-output-and-error-messages-be-localized-in-a-gui-application/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.peijnik.at/2009/06/02/should-cli-debug-output-and-error-messages-be-localized-in-a-gui-application/</link>
	<description>Stephan's Free Software blog</description>
	<lastBuildDate>Fri, 25 Dec 2009 16:18:33 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: bcx</title>
		<link>http://blog.peijnik.at/2009/06/02/should-cli-debug-output-and-error-messages-be-localized-in-a-gui-application/comment-page-1/#comment-68</link>
		<dc:creator>bcx</dc:creator>
		<pubDate>Thu, 04 Jun 2009 13:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.peijnik.at/?p=137#comment-68</guid>
		<description>I think there are two different type of error messages. One you&#039;d display in a nice dialog to some imaginary user (I always image my mother is reading it) and then the user would know what to do. I&#039;d like those messages translated.

The second type of error message is when something is terribly wrong. The type that gives you lots of techy details to solve a difficult problem. The one you (or medium-techy users) would copy-paste to google and get the answer they need to solve a problem. They need to be in english because of two reasons: 

* They probably contain technical slang, something translators might confuse for actual words that can be translated. As such a translated error message can get very confusing. The english is probably more clear

* Google. You can search the entire web if the message has occurred somewhere else. Find bugreports. etc.</description>
		<content:encoded><![CDATA[<p>I think there are two different type of error messages. One you&#8217;d display in a nice dialog to some imaginary user (I always image my mother is reading it) and then the user would know what to do. I&#8217;d like those messages translated.</p>
<p>The second type of error message is when something is terribly wrong. The type that gives you lots of techy details to solve a difficult problem. The one you (or medium-techy users) would copy-paste to google and get the answer they need to solve a problem. They need to be in english because of two reasons: </p>
<p>* They probably contain technical slang, something translators might confuse for actual words that can be translated. As such a translated error message can get very confusing. The english is probably more clear</p>
<p>* Google. You can search the entire web if the message has occurred somewhere else. Find bugreports. etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
