No, what OP is talking about is the fact that Excel formats and parses CSV files differently depending on locale settings. For example, here in mainland Europe, Excel thinks CSV files should look like this:
ColA;ColB;ColC
1,618;2,718;3,14159
And in fact, to open an "American" CSV file in Excel you either have to set Windows to American locale settings, or use the text import wizard or the "text to columns" feature. If you don't use the correct settings, Excel will not complain, but corrupt the data (sometimes subtly).
I hope you agree that it is INSANE to make a file format depend on locale settings. As someone who writes software for scientists in Europe it leads to endless confusion and annoyance.
(And even if you do everything correctly, Excel will still mangle certain CSV files, interpreting phone numbers as dates etc...)
I hope you agree that it is INSANE to make a file format depend on locale settings. As someone who writes software for scientists in Europe it leads to endless confusion and annoyance.
(And even if you do everything correctly, Excel will still mangle certain CSV files, interpreting phone numbers as dates etc...)