On Oct 25, 3:31 am, Joel wrote:
One possible reason for your problem could be the way the different operating
system handles the carriage returns and line feed. The macro below fixes the
carriage returns and linefeed so the file so it is compatable with Windows.
Modify the Path and input and output file names as needed.


This is not a CR-LF vs. LF issue. It is an encoding issue. Excel does
not (as far as I can see) give the option of opening a CSV file in the
standard UTF-8 encoding for Unicode. It has no trouble finding the
ends of lines and separating the lines into columns according to the
commas. It simply misinterprets all non-ASCII UTF-8 characters. The
result is a spreadsheet with all the numerical data correct, but all
the textual data corrupted.

But thanks.

[...]

(In any case, OS X *is* a Unix operating system, and my source files
come from another flavor of Unix. So this wouldn't be an issue.)