Closed blcham closed 1 year ago
From the picture below I understand that It is allowed to have a delimiter in the value
The first example (I saw a line where value of cell starts with quotes (see "PAINT):
) wrapped in the double quotes is valid but the second one is incorrect, it should be wrapped in double quotes, and the quote inside should be escaped by another one.
yes but it says: "if double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by preceding it with another double quote."
So to me, it seems that their export was valid. See also: https://stackoverflow.com/questions/28669201/avoid-double-quote-confusion-when-generating-csv-files
I see, but if you look at the non-escaped = *textdata
, text data does not include a double quote in the range
Yes, but it is related to CSV standard and they send us TSV :( Here i another document: https://www.iana.org/assignments/media-types/text/tab-separated-values.
@Matthew-Kulich I found it !!! the solution for SuperCSV is described here (quite funny to read whole post:): https://stackoverflow.com/a/15213005/6812609
Also please upgrade to the newest version (2.4.0) of supercsv, it has better error messages e.g.: https://github.com/super-csv/super-csv/issues/33
@Matthew-Kulich should we close this issue ?
Yes, we can.
The goal is to find out if we are getting valid CSV as input or not (see https://www.rfc-editor.org/rfc/rfc4180). Based on that we should fix/change the implementation of the pipeline.
I saw a line where value of cell starts with quotes (see
"PAINT
):On the other hand we have
"
(quote) used inside:By the way i checked how it is implemented in CSV processor and I think it does not support quotes inside of text ....