News for hackers. Stuff that matters.

A comment on Dangers of CSV Injection. Parent comment

Re:Dangers of CSV Injection by seszett on Tuesday October 10, 2017 @04:21AM (#15440206)
> Some idiot somewhere decided that Comma Separated Values in certain locales should be based on semicolons

Semicolons are really better though, because they aren't used as a decimal separator unlike commas in most countries.

I don't know about Excel, but LibreOffice allows very easily to select which parameters to use when opening a CSV file, it works just fine.

[ Parent | on HN ]
Re:Dangers of CSV Injection by PhasmaFelis on Tuesday October 10, 2017 @04:40AM (#15440292)
> Semicolons are really better though, because they aren't used as a decimal separator unlike commas in most countries.

If you're going to separate values with semicolons--which is perfectly reasonable--I feel like you probably shouldn't do that with a format called Comma Separated Values.

[ Parent | on HN ]
Re:Dangers of CSV Injection by mulmen on Tuesday October 10, 2017 @05:16AM (#15440454)
Picking a less-common separator might help but you could also just follow RFC 4180 and quote fields that have commas then double any single quotes in values.
[ Parent | on HN ]
Re:Dangers of CSV Injection by mark-r on Tuesday October 10, 2017 @11:36AM (#15442670)
You can also use the file import wizard in Excel to make similar choices. But that's not the default behavior for files with a .csv extension.
[ Parent | on HN ]