<?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"
	>
<channel>
	<title>Comments on: Internationalization of Names</title>
	<atom:link href="http://zevils.com/2007/12/28/internationalization-of-names/feed/" rel="self" type="application/rss+xml" />
	<link>http://zevils.com/2007/12/28/internationalization-of-names/</link>
	<description>More fun than a gallon of strawberries</description>
	<pubDate>Tue, 06 Jan 2009 03:24:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Adrienne Adams</title>
		<link>http://zevils.com/2007/12/28/internationalization-of-names/#comment-134</link>
		<dc:creator>Adrienne Adams</dc:creator>
		<pubDate>Fri, 07 Mar 2008 20:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://zevils.com/2007/12/28/internationalization-of-names/#comment-134</guid>
		<description>&lt;p&gt;Thanks for this article. I have linked to it from a topic I started on the WordPress forum, as I have issues with the limited way that WordPress treats names. Blogging is international, and applications like WordPress (in my view) are especially compelled to non-culturally-biased practices.&lt;/p&gt;

&lt;p&gt;My suggestion for WordPress developers was simply this: provide multiple entry fields, &lt;em&gt;sans&lt;/em&gt; culturally-biased labels, and then&#8212;as you mention above&#8212;&lt;em&gt;simply &lt;strong&gt;ask the person&lt;/strong&gt; how he/she would prefer to be addressed.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The data design shouldn't impose cultural structure, merely mirror it.&lt;/p&gt;

&lt;p&gt;I also agree with Chad's suggestion of avoiding gender classification, as well.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for this article. I have linked to it from a topic I started on the WordPress forum, as I have issues with the limited way that WordPress treats names. Blogging is international, and applications like WordPress (in my view) are especially compelled to non-culturally-biased practices.</p>

<p>My suggestion for WordPress developers was simply this: provide multiple entry fields, <em>sans</em> culturally-biased labels, and then&mdash;as you mention above&mdash;<em>simply <strong>ask the person</strong> how he/she would prefer to be addressed.</em></p>

<p>The data design shouldn&#8217;t impose cultural structure, merely mirror it.</p>

<p>I also agree with Chad&#8217;s suggestion of avoiding gender classification, as well.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://zevils.com/2007/12/28/internationalization-of-names/#comment-35</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Fri, 28 Dec 2007 22:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://zevils.com/2007/12/28/internationalization-of-names/#comment-35</guid>
		<description>&lt;p&gt;I understand this confusion and conflation.  I myself have a more thai/russian style nickname, in the sense that it was given to me very shortly after birth, is derived from my first name, and I use it far more frequently than my actual first name.  Fortunately, when I started the new job, I was able to have a conversation with IT early enough that they formulated my e-mail address there with my well used nickname, instead of my lesser known full name.&lt;/p&gt;

&lt;p&gt;I won't go on about the inappropriateness of encoding metadata (generation, gender) into your name.  Efficient, but as we can see, in the long run, a bad idea.  This is different from the appelations of Sr., Jr., or in my case, III....  these are also metadata in the name, but they are not concatenated or hashed with any other part of the name, and so in many circumstances can be safely disregarded.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I understand this confusion and conflation.  I myself have a more thai/russian style nickname, in the sense that it was given to me very shortly after birth, is derived from my first name, and I use it far more frequently than my actual first name.  Fortunately, when I started the new job, I was able to have a conversation with IT early enough that they formulated my e-mail address there with my well used nickname, instead of my lesser known full name.</p>

<p>I won&#8217;t go on about the inappropriateness of encoding metadata (generation, gender) into your name.  Efficient, but as we can see, in the long run, a bad idea.  This is different from the appelations of Sr., Jr., or in my case, III&#8230;.  these are also metadata in the name, but they are not concatenated or hashed with any other part of the name, and so in many circumstances can be safely disregarded.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 3.819 seconds -->
