<?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 on: Changes to Internet approved: Expect lots of annoying URLs now</title>
	<atom:link href="http://www.crunchgear.com/2008/06/27/changes-to-internet-approved-expect-lots-of-annoying-urls-now/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crunchgear.com/2008/06/27/changes-to-internet-approved-expect-lots-of-annoying-urls-now/</link>
	<description>Gadgets, gear and computer hardware.</description>
	<lastBuildDate>Tue, 10 Nov 2009 15:11:01 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul</title>
		<link>http://www.crunchgear.com/2008/06/27/changes-to-internet-approved-expect-lots-of-annoying-urls-now/comment-page-1/#comment-750335</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sat, 28 Jun 2008 00:43:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=28903#comment-750335</guid>
		<description>Allow me to geek out for a moment:
Have you seen the way they&#039;re going to encode the non-ASCII international characters into the ASCII domain names?  It&#039;s not UTF8 with % HEX HEX encoding, as you might expect from looking at any international URL.  Oh no, that would be too logical.  They invented a brand new encoding called Punycode to encode the Unicode characters.  I&#039;m not joking, check out RFC 3492.  It&#039;s a fairly complex algorithm, and the output looks like gibberish.  Example conversion of Chinese (simplified):
u+4ED6 u+4EEC u+4E3A u+4EC0 u+4E48 u+4E0D u+8BF4 u+4E2D u+6587
Punycode: ihqwcrb4cv8a8dqg056pqjye

Intuitive, eh?  I guess it doesn&#039;t really matter since your browser will normally do the conversion for you, but still come on!  Domain names are supposed to be readable!</description>
		<content:encoded><![CDATA[<p>Allow me to geek out for a moment:<br />
Have you seen the way they&#8217;re going to encode the non-ASCII international characters into the ASCII domain names?  It&#8217;s not UTF8 with % HEX HEX encoding, as you might expect from looking at any international URL.  Oh no, that would be too logical.  They invented a brand new encoding called Punycode to encode the Unicode characters.  I&#8217;m not joking, check out RFC 3492.  It&#8217;s a fairly complex algorithm, and the output looks like gibberish.  Example conversion of Chinese (simplified):<br />
u+4ED6 u+4EEC u+4E3A u+4EC0 u+4E48 u+4E0D u+8BF4 u+4E2D u+6587<br />
Punycode: ihqwcrb4cv8a8dqg056pqjye</p>
<p>Intuitive, eh?  I guess it doesn&#8217;t really matter since your browser will normally do the conversion for you, but still come on!  Domain names are supposed to be readable!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: greatslack</title>
		<link>http://www.crunchgear.com/2008/06/27/changes-to-internet-approved-expect-lots-of-annoying-urls-now/comment-page-1/#comment-750107</link>
		<dc:creator>greatslack</dc:creator>
		<pubDate>Fri, 27 Jun 2008 19:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=28903#comment-750107</guid>
		<description>Seems like a ploy to make a lot of people a lot of money.  Also an opportunity for snobbery.

&quot;Oh, you&#039;ve got your own website?  That&#039;s cute.  I&#039;ve got my own TLD.&quot;</description>
		<content:encoded><![CDATA[<p>Seems like a ploy to make a lot of people a lot of money.  Also an opportunity for snobbery.</p>
<p>&#8220;Oh, you&#8217;ve got your own website?  That&#8217;s cute.  I&#8217;ve got my own TLD.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
