-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delimiter not auto-detected correctly when quoted fields contains more than one new line char #681
Comments
Could you test this is fixed on current master? #687 may have fixed this. |
@pokoli - I think I am having a related issue and I just tested on the master branch with no luck. I tried to remove new line characters, but the error still occurs - so I think my issue is completely unrelated. On the demo website, it detects the column as If I set the delimiter in the parsing options to CSV:
|
When trying to auto-detect the delimiter from following line:
Field1;Field2;"F\ni,e,l,d\n,3"
it wrongly guesses the delimiter as COMMA instead of SEMICOLON, even if the field with new line and comma is quoted.
Tested on demo site: https://www.papaparse.com/demo
Expected behavior would be that the guessing logic correctly takes a quoted string as a field and would not consider its characters when guessing the delimiter, even if they contain new line: ["Field1", "Field2", "F↵i,e,l,d↵,3"]
PS. Escaping the new line char within the quoted field is not an option in our business case.
The text was updated successfully, but these errors were encountered: