Re: Advice on handling malformed CSV with FasterCSV

From: Wes G.

  1. Is there a way to get FasterCSV to accept input like the
    above? How can I set up a custom parsing scheme?

I don’t know the answer to this question.

  1. Should I modify the FasterCSV parser directly to accept
    this sort of input?

I would personally say no. Keep the core library powerful and
streamlined; don’t ‘fix’ it to accept crazy data.

  1. Should I pre-process the file to eliminate/modify these sorts of
    cases to improve the likelihood of a successful FasterCSV parse?

That’s what I would suggest. It gives you the power to decide how you
want to handle it. If your input data is:
then I think you’d much prefer to decide how to clean that up (to match
your legacy system, perhaps) rather than hoping that someone put code in
the library that handles it the same way.