Re^2: Recommendations for parsing invalid CSV

in reply to Re: Recommendations for parsing invalid CSV
in thread Recommendations for parsing invalid CSV

I am not. I'm working with an export of an older version of the "TimeMatters" software.

Regarding what Text::CSV_XS can do, in summary are you saying that one of the "allow_loose_quotes" or "allow_loose_escapes" option can or will be able to handle this?

That would certainly be the easiest path for me. Thanks so much for the fast and helpful response!

Mark Stosberg

Comment on Re^2: Recommendations for parsing invalid CSV

Replies are listed 'Best First'.
Re^3: Recommendations for parsing invalid CSV by Tux (Canon) on Apr 21, 2008 at 14:45 UTC
Yes. You'd have to play with `allow_loose_quotes`, `allow_loose_escapes` and/or setting `escape_char` to undef to find your best combination. The upcoming 0.43 has a new util examples/csv-check, which will tell you line number and position in-line of where the first failure happens Enjoy, Have FUN! H.Merijn	[reply] [d/l] [select]

In Section Seekers of Perl Wisdom