Posts Tagged ‘carriage return’
December 6, 2010 5 comments
I ran into this at work a few weeks ago and thought I’d share.
Excel 2008’s CSV export feature is broken. For instance, enter the following fake data into Excel:
Save as -> CSV file
When you use standard unix commands to view the output, the results are all garbled.
[Documents]$ cat Workbook1.csv 1,Bill,48[Documents]$ $ wc -l Workbook1.csv 0 Workbook1.csv
What is the issue? The file command reveals the problem:
$ file Workbook1.csv Workbook1.csv: ASCII text, with CR line terminators
CR stands for Carriage return, the ‘\r’ control sequence which, along with the newline character (‘\n’), is used to break up lines on Windows. Unix OSes like Mac OS expect a single ‘\n’ new line character to terminate lines.
How can we fix this?
# convert the Workbook1.csv file into a Unix appropriate file dos2unix Workbook1.csv WithUnixLineEndings.csv
If you don’t have dos2unix on your Mac, and you don’t want to install it, you can fake it with the tr command:
tr '\15' '\n' < Workbook1.csv # remove the carriage returns, replace with a newline Row,Name,Age 0,Nick,23 1,Bill,48
Very annoying that the Mac Excel doesn’t respect Unix line terminators. Interestingly, I found a post that talks about ensuring that you choose a CSV file encoded for Mac, but that option seems missing from the Mac version itself.
If I’m missing something obvious, please correct me.