On 3/23/2026 1:05 AM, Bruce Horrocks wrote:
On 22 Mar 2026, at 18:11, luigi scarso <[email protected]> wrote:
While other "acronyms" seem reasonable, in
JSON, XML und CSV als Datenformate,
CSV should be deprecated. I understand that many use CSV and that, if
implemented correctly, it doesn't cause problems,
but it's precisely the "correct" implementation that has become difficult to
find.
CSV is a standard - RFC4180 - and therefore should not be deprecated.
I would propose the ucsv format, Unicode Controls Separated Values,
where fields are separated by 001F (insteead of ',') and records by 001E
(instead of newline)
or alternatively 241F and 241E. These characters should not appear in the text,
to make the parser very simple.
The CSV standard is a truly awful one in that it encodes common and historical
practice rather than starting with a clean set of requirements, so I'm definitely
in favour of *adding* ASCII/Unicode 21-31 (FS, GS, RS & US) as a separately
supported type.
and
0x2 : START OF TEXT
0x3 : END OF TEXT
instead of quotes (which we happen to support in luametatex's mplib
variant so that embedded quotes and newlines work fine)
$ sqlite3 -header -csv my_db.db "select * from my_table;" > out.csv
hm, i need to test that
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : [email protected] /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
