<?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: You can have your delimiter in any character, as long as it is comma</title>
	<atom:link href="http://halfcooked.com/blog/2009/06/24/you-can-have-your-delimiter-in-any-character-as-long-as-it-is-comma/feed/" rel="self" type="application/rss+xml" />
	<link>http://halfcooked.com/blog/2009/06/24/you-can-have-your-delimiter-in-any-character-as-long-as-it-is-comma/</link>
	<description>Wherein I write some stuff  that you may like to read. Or not, its up to you really.</description>
	<lastBuildDate>Fri, 11 Nov 2011 18:30:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Slate</title>
		<link>http://halfcooked.com/blog/2009/06/24/you-can-have-your-delimiter-in-any-character-as-long-as-it-is-comma/comment-page-1/#comment-38243</link>
		<dc:creator>Slate</dc:creator>
		<pubDate>Wed, 24 Jun 2009 10:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://halfcooked.com/blog/?p=116#comment-38243</guid>
		<description>I am working as designer on a Datawarehousing projekt, and we require the same format, for the input, too. The pipe delimiter is a very good choice. I do not go into further details about that here.

If you are feeding your system with handmade interface files, then you have to implement a guessing-error-retry layer in the loader anyway. And don&#039;t forget to assign a full time programmer to this task, who is trained to be unpopular:) 

FYI there exists at least two different versions of the &quot;popular desktop productivity software &quot;, which produce different csv output with the same settings.

IMHO the bigger problem is &quot;ASCII encoded DOS file&quot;, which means no i18n support. The casual observer would think, that this system will have a very hard time loading a description or a surname field.</description>
		<content:encoded><![CDATA[<p>I am working as designer on a Datawarehousing projekt, and we require the same format, for the input, too. The pipe delimiter is a very good choice. I do not go into further details about that here.</p>
<p>If you are feeding your system with handmade interface files, then you have to implement a guessing-error-retry layer in the loader anyway. And don&#8217;t forget to assign a full time programmer to this task, who is trained to be unpopular:) </p>
<p>FYI there exists at least two different versions of the &#8220;popular desktop productivity software &#8220;, which produce different csv output with the same settings.</p>
<p>IMHO the bigger problem is &#8220;ASCII encoded DOS file&#8221;, which means no i18n support. The casual observer would think, that this system will have a very hard time loading a description or a surname field.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

