3 ms·
Though I'm not familiar with the CSV export of those two tools, I've had adventures in CSV parsing from other tools. How do they screw it up? Is there a canon
by jasonjayr 8y ago
Though I'm not familiar with the CSV export of those two tools, I've had adventures in CSV parsing from other tools. How do they screw it up? Is there a canonical "correct" way defined somewhere?
- sbuttgereit 8y agoI wonder what percentage of CSV represented data 1) passes through a spreadsheet at some point from data source to final data consumption and 2) how much of that spreadsheet action is specifically MS Excel. You're right, there is no standard that I'm aware of, though the answer to those first two questions could well be a proxy for a de facto standard in practice.
- dariusj18 8y agoI cannot remember exactly how they each screw it up, but the issues I have had are, but not limited to, a) truncation of data b) removal of line breaks c) not escaping enclosing values, ex. " as "" d) using \n or other values in place of actual line breaks or tabs e) using \N for NULL values (which isn't too bad, but it would be nice to be able to configure this) f) in general not complying with https://tools.ietf.org/html/rfc4180 https://tools.ietf.org/html/rfc4180
- sabas_ge 8y agoNo 'standard' but you could check and use the FrictionlessData specifications from OKFN (https://frictionlessdata.io/specs/csv-dialect/ https://frictionlessdata.io/specs/csv-dialect/)