<?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: For God&#8217;s sake: there is more to the world than just USA</title>
	<atom:link href="http://rassie.org/archives/147/feed" rel="self" type="application/rss+xml" />
	<link>http://rassie.org/archives/147</link>
	<description>Barking at technology</description>
	<lastBuildDate>Wed, 28 Dec 2011 06:51:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Nikolai Prokoschenko</title>
		<link>http://rassie.org/archives/147/comment-page-1#comment-10</link>
		<dc:creator>Nikolai Prokoschenko</dc:creator>
		<pubDate>Sat, 03 Nov 2007 20:39:59 +0000</pubDate>
		<guid isPermaLink="false">http://rassie.org/archives/147#comment-10</guid>
		<description>phil: This is not about e-mail names (before @), but about domain names. It&#039;s been widely criticized that one can have umlauts in their domain name now, but not in their name without considerable effort. What your company is doing is a workaround at best, consider what you&#039;ll be printing on a business card? Two or three different addresses won&#039;t do, in the end you&#039;d be printing and giving away only the most commonly understandable address, which will make other aliases obsolete. No hope for solution as far as I can see now :(</description>
		<content:encoded><![CDATA[<p>phil: This is not about e-mail names (before @), but about domain names. It&#8217;s been widely criticized that one can have umlauts in their domain name now, but not in their name without considerable effort. What your company is doing is a workaround at best, consider what you&#8217;ll be printing on a business card? Two or three different addresses won&#8217;t do, in the end you&#8217;d be printing and giving away only the most commonly understandable address, which will make other aliases obsolete. No hope for solution as far as I can see now :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikolai Prokoschenko</title>
		<link>http://rassie.org/archives/147/comment-page-1#comment-9</link>
		<dc:creator>Nikolai Prokoschenko</dc:creator>
		<pubDate>Sat, 03 Nov 2007 20:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://rassie.org/archives/147#comment-9</guid>
		<description>jfedor: I&#039;m actually not defending IDN in any way. I have been growing up with two writing systems and I actually feed the need for some kind of URL internationalization. However, I do not really feel that current solution will be the ultimate one. But the fact alone that it exists is enough for me to make everyone else support it so that it&#039;s at least usable. Normal people will not be thinking about whatever technical problems there might be when registering a domain name, they&#039;ll ask their registrar whether they can have a .de domain written like their surname and the registrar will say, yes, it&#039;s possible. We can&#039;t possibly make these people liable for lack of a good general solution when they try to register at some web site which tells them they don&#039;t have a valid e-mail address. We have to support IDN, whether we want it or not. As web developers, we&#039;ve committed to this.</description>
		<content:encoded><![CDATA[<p>jfedor: I&#8217;m actually not defending IDN in any way. I have been growing up with two writing systems and I actually feed the need for some kind of URL internationalization. However, I do not really feel that current solution will be the ultimate one. But the fact alone that it exists is enough for me to make everyone else support it so that it&#8217;s at least usable. Normal people will not be thinking about whatever technical problems there might be when registering a domain name, they&#8217;ll ask their registrar whether they can have a .de domain written like their surname and the registrar will say, yes, it&#8217;s possible. We can&#8217;t possibly make these people liable for lack of a good general solution when they try to register at some web site which tells them they don&#8217;t have a valid e-mail address. We have to support IDN, whether we want it or not. As web developers, we&#8217;ve committed to this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://rassie.org/archives/147/comment-page-1#comment-8</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sat, 03 Nov 2007 17:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://rassie.org/archives/147#comment-8</guid>
		<description>One thing my company, and I imagine others do also, is to give people with &quot;international&quot; characters in their name multiple email address aliases.  So Heinrich Müller would have hmüller@company.com and hmueller@company.com.  This defeats both overly restrictive regexps and the inability of people with US keyboard to easily type their name, but they can still use their &quot;proper&quot; name with people who speak their name&#039;s language.</description>
		<content:encoded><![CDATA[<p>One thing my company, and I imagine others do also, is to give people with &#8220;international&#8221; characters in their name multiple email address aliases.  So Heinrich Müller would have hmüller@company.com and <a href="mailto:hmueller@company.com">hmueller@company.com</a>.  This defeats both overly restrictive regexps and the inability of people with US keyboard to easily type their name, but they can still use their &#8220;proper&#8221; name with people who speak their name&#8217;s language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jfedor</title>
		<link>http://rassie.org/archives/147/comment-page-1#comment-7</link>
		<dc:creator>jfedor</dc:creator>
		<pubDate>Sat, 03 Nov 2007 15:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://rassie.org/archives/147#comment-7</guid>
		<description>No, please stop. The IDN must die. It&#039;s a bad, bad idea and it&#039;s only implemented so that every company with an umlaut in its name must buy _both_ domains (or, even three of them, one with an &quot;u&quot;, one with &quot;ü&quot; and one with &quot;ue&quot;). Hence, more money for the registrars.

And don&#039;t think that I&#039;m saying this because I am a stupid American that has no idea that there are other alphabets and scripts out there. My last name has a &quot;ń&quot; in it. But I don&#039;t need it in my website URL.

I know what you&#039;re going to say - that the CJKV folks have it even worse. That&#039;s _exactly_ why we must keep the domain system to ASCII. How am I supposed to copy an email address from a business card if it looks like this: info@例子.测试?</description>
		<content:encoded><![CDATA[<p>No, please stop. The IDN must die. It&#8217;s a bad, bad idea and it&#8217;s only implemented so that every company with an umlaut in its name must buy <em>both</em> domains (or, even three of them, one with an &#8220;u&#8221;, one with &#8220;ü&#8221; and one with &#8220;ue&#8221;). Hence, more money for the registrars.</p>

<p>And don&#8217;t think that I&#8217;m saying this because I am a stupid American that has no idea that there are other alphabets and scripts out there. My last name has a &#8220;ń&#8221; in it. But I don&#8217;t need it in my website URL.</p>

<p>I know what you&#8217;re going to say - that the CJKV folks have it even worse. That&#8217;s <em>exactly</em> why we must keep the domain system to ASCII. How am I supposed to copy an email address from a business card if it looks like this: info@例子.测试?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikolai Prokoschenko</title>
		<link>http://rassie.org/archives/147/comment-page-1#comment-6</link>
		<dc:creator>Nikolai Prokoschenko</dc:creator>
		<pubDate>Fri, 02 Nov 2007 14:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://rassie.org/archives/147#comment-6</guid>
		<description>Hey, you&#039;re here so soon :) Thanks for your comment; I&#039;ve actually found that article good too, I&#039;m just worried that the first site on Google for the query &quot;e-mail validation regular expression&quot; does not even mention the rest of the world. There are a lot of newbies and copy-pasters who won&#039;t even consider thinking for themselves when a solution from an &quot;authority&quot; is available. I&#039;ve also contacted regular-expressions.info on this topic, hopefully they&#039;ll correct it someday.</description>
		<content:encoded><![CDATA[<p>Hey, you&#8217;re here so soon :) Thanks for your comment; I&#8217;ve actually found that article good too, I&#8217;m just worried that the first site on Google for the query &#8220;e-mail validation regular expression&#8221; does not even mention the rest of the world. There are a lot of newbies and copy-pasters who won&#8217;t even consider thinking for themselves when a solution from an &#8220;authority&#8221; is available. I&#8217;ve also contacted regular-expressions.info on this topic, hopefully they&#8217;ll correct it someday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ragnvald or Reinhold</title>
		<link>http://rassie.org/archives/147/comment-page-1#comment-5</link>
		<dc:creator>Ragnvald or Reinhold</dc:creator>
		<pubDate>Fri, 02 Nov 2007 12:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://rassie.org/archives/147#comment-5</guid>
		<description>Yes, there is MUCH more to the world than en_US. We Canadians can attest to that. I used to work with a company that has an email product, and after ten years in the business, they realized that handling 90% or 95% or even 99% of the possible emails was not enough, sooner or later a client would have a need to handle m&#252;ller.info and they would have to upgrade their validity checking. They now warn people if the email address looks unusual--they don&#039;t even call it invalid--but accept that the only way to be sure is to send the email and see if it is rejected by the host.

What I liked about that post is that it discussed teh trade-offs, it didn&#039;t pretend that there was a foolproof mechanism, even for US addresses.</description>
		<content:encoded><![CDATA[<p>Yes, there is MUCH more to the world than en_US. We Canadians can attest to that. I used to work with a company that has an email product, and after ten years in the business, they realized that handling 90% or 95% or even 99% of the possible emails was not enough, sooner or later a client would have a need to handle m&uuml;ller.info and they would have to upgrade their validity checking. They now warn people if the email address looks unusual&#8212;they don&#8217;t even call it invalid&#8212;but accept that the only way to be sure is to send the email and see if it is rejected by the host.</p>

<p>What I liked about that post is that it discussed teh trade-offs, it didn&#8217;t pretend that there was a foolproof mechanism, even for US addresses.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

