Am 22.03.26 um 19:11 schrieb luigi scarso:
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.
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.
(Even better would be Sqlite As An Application File Format
https://www.sqlite.org/appfileformat.html
but that's just my opinion.)
Binary formats are never a solution for simple requirements.
CSV is simple and doesn’t need special input methods for uncommon
characters.
It’s not about parsability / machine readability, but also about human
editability.
Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
