Allow for non-comma separators

[robwyse]

As it currently stands, a CSV file with a non-comma separator will return "no valid row found in the CSV file". Given that Excel uses a semicolon as CSV separator by default when comma is used the decimal separator, as is the case in e.g. the default Dutch language settings, being able to parse such CSV files without having to replace all semicolons with commas would increase user friendliness, especially for less tech-savvy users.

[nvanderperren]

We are aware of this Microsoft problem, but for now I would advise to use LibreOffice or Google Sheets to create CSV's or transform Excel CSV's. We will point this out in the wiki.

We are using an already existing npm module to parse csv's that only supports comma seperated values documents. Maybe in the near future, we could look how we could support the Excel CSV. (Excel is just not a good tool for creating CSV's).

[robwyse]

I've done some playing around, and found that with csv-parse you can set the separator character via the "delimiter" option. This opens up the possibility of letting the user choose the separator, perhaps under the advanced options, with comma as the default value.