<?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; Unicode</title>
	<atom:link href="http://joconner.com/tag/unicode/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>These characters aren&#8217;t exotic!</title>
		<link>http://joconner.com/2010/06/exotic-chars/</link>
		<comments>http://joconner.com/2010/06/exotic-chars/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 07:31:07 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[Unicode]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[characters]]></category>

		<guid isPermaLink="false">http://joconner.com/2010/06/exotic-chars/</guid>
		<description><![CDATA[Recently I had the opportunity to sign up for health benefits with a 3rd party site that manages these things for my employer. Sites that collect data often limit the set of characters that you must use for each field. That&#8217;s reasonable for numeric fields, date fields, etc. After all, you don&#8217;t want invalid data [...]]]></description>
		<wfw:commentRss>http://joconner.com/2010/06/exotic-chars/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An Internationalization and Unicode Web Service?</title>
		<link>http://joconner.com/2009/07/i18n-web-service/</link>
		<comments>http://joconner.com/2009/07/i18n-web-service/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 07:54:27 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[Unicode]]></category>
		<category><![CDATA[i18n]]></category>

		<guid isPermaLink="false">http://joconner.com/2009/07/an-internationalization-and-unicode-web-service/</guid>
		<description><![CDATA[Chances are that your favorite development platform already has internationalization support built into it. And probably Unicode charset support is there too. For example, Java and .NET platforms contain lots of APIs for formatting dates, numbers, etc in locale-sensitive ways. And you can get Unicode character data easily too. Unfortunately, the Unicode standard changes periodically, [...]]]></description>
		<wfw:commentRss>http://joconner.com/2009/07/i18n-web-service/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Unicode support doesn&#8217;t mean your application is internationalized</title>
		<link>http://joconner.com/2008/10/unicode-support/</link>
		<comments>http://joconner.com/2008/10/unicode-support/#comments</comments>
		<pubDate>Mon, 06 Oct 2008 16:34:12 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[Unicode]]></category>
		<category><![CDATA[internationalization]]></category>

		<guid isPermaLink="false">http://joconner.com/unicode/unicode-support-doesnt-mean-your-application-is-internationalized</guid>
		<description><![CDATA[Over the years, I&#8217;ve helped many organizations internationalize their software products. One of the most common misunderstandings is how Unicode will help their product. Customers sometimes mistakenly believe that Unicode support will be sufficient to internationalize their products. Sometimes they believe that Unicode &#8220;support&#8221; is a single, yes-no, on-off ability, when instead Unicode support is [...]]]></description>
		<wfw:commentRss>http://joconner.com/2008/10/unicode-support/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>What is Unicode?</title>
		<link>http://joconner.com/2008/10/what-is-unicode/</link>
		<comments>http://joconner.com/2008/10/what-is-unicode/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 22:53:35 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[Unicode]]></category>
		<category><![CDATA[character set]]></category>
		<category><![CDATA[charset]]></category>

		<guid isPermaLink="false">http://joconner.com/unicode/what-is-unicode</guid>
		<description><![CDATA[Unicode is a character set standard. This particular standard assigns a unique number to every character used around the globe, regardless of written and spoken language, computing platform, or application. Unicode includes all the characters used from other more limited character sets. Prior to Unicode, smaller character sets assigned character values differently from each other. [...]]]></description>
		<wfw:commentRss>http://joconner.com/2008/10/what-is-unicode/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Character Conversion points</title>
		<link>http://joconner.com/2008/08/character-conversion-points/</link>
		<comments>http://joconner.com/2008/08/character-conversion-points/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 08:11:12 +0000</pubDate>
		<dc:creator>joconner</dc:creator>
				<category><![CDATA[Unicode]]></category>

		<guid isPermaLink="false">http://joconner.com/?p=16</guid>
		<description><![CDATA[You&#8217;d think this sort of problem would be resolved by now, but it&#8217;s not. It&#8217;s still almost impossible to quickly and easily migrate an application from the too common default Latin-1 to UTF-8 character set encoding. The problem isn&#8217;t that UTF-8 can&#8217;t handle the conversion. No, that&#8217;s definitely not it. UTF-8 can represent any Latin-1 [...]]]></description>
		<wfw:commentRss>http://joconner.com/2008/08/character-conversion-points/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
