<?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: Twitter and Web Globalization</title>
	<atom:link href="http://www.globalbydesign.com/blog/2009/05/20/twitter-and-web-globalization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.globalbydesign.com/blog/2009/05/20/twitter-and-web-globalization/</link>
	<description>Adventures in Web Globalization</description>
	<lastBuildDate>Wed, 17 Mar 2010 14:06:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gareth Morgan</title>
		<link>http://www.globalbydesign.com/blog/2009/05/20/twitter-and-web-globalization/comment-page-1/#comment-32930</link>
		<dc:creator>Gareth Morgan</dc:creator>
		<pubDate>Thu, 22 Oct 2009 15:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.globalbydesign.com/?p=1693#comment-32930</guid>
		<description>Twitter seems to have some good policies in place re. name squatting and the like (see http://help.twitter.com/forums/26257/entries), but looks like they haven&#039;t addressed the multiple language feeds issue. I can see problems if users go with any willy-nilly syntax for naming their language offerings, rather than following the ISO 639-2 standard. But then how many people would know to name their Danish feed da_dk? And for branding or promoting that name to Danish customers, da_dk is not exactly memorable. Some education would help Twitter point its users on the right track, though whether they will follow standards is another matter (just like TLDs have been co-opted into brand and product names)</description>
		<content:encoded><![CDATA[<p>Twitter seems to have some good policies in place re. name squatting and the like (see <a href="http://help.twitter.com/forums/26257/entries)" rel="nofollow">http://help.twitter.com/forums/26257/entries)</a>, but looks like they haven&#8217;t addressed the multiple language feeds issue. I can see problems if users go with any willy-nilly syntax for naming their language offerings, rather than following the ISO 639-2 standard. But then how many people would know to name their Danish feed da_dk? And for branding or promoting that name to Danish customers, da_dk is not exactly memorable. Some education would help Twitter point its users on the right track, though whether they will follow standards is another matter (just like TLDs have been co-opted into brand and product names)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Twitter Domain Rush: Don&#8217;t Get &#8220;Twit-jacked&#8221; &#124; Global by Design</title>
		<link>http://www.globalbydesign.com/blog/2009/05/20/twitter-and-web-globalization/comment-page-1/#comment-28050</link>
		<dc:creator>The Twitter Domain Rush: Don&#8217;t Get &#8220;Twit-jacked&#8221; &#124; Global by Design</dc:creator>
		<pubDate>Wed, 27 May 2009 03:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.globalbydesign.com/?p=1693#comment-28050</guid>
		<description>[...] previous post on Twitter got me thinking about what other companies had registered language-specific domains for their [...]</description>
		<content:encoded><![CDATA[<p>[...] previous post on Twitter got me thinking about what other companies had registered language-specific domains for their [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
