Programming

21332 readers

243 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

TIL that RFC 4180 specifies the CSV format to use CRLF line endings (datatracker.ietf.org)

submitted 2 days ago by JackbyDev@programming.dev to c/programming@programming.dev

7 comments fedilink hide all child comments

I noticed a repository's .gitattributes entry for *.csv used text eol=crlf so I investigated and found this.

you are viewing a single comment's thread
view the rest of the comments

[–] verstra@programming.dev 4 points 2 days ago (3 children)

I hate that the pleasant news about standardization of CSV come with the let-down that is using two bytes for new lines.

[–] FizzyOrange@programming.dev 2 points 2 days ago (1 children)

Don't worry, it's not really standardised despite this attempt. You can use UNIX line endings and nothing bad will happen.

[–] Kissaki@programming.dev 6 points 1 day ago (1 children)

Unless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…

[–] ulterno@programming.dev 0 points 20 hours ago

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.

load more comments (1 replies)