Bug #271
closedCSV Import Problems
0%
Description
I have figured out why some users (see Bug #125, entries 4 & 5) cannot load CSV files and obtain a "new-line character seen" error. It turns out that you are assuming a Windows CSV file, which terminates lines with a CR/LF (0x0D/0x0A) character pair. Linux and Mac OSX terminate lines with just a CR (0x0D) character. If you adjust your code to accept both line terminations, things should start working for all the O/Ss.
Files
Updated by Tom Hayward over 12 years ago
I can't reproduce this. I'm on OS X and files with both newline formats open without issue.
Updated by Chuck Burton over 12 years ago
- File Test1.csv Test1.csv added
- File Test2.csv Test2.csv added
- File Test2Error.jpg Test2Error.jpg added
I am running OS X 10.6.8 and Chirp20120730.app. Test1.csv loads in Chirp just fine, but Test2.csv provides the error (Test2Error.jpg).
Updated by Chuck Burton over 12 years ago
Oops, for got to tell you that Test1.csv has CR/LF terminating the lines. While Test2.csv is the same as Test1, but only has CR terminating the lines.
Updated by Tom Hayward over 12 years ago
- Status changed from New to In Progress
- Assignee set to Tom Hayward
- Target version set to 0.2.3
Oh, I guess I didn't read carefully enough. I tried Windows and Unix newlines (\r\n and \n). This is old Mac format (\r). We should be able to support it...
Updated by Tom Hayward over 12 years ago
Almost forgot to ask... which MRA group are you with? I am with http://larimercountysar.org
Updated by Chuck Burton over 12 years ago
I'm with Chaffee County North (most 14ers in the US).
Updated by Tom Hayward about 12 years ago
- Status changed from In Progress to Closed
Fixed last week.