Frictionless Data: Lightweight standards and tooling for data sharing

Re:Frictionless Data: Lightweight standards and tooling for ... by slowmotiony on Wednesday September 27, 2017 @07:12AM (#15346609)

I hate csv so much. Simply opening a csv in Excel and saving it breaks the format so much that most parsers cannot understand it anymore. Plus there is no way to know which encoding the csv came in - Notepad++ might say one thing and PowerShell will say another. Have fun figuring out why cyrrilic characters or umlauts cause issues in your scripts...

[ Parent | on HN ]

Re:Frictionless Data: Lightweight standards and tooling for ... by jarman on Wednesday September 27, 2017 @07:48AM (#15346806)

Problem is not CSV, it's Excel. It's hard to blame format, when application is insane enough to use locale settings to determine file parsing

[ Parent | on HN ]

Re:Frictionless Data: Lightweight standards and tooling for ... by carlps on Wednesday September 27, 2017 @07:37AM (#15346745)

I think the excel issue is a problem with excel, not csv. Why can't excel preserve the format of the file?

[ Parent | on HN ]

Re:Frictionless Data: Lightweight standards and tooling for ... by jarman on Wednesday September 27, 2017 @07:50AM (#15346821)

>why cyrrilic characters or umlauts cause issues in your scripts...

Any text format can be broken by broken character encoding. I saw plenty of XML being used without any charset declarations. And JSON is in same position as CSV.

[ Parent | on HN ]