JackbyDev@programming.dev to Programming@programming.devEnglish · 3 days agoTIL that RFC 4180 specifies the CSV format to use CRLF line endingsdatatracker.ietf.orgexternal-linkmessage-square7fedilinkarrow-up118arrow-down10file-text
arrow-up118arrow-down1external-linkTIL that RFC 4180 specifies the CSV format to use CRLF line endingsdatatracker.ietf.orgJackbyDev@programming.dev to Programming@programming.devEnglish · 3 days agomessage-square7fedilinkfile-text
I noticed a repository’s .gitattributes entry for *.csv used text eol=crlf so I investigated and found this.
minus-squareverstra@programming.devlinkfedilinkarrow-up4·2 days agoI hate that the pleasant news about standardization of CSV come with the let-down that is using two bytes for new lines.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up2·2 days agoDon’t worry, it’s not really standardised despite this attempt. You can use UNIX line endings and nothing bad will happen.
minus-squareKissaki@programming.devlinkfedilinkEnglisharrow-up6·1 day agoUnless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up0·17 hours agoIf I am using Excel, I am using Windows and I will be changing all text to use CR-LF newline format (if sending from a Linux system) anyway.
I hate that the pleasant news about standardization of CSV come with the let-down that is using two bytes for new lines.
Don’t worry, it’s not really standardised despite this attempt. You can use UNIX line endings and nothing bad will happen.
Unless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…
If I am using Excel, I am using Windows and I will be changing all text to use CR-LF newline format (if sending from a Linux system) anyway.