this post was submitted on 03 Nov 2025
        
      
      988 points (98.1% liked)
      memes
    17906 readers
  
      
      3065 users here now
      Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
 - !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
 - !linuxmemes@lemmy.world : Linux themed memes
 - !comicstrips@lemmy.world : for those who love comic stories.
 
        founded 2 years ago
      
      MODERATORS
      
    you are viewing a single comment's thread
view the rest of the comments
    view the rest of the comments
Correct me if I'm wrong, but doesn't text with commas in it get put in double quotes in acsv file to avoid this exact thing?
Like if I had cells (1A: this contains no comma), (2B: this, contains a comma), and (3C: end of line), the csv file would store (this contains no comma,"this, contains a comma",end of line)
A CSV is just a long string of text with a few control characters tossed in for end lines. There are practically no rules enforced by the file type itself. You can dump that unsanitized and poorly awk'd data into whatever awful mess you want. Nobody's stopping you. Sure, excel will force it's CSV formatting rules on you when you export like a child's training wheels. But that's not relevant here.
Yes and no. Like yes, that can be true. But a lot of tools don’t handle commas correctly no matter how you escape them.
Only if it's actually using a standard like rfc 4180 https://www.ietf.org/rfc/rfc4180.txt
Also just noticed it specifies CRLF as the line ending, not LF, which is kind of weird.
Also 4180 is not a standard (it says on the first page)