<?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 for ankit644.comankit644.com</title>
	<atom:link href="http://www.ankit644.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.ankit644.com</link>
	<description>Ankit blogs...</description>
	<lastBuildDate>Thu, 28 Mar 2013 10:07:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Contextualization for Software Localization by Ankit Patel</title>
		<link>http://www.ankit644.com/?p=296&#038;cpage=1#comment-400</link>
		<dc:creator>Ankit Patel</dc:creator>
		<pubDate>Thu, 28 Mar 2013 10:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ankit644.com/?p=296#comment-400</guid>
		<description><![CDATA[* You are right in a way that it should be in one of the check-list for software developers, but we don&#039;t have any guidelines for this in most of the open source projects we work.
* also with respect to considering screenshots for better localization, we got introduced to the screenshot comparison method by fuelproject here: http://www.fuelproject.org/translationquality/index

/Ankit]]></description>
		<content:encoded><![CDATA[<p>* You are right in a way that it should be in one of the check-list for software developers, but we don&#8217;t have any guidelines for this in most of the open source projects we work.<br />
* also with respect to considering screenshots for better localization, we got introduced to the screenshot comparison method by fuelproject here: <a href="http://www.fuelproject.org/translationquality/index" rel="nofollow">http://www.fuelproject.org/translationquality/index</a></p>
<p>/Ankit</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Contextualization for Software Localization by Sebastian</title>
		<link>http://www.ankit644.com/?p=296&#038;cpage=1#comment-398</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Mon, 25 Mar 2013 17:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.ankit644.com/?p=296#comment-398</guid>
		<description><![CDATA[Context is everything, especially in terms of quality. It&#039;s important to keep this on the agenda for software developers. All too often, missing context will unnecessarily increase overhead because back-and-forth messaging between product management and translator is required to clear misunderstandings.
We&#039;ve been putting a lot of work into this based on our experience as well, at http://lingohub.com and we&#039;ve been trying to tackle it from some similar angles you did: we allow extensive commenting, and also screenshot uploads. These can actually also be supplied already from within the files, or via an API, to make the experience even smoother. I am not sure if you&#039;ve thought of it, but what also can be put into source files is meta information such as character length etc. Love to hear more of your thoughts on this. Cheers]]></description>
		<content:encoded><![CDATA[<p>Context is everything, especially in terms of quality. It&#8217;s important to keep this on the agenda for software developers. All too often, missing context will unnecessarily increase overhead because back-and-forth messaging between product management and translator is required to clear misunderstandings.<br />
We&#8217;ve been putting a lot of work into this based on our experience as well, at <a href="http://lingohub.com" rel="nofollow">http://lingohub.com</a> and we&#8217;ve been trying to tackle it from some similar angles you did: we allow extensive commenting, and also screenshot uploads. These can actually also be supplied already from within the files, or via an API, to make the experience even smoother. I am not sure if you&#8217;ve thought of it, but what also can be put into source files is meta information such as character length etc. Love to hear more of your thoughts on this. Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gujarati locale and standards&#8230; by Dr.Kishorbhai Mohanbhai Patel</title>
		<link>http://www.ankit644.com/?p=32&#038;cpage=1#comment-103</link>
		<dc:creator>Dr.Kishorbhai Mohanbhai Patel</dc:creator>
		<pubDate>Tue, 23 Aug 2011 06:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.ankit644.com/?p=32#comment-103</guid>
		<description><![CDATA[Dear Ankitbhai 

very very nice blog 

but YR Word...............! 

Dr. K.M.Patel]]></description>
		<content:encoded><![CDATA[<p>Dear Ankitbhai </p>
<p>very very nice blog </p>
<p>but YR Word&#8230;&#8230;&#8230;&#8230;&#8230;! </p>
<p>Dr. K.M.Patel</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby on Rails Application Deployment with Passenger on Fedora by Ankit Patel</title>
		<link>http://www.ankit644.com/?p=241&#038;cpage=1#comment-99</link>
		<dc:creator>Ankit Patel</dc:creator>
		<pubDate>Tue, 14 Jun 2011 11:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.ankit644.com/?p=241#comment-99</guid>
		<description><![CDATA[because webrick is not suitable because of it&#039;s stability for production purpose.]]></description>
		<content:encoded><![CDATA[<p>because webrick is not suitable because of it&#8217;s stability for production purpose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby on Rails Application Deployment with Passenger on Fedora by Sandeep</title>
		<link>http://www.ankit644.com/?p=241&#038;cpage=1#comment-98</link>
		<dc:creator>Sandeep</dc:creator>
		<pubDate>Tue, 14 Jun 2011 11:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ankit644.com/?p=241#comment-98</guid>
		<description><![CDATA[why passenger instead of WEBrick ?]]></description>
		<content:encoded><![CDATA[<p>why passenger instead of WEBrick ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
