CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.
Excel mangles everthing…
I work with a lot of EANs and every CSV import into Excel means I have to pay extra attention to the EAN field, because Excel likes to think for me, and thinks that the scientific notation would be very helpful for me… It’s not! 8.72E+12 is useless to me, Excel!!!
And don’t get me started on FEB-01.
Fuck Excel’s CSV handing. It differs by locale, silently. Imagine the thousands of people every year who patiently wait to import a multi-megabyte CSV from some instrument only to see garbage because their language uses the decimal comma and semicolon separator.
CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.
Excel mangles everthing…
I work with a lot of EANs and every CSV import into Excel means I have to pay extra attention to the EAN field, because Excel likes to think for me, and thinks that the scientific notation would be very helpful for me… It’s not! 8.72E+12 is useless to me, Excel!!!
And don’t get me started on FEB-01.
I just fuckin’ hate Excel.
Fuck Excel’s CSV handing. It differs by locale, silently. Imagine the thousands of people every year who patiently wait to import a multi-megabyte CSV from some instrument only to see garbage because their language uses the decimal comma and semicolon separator.
I think semicolon separated files should be named SSV