<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: International support, tooltips, and improved alerts/invites</title>
	<link>http://blog.competitio.us/2006/10/24/international-support-tooltips-and-improved-alertsinvites/</link>
	<description>Our company blog</description>
	<pubDate>Wed, 07 Jan 2009 14:10:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Nash</title>
		<link>http://blog.competitio.us/2006/10/24/international-support-tooltips-and-improved-alertsinvites/#comment-2295</link>
		<pubDate>Mon, 12 Mar 2007 11:03:38 +0000</pubDate>
		<guid>http://blog.competitio.us/2006/10/24/international-support-tooltips-and-improved-alertsinvites/#comment-2295</guid>
					<description>I just went through your presentation on Google Video and it was very insightful of RoR. 

I myself struggled with the decision of using RoR or django. At the end of the day, the main deciding factor became internationalization support and RoR just had no support for it so I've gone down the django road. But seeing this new feature, I'd like to know how hard was internationalization support for you guys? Last time I checked, alot of code didn't work right with UTF strings and other issues. I'd love to hear about your experience</description>
		<content:encoded><![CDATA[<p>I just went through your presentation on Google Video and it was very insightful of RoR. </p>
<p>I myself struggled with the decision of using RoR or django. At the end of the day, the main deciding factor became internationalization support and RoR just had no support for it so I&#8217;ve gone down the django road. But seeing this new feature, I&#8217;d like to know how hard was internationalization support for you guys? Last time I checked, alot of code didn&#8217;t work right with UTF strings and other issues. I&#8217;d love to hear about your experience
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
