News for hackers. Stuff that matters.
Re:Microsoft Excel’s 35th birthday by ndespres on Friday October 02, 2020 @11:14AM (#24663478)
I have long suspected that Excel's treatment of CSV files was intentionally antagonistic. For example, opening a CSV file will start an importer function where you must specify how fields are delimited within the file, and "comma" is not automatically selected, ever, despite "comma-separated" being literally named in the file extension.

Surely the folks programming it are not that short-sighted. It's just a punishment for not using their default format.

Re:Microsoft Excel’s 35th birthday by kalleboo on Friday October 02, 2020 @08:33PM (#24668442)
It also has really broken handling of text encodings.

I've taken to importing CSV files using Apple Numbers, and saving as Excel

(i use Numbers primarily, Excel is just when I need to be interoperable with someone else)

Re:Microsoft Excel’s 35th birthday by rightbyte on Friday October 02, 2020 @12:58PM (#24664581)
Well I would give Excel some cred for acctually following local number conventions. It the beginning there was no internet and interoperability issue.

Usually it is the us-en way or the highway.