<?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>Comentários sobre: Context in GNOME translations</title>
	<atom:link href="http://leonardof.org/2007/12/01/context-in-gnome-translations/feed/" rel="self" type="application/rss+xml" />
	<link>http://leonardof.org/2007/12/01/context-in-gnome-translations/</link>
	<description>Tradutor do GNOME para o português do Brasil</description>
	<lastBuildDate>Tue, 24 Jan 2012 22:29:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Por: Leonardo Fontenelle &#124; msgctxt for GNOME 2.26?</title>
		<link>http://leonardof.org/2007/12/01/context-in-gnome-translations/#comment-2407</link>
		<dc:creator>Leonardo Fontenelle &#124; msgctxt for GNOME 2.26?</dc:creator>
		<pubDate>Tue, 19 Aug 2008 21:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://leonardof.org/2007/12/01/context-in-gnome-translations/en/#comment-2407</guid>
		<description>[...] 2007 I wrote about GNOME adopting gettext&#8217;s msgctxt feature (and so did Andre Klapper). 8 months latter, this still is considered a proposed GNOME Goal. I [...]</description>
		<content:encoded><![CDATA[<p>[...] 2007 I wrote about GNOME adopting gettext&#8217;s msgctxt feature (and so did Andre Klapper). 8 months latter, this still is considered a proposed GNOME Goal. I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Por: F Wolff</title>
		<link>http://leonardof.org/2007/12/01/context-in-gnome-translations/#comment-1564</link>
		<dc:creator>F Wolff</dc:creator>
		<pubDate>Tue, 04 Dec 2007 07:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://leonardof.org/2007/12/01/context-in-gnome-translations/en/#comment-1564</guid>
		<description>I&#039;m also very happy about this. I think the most important part of this is that automatic QA with pofilter (or similar tools) will now work better with these strings. Now the work begins to get rid of the existing things - I really hope that a clean upgrade path exists so that we don&#039;t end with lots of fuzzy / untranslated entries (in underresourced languages, many files only get attention once in a few years :-/ )  I think it will also be important to help developers understand the difference between comments and context. Unnecessary disambiguation with context will cause more translations (and small teams are already not coping!)  And context doesn&#039;t mean that comments are not needed :-)</description>
		<content:encoded><![CDATA[<p>I&#8217;m also very happy about this. I think the most important part of this is that automatic QA with pofilter (or similar tools) will now work better with these strings. Now the work begins to get rid of the existing things &#8211; I really hope that a clean upgrade path exists so that we don&#8217;t end with lots of fuzzy / untranslated entries (in underresourced languages, many files only get attention once in a few years <img src='http://leonardof.org/wp-content/plugins/tango-smilies/tango/face-uncertain.png' alt=':-/' class='wp-smiley' />  )  I think it will also be important to help developers understand the difference between comments and context. Unnecessary disambiguation with context will cause more translations (and small teams are already not coping!)  And context doesn&#8217;t mean that comments are not needed <img src='http://leonardof.org/wp-content/plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
