<?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: People, mind your dates&#8230; plz?</title>
	<atom:link href="http://blog.nkadesign.com/2007/people-mind-your-dates-plz/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nkadesign.com/2007/people-mind-your-dates-plz/</link>
	<description>Just another programming weblog</description>
	<pubDate>Thu, 28 Aug 2008 07:46:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Alex Dybenko</title>
		<link>http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8956</link>
		<dc:creator>Alex Dybenko</dc:creator>
		<pubDate>Mon, 04 Aug 2008 07:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8956</guid>
		<description>&lt;p&gt;Hi,
i think best aproach is one Access has. User can setup the date format he likes in control panel and Access uses it to enter and display dates, if you set format to short date. I follow this in my applications and it works fine for different contries&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi,
i think best aproach is one Access has. User can setup the date format he likes in control panel and Access uses it to enter and display dates, if you set format to short date. I follow this in my applications and it works fine for different contries</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Renaud</title>
		<link>http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8954</link>
		<dc:creator>Renaud</dc:creator>
		<pubDate>Mon, 04 Aug 2008 01:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8954</guid>
		<description>&lt;p&gt;Hi Tony,
thanks for dropping by.
Sorry to have bundled the USA with Canada in this, but from what you say, the situation is even worse in Canada with multiple formats being in use.&lt;/p&gt;

&lt;p&gt;You are right that ISO8601 is unambiguous. I would be glad if it were more widely adopted and everyone knew about it, but it's not the case unfortunately and I doubt most people would be aware of the order in which the date is specified, which makes it ambiguous to read without that knowledge.&lt;/p&gt;

&lt;p&gt;Whatever your pick, the point is to make dates as unambiguous and readable as possible so order doesn't matter.&lt;/p&gt;

&lt;p&gt;For website in multiple language where the user's locale locale is not detected to print the date in the format they expect, then the ISO YYYY/MM/DD is preferable.&lt;/p&gt;

&lt;p&gt;In English websites, documentation, etc read by an international audience, I still think that 25MAY2008 or MAY25,2008 or 2008/MAY/25 or any other variation with the year in full and the month in letters is the only way to make it absolutely unambiguous to everyone.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Tony,
thanks for dropping by.
Sorry to have bundled the USA with Canada in this, but from what you say, the situation is even worse in Canada with multiple formats being in use.</p>

<p>You are right that ISO8601 is unambiguous. I would be glad if it were more widely adopted and everyone knew about it, but it&#8217;s not the case unfortunately and I doubt most people would be aware of the order in which the date is specified, which makes it ambiguous to read without that knowledge.</p>

<p>Whatever your pick, the point is to make dates as unambiguous and readable as possible so order doesn&#8217;t matter.</p>

<p>For website in multiple language where the user&#8217;s locale locale is not detected to print the date in the format they expect, then the ISO YYYY/MM/DD is preferable.</p>

<p>In English websites, documentation, etc read by an international audience, I still think that 25MAY2008 or MAY25,2008 or 2008/MAY/25 or any other variation with the year in full and the month in letters is the only way to make it absolutely unambiguous to everyone.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Toews</title>
		<link>http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8953</link>
		<dc:creator>Tony Toews</dc:creator>
		<pubDate>Sun, 03 Aug 2008 23:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8953</guid>
		<description>&lt;p&gt;Whoops .   dd/mm.yy  should be dd/mm/yy.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Whoops .   dd/mm.yy  should be dd/mm/yy.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Toews</title>
		<link>http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8952</link>
		<dc:creator>Tony Toews</dc:creator>
		<pubDate>Sun, 03 Aug 2008 20:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nkadesign.com/2007/people-mind-your-dates-plz/#comment-8952</guid>
		<description>&lt;p&gt;1) Some Canadians including some government offices use dd/mm.yy format.  So your comment about North America is incorrect.&lt;/p&gt;

&lt;p&gt;2) Will all due respect I strenuously disagree with 05MAY2006 or similar as the date format.   The ISO standard is yyyy-mm-dd.  That date format is unambiguous.&lt;/p&gt;

&lt;p&gt;Otherwise your blog postings look quite interesting.  I'll be following your blog.&lt;/p&gt;

&lt;p&gt;Tony Toews, MS Access MVP&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>1) Some Canadians including some government offices use dd/mm.yy format.  So your comment about North America is incorrect.</p>

<p>2) Will all due respect I strenuously disagree with 05MAY2006 or similar as the date format.   The ISO standard is yyyy-mm-dd.  That date format is unambiguous.</p>

<p>Otherwise your blog postings look quite interesting.  I&#8217;ll be following your blog.</p>

<p>Tony Toews, MS Access MVP</p>]]></content:encoded>
	</item>
</channel>
</rss>
