<?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"
	>
<channel>
	<title>Comments on: Internationalize PHP Applications</title>
	<atom:link href="http://code.mikwat.com/archives/16/feed" rel="self" type="application/rss+xml" />
	<link>http://code.mikwat.com/archives/16</link>
	<description>A coder's daily explorations through PHP, Java, CSS, JavaScript, Linux, OS X, Apache, Tomcat, and everything else.</description>
	<pubDate>Wed, 07 Jan 2009 12:17:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Jesse Englert</title>
		<link>http://code.mikwat.com/archives/16#comment-3</link>
		<dc:creator>Jesse Englert</dc:creator>
		<pubDate>Thu, 03 May 2007 01:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://code.mikwat.com/archives/16#comment-3</guid>
		<description>Building localization into your apps is good even if you only plan on supporting one language now.  It forces you to centralize all your strings and you never know what your app with require in the future.</description>
		<content:encoded><![CDATA[<p>Building localization into your apps is good even if you only plan on supporting one language now.  It forces you to centralize all your strings and you never know what your app with require in the future.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
