Mac end of lines

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Make a CSV file
2. Save it using Mac formatted ends of lines.
3. Load it up.

What is the expected output? What do you see instead?
I expect it to work. Everything works great when using windows or linux 
formatted CSV files. When using Mac files, I get CSVDataError: Illegal state 
[Row:1]. 

What version of the product are you using? On what operating system?
This library has always acted this way. I hadn't gotten around to filing this 
particular bug report yet. But I would like it fixed if possible, so that I 
don't have to make my users worry about end of line formatting. So even in 
0.71, this happens. 

Please provide any additional information below.

Maybe the weird mac formatting is not in the official spec for CSV, but it 
would be nice if we could use it anyways. Why create the extra work for my 
end-users? 

This test.csv will fail to load. This test2.csv is identical, except for it 
uses windows end of line formats. A good text editor doesn't show the 
difference. The actual difference is that Mac format doesn't use line feed 
characters, and this causes jquery-csv to fail. This also messes up 
Notepad.exe. 

Original issue reported on code.google.com by Chad.R.B...@gmail.com on 30 May 2013 at 1:06

Attachments:

• test.csv
• test2.csv

[GoogleCodeExporter]

Technically 'carriage return' line endings are no longer a valid form of line 
ending on any platform. Since the release of OSX mac line endings have followed 
the Unix convention (ie newline).

Excel for OSX is the only application I know of that still (incorrectly) 
explicitly uses CR line endings.

To keep the parser as simple and efficient as possible, it silently ignores all 
CR characters making both CRLF and LF characters read the same.

There are two approaches to fix this issue:

1. Run the CSV data through a pre-processor function that converts all CR/CRLF 
characters to LF characters.

2. Change the parser code to add special cases for both CRLF and CR line 
endings.

I strongly suggest the former. Hacking on the parser code is no simple matter. 
The lexer is written to be as slim and efficient as possible, adding more edge 
cases will slow down the parser for everything. You may see a lot of CSV with 
CR characters but in the greater scope of things, CSV with CR line endings is 
not a common occurrence.

If you'd like to contribute a patch, or need help working out a pre-processor 
I'll try to help. Due to personal/work circumstances I don't have the time to 
focus on further development right now.

Original comment by evanpla...@gmail.com on 31 May 2013 at 4:40

[GoogleCodeExporter]

I know you don't want to add this, but man I would totally donate beer money to 
get it working. Having to tell people to open their files in Excel just to 
save-as a different csv isn't a great user experience.

Is there any javascript out there that normalizes line endings in a csv?

Original comment by jpsi...@gmail.com on 4 Sep 2013 at 2:28

[GoogleCodeExporter]

Can we just use regular expressions or something to convert all CR to LF? 

Original comment by Chad.R.B...@gmail.com on 9 Sep 2013 at 10:33

[GoogleCodeExporter]

it would be awesome if this was just built in as a failsafe, i run in to this 
issue constantly

Original comment by jpsi...@gmail.com on 10 Sep 2013 at 4:26

[GoogleCodeExporter]

I was able to get the parser to work by treating the "^/r$" case as end of line 
in all 3 states of the parser. I don't know how this will affect non Unix/Excel 
exported case. 

Original comment by dan.bo...@gmail.com on 10 Sep 2013 at 8:18

[GoogleCodeExporter]

I would agree with the comment that "it would be awesome if it was just built 
in"  Since part of the idea of jQuery is corss-platform functionality it seems 
that it should be the library that handles it and not have to special case the 
use of the library.

Original comment by dan.bo...@gmail.com on 10 Sep 2013 at 8:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Here is a copy of the parser as I mentioned in comment #5

Original comment by dan.bo...@gmail.com on 10 Sep 2013 at 8:38

Attachments:

• jquery-csv.js

[GoogleCodeExporter]

Dan, what exactly did you change in this? whatever it is fixes my issue

Original comment by jpsi...@gmail.com on 10 Sep 2013 at 9:39

[GoogleCodeExporter]

wait nevermind, i spoke too soon.  this just switches it up, it works for the 
mac one but breaks the normal working ones

Original comment by jpsi...@gmail.com on 10 Sep 2013 at 9:41

[GoogleCodeExporter]

I only have the Mac Excel files, If you can send me a working case test file. 
Let me look at it.

Original comment by dan.bo...@gmail.com on 10 Sep 2013 at 9:47

[GoogleCodeExporter]

Attached is one that is totally messed up. It works fine if I open it in excel, 
save-as, and change the format to "windows comma separated (.csv)".   If I do 
that there are no issues with the parser.

Original comment by jpsi...@gmail.com on 10 Sep 2013 at 11:28

Attachments:

• openflash.csv