Leonard Siu

I agree we probably shouldn't be calling this a bug, more like a suggestion. I am probably not the first one to trip up on this as shown in support request: https://sourceforge.net/p/opencsv/support-requests/45/. Yes, I did found a way to work around it as show in the commented out line in my test case: // to get this to work, we cannot just use the default reader like we did with the default writer, we need to "disable" the escape char // CSVReader csvReader = new CSVReaderBuilder(new FileReader(file)).withCSVParser(new...

My first thought is to default to no escape value for the CsvParser for my use case, but I realizes this has large implication, and want to put this up here for discussion first.

This is somewhat related to this: https://sourceforge.net/p/opencsv/support-requests/45/

In consistency between CsvReader and CsvWriter with backslash