3 ms·
I've been using an emoji separated values format for a personal project where fields contain lots of special characters including whitespace. I'd previously gi
by jbaber 3y ago
I've been using an emoji separated values format for a personal project where fields contain lots of special characters including whitespace.
I'd previously given up using ASV because of the printability and copy/paste problems described. Replacing the control characters by their printable glyphs solves all my previous problems and is as genius as it is naughty.
I sympathize with the arguments people here present against and agree the SYN character and Group Separator are weird -- but cause no harm. I'm not bothered by the same data having multiple representations since I'm insisting on human readability rather than byte-by-byte perfection in the first place.
It took 20 minutes to convert my project and I'm very happy.
Only tooling change I had to make was adding digraphs to vim
digraph rs 9246 us 9247
etc. Easy to type directly in my .usv file. Easy to type and read in some Python consuming it.
Regardless of it becoming a standard and my lingering grouchiness about multi-byte characters, needing to use non-xterm, etc. this works very well for me.
- jph 3y agoGood points. I dropped SYN now because of feedback here. Thanks for the digraph vi info. Thanks to you, I added a vi-specific page in the repo for your tip.