Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CSVs should be RFC4180 Compliant #35

Open
djbusby opened this issue Dec 15, 2021 · 2 comments
Open

CSVs should be RFC4180 Compliant #35

djbusby opened this issue Dec 15, 2021 · 2 comments
Labels
wontfix This will not be worked on

Comments

@djbusby
Copy link
Member

djbusby commented Dec 15, 2021

This was reported ages ago (at least Dec 1st, if not earlier)
The CSV files that the LCB accepts are not compliant with RFC4180
-- so this means, no quoted fields and no embedded commas in field values (and likely a host of other bugs)

https://datatracker.ietf.org/doc/html/rfc4180
Also, for notes: https://datatracker.ietf.org/doc/html/rfc7111
@djbusby
Copy link
Member Author

djbusby commented Dec 18, 2021

Adding onto this; previously many files were submitted using UNIX style line endings. Just recently that switched and now their system REQUIRES a CRLF (Windows) style line-ending.

We have looked at your files and found that all your line endings are not Microsoft Windows .CSV line endings (CRLF). When files are originated on a Unix based system, or the file is generated programmatically, the correct line endings may not have been specified correctly. Please save your files as a Windows .CSV file type, and resubmit your files.

@djbusby djbusby mentioned this issue Dec 29, 2021
Open
@djbusby djbusby added the wontfix This will not be worked on label Jul 25, 2022
@djbusby
Copy link
Member Author

djbusby commented Jul 25, 2022

The LCB will NOT fix this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@djbusby