4 ms·

I don't get the no-escape rule...it should be possible to escape

• giraffe_lady 5y ago
  Why? Without escaping it's very simple to implement a parser or verifier for it. With escaping it has no real advantages over csv. The characters are pretty much just for this, when would you ever need to put them in the data? If you're working on tooling for unicode itself? Just use... any other format. Literally any.
• selfhoster11 5y ago
  In what world would you ever use a tabular format that contains Unicode escapes as a natural part of the content?
• jph 5y ago
  No-escape makes serialization and deserialization simpler, faster, and easier to test. For example, import/export is a breeze on the command line with typical Unix tools such as awk, sed, grep, mlr. No-escape makes international standardization clearer for Backus–Naur form (BNF), the same way other standards use no-escape BNF. For example, no-escape is the same choice as with the existing international standard for IANA tab separated values.
• 0x073 5y ago
  That's the problem of all CSV formats, wrong or custom implementations. Someone will generate wrong usv e.g. escape or encapsulate values. And if you get that wrong format no one cares if they gave you a wrong format. => Your parser grows and grows...