in reply to Recommendations for parsing invalid CSV

Are you by any chance working together with Michael Fowler? He asks almost the same thing in this RT entry.

See my comments there.


Enjoy, Have FUN! H.Merijn
  • Comment on Re: Recommendations for parsing invalid CSV

Replies are listed 'Best First'.
Re^2: Recommendations for parsing invalid CSV
by markjugg (Curate) on Apr 21, 2008 at 14:37 UTC
    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

[reply]

      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