<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: consistency of translations</title>
	<atom:link href="http://blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/</link>
	<description>i&#039;m not dead yet, but i&#039;m working on it.</description>
	<lastBuildDate>Mon, 23 Jan 2012 11:17:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Djihed Afifi</title>
		<link>http://blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/comment-page-1/#comment-138</link>
		<dc:creator>Djihed Afifi</dc:creator>
		<pubDate>Tue, 01 Jan 2008 00:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/#comment-138</guid>
		<description>[shameless plug]
A while back I wrote this post:

http://djihed.com/arabisation/statistical-analysis-of-strings-in-popular-open-source-projects

I used a script to cook up the most popular strings to try and consistently translate them. This is a big issue for Arabic because nearly none of the computing related terms are settled yet.

It helped us immensely in prioritising and identifying strings where conflicts are even less tolerated.</description>
		<content:encoded><![CDATA[<p>[shameless plug]<br />
A while back I wrote this post:</p>
<p><a href="http://djihed.com/arabisation/statistical-analysis-of-strings-in-popular-open-source-projects" rel="nofollow">http://djihed.com/arabisation/statistical-analysis-of-strings-in-popular-open-source-projects</a></p>
<p>I used a script to cook up the most popular strings to try and consistently translate them. This is a big issue for Arabic because nearly none of the computing related terms are settled yet.</p>
<p>It helped us immensely in prioritising and identifying strings where conflicts are even less tolerated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: F Wolff</title>
		<link>http://blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/comment-page-1/#comment-133</link>
		<dc:creator>F Wolff</dc:creator>
		<pubDate>Thu, 20 Dec 2007 07:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/#comment-133</guid>
		<description>As you know I reported a bug or two today against packages that could use the gtk+ stock texts but don&#039;t. This might already provide some improvement (by making it impossible to have it inconsistent). We have written poconflicts in the translate toolkit for this purpose of checking  for certain types of inconsistencies. I thought you might be interested: http://translate.sourceforge.net/wiki/toolkit/poconflict</description>
		<content:encoded><![CDATA[<p>As you know I reported a bug or two today against packages that could use the gtk+ stock texts but don&#8217;t. This might already provide some improvement (by making it impossible to have it inconsistent). We have written poconflicts in the translate toolkit for this purpose of checking  for certain types of inconsistencies. I thought you might be interested: <a href="http://translate.sourceforge.net/wiki/toolkit/poconflict" rel="nofollow">http://translate.sourceforge.net/wiki/toolkit/poconflict</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/aklapper/2007/12/08/consistency-of-translations/feed/ ) in 0.14252 seconds, on Feb 11th, 2012 at 4:08 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 5:08 am UTC -->
