<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>J. O&#039;Conner &#187; JavaScript</title>
	<atom:link href="http://joconner.com/category/javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://joconner.com</link>
	<description>Creating global software</description>
	<lastBuildDate>Thu, 01 Jul 2010 22:05:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Encoding URIs and their components</title>
		<link>http://joconner.com/2008/09/encoding-uris-and-their-components/</link>
		<comments>http://joconner.com/2008/09/encoding-uris-and-their-components/#comments</comments>
		<pubDate>Sat, 13 Sep 2008 06:48:38 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://joconner.com/?p=89</guid>
		<description><![CDATA[As you pass data from the browser to the application server to the database, opportunities for data loss lurk. I highlighted some of those conversion points earlier, but I neglected a browser issue. The JavaScript layer has its own lossy points of interest. One of those points is the escape function. The escape function &#8220;encodes&#8221; [...]]]></description>
		<wfw:commentRss>http://joconner.com/2008/09/encoding-uris-and-their-components/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JavaScript file encoding</title>
		<link>http://joconner.com/2008/09/javascript-file-encoding/</link>
		<comments>http://joconner.com/2008/09/javascript-file-encoding/#comments</comments>
		<pubDate>Sun, 07 Sep 2008 18:41:39 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://joconner.com/?p=19</guid>
		<description><![CDATA[Although JavaScript itself uses Unicode internally, you can still run into charset conversion problems. Consider the following example of charset conversion issues with a very simple HTML and JS file. In this example, a hello.html document says &#8220;Hello&#8221; when you click a button. The button calls a snippet of JavaScript (the sayHello function) to display [...]]]></description>
		<wfw:commentRss>http://joconner.com/2008/09/javascript-file-encoding/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Localizing JavaScript with JSPs</title>
		<link>http://joconner.com/2008/08/localizing-javascript-with-jsps/</link>
		<comments>http://joconner.com/2008/08/localizing-javascript-with-jsps/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 07:41:14 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://joconner.com/javascript/localizing-javascript-with-jsps</guid>
		<description><![CDATA[Last week a friend asked an interesting web-based localization question. He surprised me with it. I wish that I had considered it before, but I had not. In my less than complete analysis of his problem, I found a solution, but I don&#8217;t know if he&#8217;ll like it. Hell, I barely like it myself, but [...]]]></description>
		<wfw:commentRss>http://joconner.com/2008/08/localizing-javascript-with-jsps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
