I think these problems can be mitigated if the CSV format is strictly defined,
such as how I specified it in my previous message.
In particular, the parser has to recognize only one specific header line that
has a version number somewhere, or abort - and I still insist on quoting the
labels wit
Having previously developed an export format[1] for general cryptocurrency
transaction information, I can attest to the value of the human-readable CSV. I
was careful to mention the RFC 4180 spec so that implementations could avoid
the pitfalls of incorrect CSV encoding.
[1]: https://github.com
