3 ms·
You can disallow those metacharacters in the data proper. Then you have a format that can store any utf8 or whatever except the non-whitespace control codes wit
by chrishill89 2y ago
You can disallow those metacharacters in the data proper. Then you have a format that can store any utf8 or whatever except the non-whitespace control codes without any escaping. That solves a problem in an opinionated way. Just like how json is opinionated (utf8 only).
You can convert to another format if you need something crazier than rows and columns consisting of normal text.
- chubot 2y agoThat already exists -- TSV. You disallow the tab metacharacter.
- thayne 2y agoAnd the newline character. Both of which commonly occur in normal text.
- chrishill89 2y agoThen I don't understand. Like the sibling comment said the really "problematic" character in TSV is the line feed. But a tab can occur as well. The format that I described does not already exist in the form of TSV. And further based on your original comment I would have thought that both TSV and this format would be discarded as not-useful.