Re: Deutschland-Stack
Bruce Horrocks <[email protected]>
| Newsgroups | gmane.comp.tex.context |
|---|---|
| Message-ID | <[email protected]> |
> 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. > (Even better would be Sqlite As An Application File Format > https://www.sqlite.org/appfileformat.html > but that's just my opinion.) It's easy enough to convert sqlite to CSV on the command line: $ sqlite3 -header -csv my_db.db "select * from my_table;" > out.csv so you can use that in the interim. You can always use a Makefile to keep the .csv files updated. Regards, — Bruce Horrocks Hampshire, UK ___________________________________________________________________________________ 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 ___________________________________________________________________________________