From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] csv files -> embarrasing
Date: Sun, 30 Apr 2006 19:34:17 -0500 [thread overview]
Message-ID: <d64c05865c6ae37dafcfa882f62c869b@quanstro.net> (raw)
ooks slightly more painful than the previous case, but i think that
using my original trick, one can continue to add elements to the
lifing pipeline and move character-stuffed " and \" out of the way, too.
and didn't i learn that trick well from parsing data from yahoo categories.
- erik
On Sun Apr 30 05:38:13 CDT 2006, mattmobile@proweb.co.uk wrote:
> > Is parsing CSV really so difficult?
>
> depends on your CSV
>
> 1, "2", "3""3","4, 4", "5\",5"
>
> which I interpret as (\n separated) :
> 1
> 2
> 3"3
> 4, 4
> 5",5
>
>
> If you've ever worked with Excel CSV you know what CSV hell is like
next reply other threads:[~2006-05-01 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 0:34 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-28 14:36 Steve Simon
2006-04-28 14:43 ` quanstro
2006-04-28 16:29 ` Russ Cox
2006-04-28 18:28 ` lucio
2006-04-30 10:36 ` matt
2006-06-01 13:53 ` Victor Nazarov
2006-06-01 16:06 ` rog
2006-06-02 3:09 ` Rogelio Serrano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d64c05865c6ae37dafcfa882f62c869b@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).