<?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: Importing Non-Standard Text Files</title>
	<atom:link href="http://sixfriedrice.com/wp/importing-non-standard-text-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://sixfriedrice.com/wp/importing-non-standard-text-files/</link>
	<description>smart business solutions</description>
	<lastBuildDate>Fri, 18 May 2012 01:30:19 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ken</title>
		<link>http://sixfriedrice.com/wp/importing-non-standard-text-files/comment-page-1/#comment-1880</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Thu, 31 Dec 2009 23:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/importing-non-standard-text-files/#comment-1880</guid>
		<description>Great comment. Really helped me with a large file (just under 1 million records) that was pipe-delimited. That would have been 15 million find/replace operations. Wow -- the Terminal tr command is virtually instantaneous!

However, the syntax needed to be a little different, it seems, at least on my OS X 10.5.8 machine. To go from pipes to commas, the command looks like this:

tr &quot;&#124;&quot; &quot;,&quot;  thecleanfile.txt

As a Unix newbie, I didn&#039;t know that I needed double-quotes around the strings. And I didn&#039;t know that the &quot;&quot; are needed to specify the input and output files respectively. I thought they were the typical sort of bracketing used by folks elsewhere to indicate &quot;install your own text here&quot; so I omitted them. Oops. 

Just thought I&#039;d mention that, since this page seems to be directed to folks who, like me, are not Terminal experts.</description>
		<content:encoded><![CDATA[<p>Great comment. Really helped me with a large file (just under 1 million records) that was pipe-delimited. That would have been 15 million find/replace operations. Wow &#8212; the Terminal tr command is virtually instantaneous!</p>
<p>However, the syntax needed to be a little different, it seems, at least on my OS X 10.5.8 machine. To go from pipes to commas, the command looks like this:</p>
<p>tr &#8220;|&#8221; &#8220;,&#8221;  thecleanfile.txt</p>
<p>As a Unix newbie, I didn&#8217;t know that I needed double-quotes around the strings. And I didn&#8217;t know that the &#8220;&#8221; are needed to specify the input and output files respectively. I thought they were the typical sort of bracketing used by folks elsewhere to indicate &#8220;install your own text here&#8221; so I omitted them. Oops. </p>
<p>Just thought I&#8217;d mention that, since this page seems to be directed to folks who, like me, are not Terminal experts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Antunes</title>
		<link>http://sixfriedrice.com/wp/importing-non-standard-text-files/comment-page-1/#comment-337</link>
		<dc:creator>Jesse Antunes</dc:creator>
		<pubDate>Thu, 09 Aug 2007 23:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/importing-non-standard-text-files/#comment-337</guid>
		<description>@Othni -

Text parsing is quite challenging in filemaker.  I can&#039;t go into detail about exactly how you would do it because it can be quite different depending on the data that you want to parse. I might be able to at least point you in the right direction.  Here are a couple questions for you:

What type of delimiter does the file use?  

Are the lines you would like to dispose of uniform?</description>
		<content:encoded><![CDATA[<p>@Othni -</p>
<p>Text parsing is quite challenging in filemaker.  I can&#8217;t go into detail about exactly how you would do it because it can be quite different depending on the data that you want to parse. I might be able to at least point you in the right direction.  Here are a couple questions for you:</p>
<p>What type of delimiter does the file use?  </p>
<p>Are the lines you would like to dispose of uniform?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Othni J. Morales</title>
		<link>http://sixfriedrice.com/wp/importing-non-standard-text-files/comment-page-1/#comment-328</link>
		<dc:creator>Othni J. Morales</dc:creator>
		<pubDate>Thu, 09 Aug 2007 03:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/importing-non-standard-text-files/#comment-328</guid>
		<description>Thanks for the tip.

I have a similar problem a little more complicated. I am importing whole folders of text files. Those text files have lines that I want converted to records. I want to accomplish more or less the same thing, and that is, to import the content of the text file in a TEMP field and later parse it.

The only problem is that the content of that TEMP field has to be converted to N number of records and then the data (a couple of fields only) parsed to fields. 

How do I start to parse the lines that are going to be records (some lines are junk) and then parse the fields?</description>
		<content:encoded><![CDATA[<p>Thanks for the tip.</p>
<p>I have a similar problem a little more complicated. I am importing whole folders of text files. Those text files have lines that I want converted to records. I want to accomplish more or less the same thing, and that is, to import the content of the text file in a TEMP field and later parse it.</p>
<p>The only problem is that the content of that TEMP field has to be converted to N number of records and then the data (a couple of fields only) parsed to fields. </p>
<p>How do I start to parse the lines that are going to be records (some lines are junk) and then parse the fields?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Coffey</title>
		<link>http://sixfriedrice.com/wp/importing-non-standard-text-files/comment-page-1/#comment-104</link>
		<dc:creator>Geoff Coffey</dc:creator>
		<pubDate>Wed, 11 Jul 2007 22:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/importing-non-standard-text-files/#comment-104</guid>
		<description>&lt;p&gt;The TR command line sample had a typo. It was putting a Mac OS style line ending in place of $, instead of a tab. I just fixed it. Sorry &#039;bout that :)&lt;/p&gt;

&lt;p&gt;Geoff&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The TR command line sample had a typo. It was putting a Mac OS style line ending in place of $, instead of a tab. I just fixed it. Sorry &#8217;bout that <img src='http://sixfriedrice.com/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Geoff</p>
]]></content:encoded>
	</item>
</channel>
</rss>

