5 ms·

ASCII Code 29: Group Separator ASCII Code 30: Record Separator ASCII Code 31: Unit Separator https://theasciicode.com.ar/ascii-control-characters/record-sepa

ASCII Code 29: Group Separator ASCII Code 30: Record Separator ASCII Code 31: Unit Separator https://theasciicode.com.ar/ascii-control-characters/record-separator-ascii-code-30.html https://theasciicode.com.ar/ascii-control-characters/record-...

srik 4y ago
Thank you for pointing them out. I've browsed, and searched through that ascii table countless times, usually looking for something in particular, yet never realized that there were such a thing as separators before.
kbouck 4y ago
this doesn't directly address the ease-of-editing concern, but if you have csv (or tsv) and want ascii (0x1f, 0x1e) or unicode(U+241F, U+241E) separated (or vice versa), 'miller' [0] is a command line tool that supports converting among these formats with these one-liners: mlr --icsv --oasv cat input.csv # csv to asv mlr --iasv --ocsv cat input.asv # asv to csv [0] https://miller.readthedocs.io/en/latest/ https://miller.readthedocs.io/en/latest/ [1] https://miller.readthedocs.io/en/latest/file-formats/#csvtsvasvusvetc https://miller.readthedocs.io/en/latest/file-formats/#csvtsv...
- jph 4y ago
  You're right, Miller is great for this, and it turns out that Miller already offers Unicode Separated Values (USV).
cestith 4y ago
It makes more sense to me in these days of ubiquitous encoding of in-band data that it would be easier to edit if we just used tabs and newlines. If you need a tab in your data, the standard could support either \t (requiring \\t if you need a literal backslash followed by a literal 't') or %09 or &09; or \x09 or something.
- account42 4y ago
  If you require escaping then you may as well stick with csv - better to have the character that needs to be escaped to be common enough that people will run into it during testing.
  - cestith 4y ago
    My actual preference is LTSV. Then all that needs escaping or encoding is a quote since a tab or newline inside the quotes is different from one outside the quotes. And I prefer encoding to escaping generally, since it's easier for someone else to come along and build a fairly naive parser.

srik 4y ago

Thank you for pointing them out. I've browsed, and searched through that ascii table countless times, usually looking for something in particular, yet never realized that there were such a thing as separators before.

kbouck 4y ago

this doesn't directly address the ease-of-editing concern, but if you have csv (or tsv) and want ascii (0x1f, 0x1e) or unicode(U+241F, U+241E) separated (or vice versa), 'miller' [0] is a command line tool that supports converting among these formats with these one-liners: mlr --icsv --oasv cat input.csv # csv to asv mlr --iasv --ocsv cat input.asv # asv to csv [0] https://miller.readthedocs.io/en/latest/ https://miller.readthedocs.io/en/latest/ [1] https://miller.readthedocs.io/en/latest/file-formats/#csvtsvasvusvetc https://miller.readthedocs.io/en/latest/file-formats/#csvtsv...

jph 4y ago
You're right, Miller is great for this, and it turns out that Miller already offers Unicode Separated Values (USV).

cestith 4y ago

It makes more sense to me in these days of ubiquitous encoding of in-band data that it would be easier to edit if we just used tabs and newlines. If you need a tab in your data, the standard could support either \t (requiring \\t if you need a literal backslash followed by a literal 't') or %09 or &09; or \x09 or something.

account42 4y ago
If you require escaping then you may as well stick with csv - better to have the character that needs to be escaped to be common enough that people will run into it during testing.
- cestith 4y ago
  My actual preference is LTSV. Then all that needs escaping or encoding is a quote since a tab or newline inside the quotes is different from one outside the quotes. And I prefer encoding to escaping generally, since it's easier for someone else to come along and build a fairly naive parser.