CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.
Excel mangles everthing…
I work with a lot of EANs and every CSV import into Excel means I have to pay extra attention to the EAN field, because Excel likes to think for me, and thinks that the scientific notation would be very helpful for me… It’s not! 8.72E+12 is useless to me, Excel!!!
And don’t get me started on FEB-01.
You would be surprised how many people are simply splitting the string on commas instead of using an actual ascii parser. Especially for one off scripts, like churning through a csv full of passwords.
CSV has standard escape sequences. This is pointless
See RFC-4180:
https://datatracker.ietf.org/doc/html/rfc4180
CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.
Excel mangles everthing…
I work with a lot of EANs and every CSV import into Excel means I have to pay extra attention to the EAN field, because Excel likes to think for me, and thinks that the scientific notation would be very helpful for me… It’s not! 8.72E+12 is useless to me, Excel!!!
And don’t get me started on FEB-01.
I just fuckin’ hate Excel.
That standard won’t stop me because I can’t read!
deleted by creator
There was terrible code to long before LLMs, where do you think they got theirs from?
deleted by creator
You would be surprised how many people are simply splitting the string on commas instead of using an actual ascii parser. Especially for one off scripts, like churning through a csv full of passwords.
Then add escape sequence to your password!
Might as well just make a working regex and call it a password