• taiyang@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    4 months ago

    Oh boy, having done data science work with government files, you remind me that they still use terrible delimiters. A white space delimiter sounds significantly worse than a tab delimited file, though!

    • Reddfugee42@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      I never use tab delimiters but thinking about it, it is much less common to encounter a tab character in a CSV field than a comma…

      • taiyang@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        4 months ago

        Tabs are also usually not allowed in many fields. The thing is, tab delimiters are fine, but the data sets often get stored without file extensions. Let me tell ya, I was the only person on staff to even know what a file extension was, let alone how to load it into software that can process tab delimiters!

    • IphtashuFitz@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      4 months ago

      I learned COBOL programming on that system. COBOL’s sequential file data type was all about space-delimited text files. Part of a program would define the various input & output files. For example a numerical userid might take up columns 1-8 then the first initial would be in column 10 then the last name in columns 12-20 and so on…

    • dohpaz42@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      Tabs are considered white space. A white space is technically any character that is not visible. That covers things like spaces, vertical/horizontal tabs, non-breaking spaces, zero-length spaces, etc.