JackbyDev to ProgrammingEnglish · 7 months agoTIL that RFC 4180 specifies the CSV format to use CRLF line endingsdatatracker.ietf.orgexternal-linkmessage-square8linkfedilinkarrow-up152arrow-down10file-text
arrow-up152arrow-down1external-linkTIL that RFC 4180 specifies the CSV format to use CRLF line endingsdatatracker.ietf.orgJackbyDev to ProgrammingEnglish · 7 months agomessage-square8linkfedilinkfile-text
I noticed a repository’s .gitattributes entry for *.csv used text eol=crlf so I investigated and found this.
minus-squareverstralinkfedilinkarrow-up9·7 months agoI hate that the pleasant news about standardization of CSV come with the let-down that is using two bytes for new lines.
minus-squareFizzyOrangelinkfedilinkarrow-up9·7 months agoDon’t worry, it’s not really standardised despite this attempt. You can use UNIX line endings and nothing bad will happen.
minus-squareKissakilinkfedilinkEnglisharrow-up8·7 months agoUnless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…
minus-squareulternolinkfedilinkEnglisharrow-up0·7 months 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.
minus-squareJackbyDevOPlinkfedilinkEnglisharrow-up1·7 months agoIt’s not pleasant news, just interesting news.
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.
It’s not pleasant news, just interesting news.