-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
most recent version of Microsoft Excel for Mac does export CSV files with "\r" as the line ending #77
Comments
This is very much not my area of expertise! haha |
For posterity, @cjyetman's comment warned of exactly this: #65 (review) |
@cjyetman When I try to run a CSV generated with excel (Attached Book1.csv), I get warnings, but it still returns a valid portfolio The warnings appear to be coming from the new logic in
it's the same "
|
I'm aware of the warning, but it's a small price to pay to maintain previous behavior, especially with an impending COP project, and fairly certain memory of having seen files like this in the wild. I'll open an issue to squelch the warning. |
On Microsoft Excel for Mac v16.81 (presumably the most recent version on my work laptop), when exporting a CSV using the "Macintosh Comma Separated (.csv)" option to export, it creates a file with only "\r" as the line ending (interestingly, in this particular case, it does not add any line ending or newline to the last line).
Similar behavior has been reported over the years (2013-2020)
https://nicercode.github.io/blog/2013-04-30-excel-and-line-endings/
https://answers.microsoft.com/en-us/msoffice/forum/all/excel-office-365-mac-not-saving-utf-8-csv-files/ba44fced-7da7-418c-b230-f24726b8ecf7
https://developmentality.wordpress.com/2010/12/06/excel-2008-for-macs-csv-bug/
Exporting from Excel in this way is something we have advised COP members to do in the recent past.
This suggests to me that getting CSV files that have a line ending with only "\r" at the end is a very real possibility.
Because of this, I think we need to revert #65 and part of #58.
@AlexAxthelm @jdhoffa
The text was updated successfully, but these errors were encountered: