3 ms·
> In hindsight, semicolons are the better choice, given that commas are common in many languages as decimal separators. Or a pipe. Or the unprintable “field s
by mulmen 6y ago
> In hindsight, semicolons are the better choice, given that commas are common in many languages as decimal separators.
Or a pipe. Or the unprintable “field separator” character.
> I don't know where there's never been some effort to create a "CSV format specification"; for example the first line could indicate quoting, delimiter, etc. style used in the file.
Fundamentally CSV or any delimited format requires agreement between parties for interchange. At that point standards don’t really help because the parties can just agree to anything that works.
> Guess it's never been big enough of a problem for people to take action. "Good enough" (or rather, "not bad enough").
Exactly.
- mavhc 6y agoIt's very annoying that ascii includes file and record separator characters and csv still exists
- dspillett 6y agoThe problem there is those code-points are usually non-printable, making the resulting file less human-readable which is often a stated desire for a data transfer file format. Some text editors will show those code points, but others will completely omit them (or worse, reject them as invalid).
- mavhc 6y agoIf they were something people used then editors would support them
- necovek 6y agoHow do you type those in modern text editors? You used to be able to ctrl + letter to input control keys on traditional terminals — was it (ord(char) - 0x20), but outside Emacs, vi and similar editors, I am sure you can't do that anymore. If you are questioning existence of human-readable/writeable (typeable?) data formats, you might want to check out SGML/XML, JSON, YAML... Are you surprised that being able to type it out holds true for all of these? Esp on standard keyboards? It's more interesting how SGML-derived languages have kept <> symbols so accessible on keyboards regular people use.