<?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: Localization: What are we missing?</title>
	<atom:link href="http://thottingal.in/blog/2009/03/25/localization-what-are-we-missing/feed/" rel="self" type="application/rss+xml" />
	<link>http://thottingal.in/blog/2009/03/25/localization-what-are-we-missing/</link>
	<description>/home/santhosh</description>
	<lastBuildDate>Wed, 08 Sep 2010 03:08:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: alok</title>
		<link>http://thottingal.in/blog/2009/03/25/localization-what-are-we-missing/comment-page-1/#comment-131</link>
		<dc:creator>alok</dc:creator>
		<pubDate>Thu, 26 Mar 2009 21:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://thottingal.in/blog/?p=63#comment-131</guid>
		<description>&lt;p&gt;the answer lies with the user&lt;/p&gt;
&lt;p&gt;Creating (very broad) guidelines for translations and making it easy for people(users) to submit bug reports will help a lot and it will even make the sometimes mechanical translation work so much more interesting too.&lt;/p&gt;
&lt;p&gt;The real issue as you pointed out, is: are we doing l10n for the sake of seeing the %ages go up in the graphs for our $LANGs or because we want to create something useful for the person who doesn&#039;t know English but knows $LANG? &lt;/p&gt;
&lt;p&gt;If we keep in mind this fact while translating, things would change.&lt;br /&gt;
Lastly hats off to all the volunteers for all $LANGs.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>the answer lies with the user</p>
<p>Creating (very broad) guidelines for translations and making it easy for people(users) to submit bug reports will help a lot and it will even make the sometimes mechanical translation work so much more interesting too.</p>
<p>The real issue as you pointed out, is: are we doing l10n for the sake of seeing the %ages go up in the graphs for our $LANGs or because we want to create something useful for the person who doesn&#8217;t know English but knows $LANG? </p>
<p>If we keep in mind this fact while translating, things would change.<br />
Lastly hats off to all the volunteers for all $LANGs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://thottingal.in/blog/2009/03/25/localization-what-are-we-missing/comment-page-1/#comment-130</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 26 Mar 2009 16:41:19 +0000</pubDate>
		<guid isPermaLink="false">http://thottingal.in/blog/?p=63#comment-130</guid>
		<description>&lt;p&gt;Localization is a pretty big effort and as Santhosh points out, it is time for looking into the quality of translation. When SMC started localization efforts, we worked with the idea of context sensitive translation. We even keep a guideline for translations and glossory of terms. But this is not enough for completing the cycle. Peer review is one good method and it takes up a lot time than normal translation. Before we used to have sprints for translations, i think we should have sprints(online/offline) for review of translation.&lt;/p&gt;
&lt;p&gt;About the keyboard shortcuts/accelerator keys, i believe its a necessity. We may have to do some innovations(one idea is keeping the same keys, and if it triggers an acceleration, irrespective of the locale set on keyboard or tranlit interface, point it to accelerator). I know its not easy and right solution. This just came to my mind. I should say, i don&#039;t know the control flow in the programs, but we should be able to find some way around.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Localization is a pretty big effort and as Santhosh points out, it is time for looking into the quality of translation. When SMC started localization efforts, we worked with the idea of context sensitive translation. We even keep a guideline for translations and glossory of terms. But this is not enough for completing the cycle. Peer review is one good method and it takes up a lot time than normal translation. Before we used to have sprints for translations, i think we should have sprints(online/offline) for review of translation.</p>
<p>About the keyboard shortcuts/accelerator keys, i believe its a necessity. We may have to do some innovations(one idea is keeping the same keys, and if it triggers an acceleration, irrespective of the locale set on keyboard or tranlit interface, point it to accelerator). I know its not easy and right solution. This just came to my mind. I should say, i don&#8217;t know the control flow in the programs, but we should be able to find some way around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://thottingal.in/blog/2009/03/25/localization-what-are-we-missing/comment-page-1/#comment-129</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 26 Mar 2009 13:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://thottingal.in/blog/?p=63#comment-129</guid>
		<description>&lt;p&gt;Localization issues&lt;/p&gt;
&lt;p&gt;Having a *real* community (not just 1 or 2 person) of localizers (most importantly translators) should have resolved all of the above issues for Indic Localization.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Localization issues</p>
<p>Having a *real* community (not just 1 or 2 person) of localizers (most importantly translators) should have resolved all of the above issues for Indic Localization.</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! -->