In article ,   
   Hans Bezemer   wrote:   
   >A well behaved CSV is easy to parse. However, if there are quotes,   
   >delimiters or line terminators involved, it gets complicated quickly.   
   >   
   >TSV solves that problem. Now, what does it require to get supported in 4tH?   
   >   
   >https://youtu.be/2lZ72SD-eXg   
      
   If there is a generally accepted standard, one has no choice to abide by   
   that standard.   
   I can download my bank data in CSV but TSV is not an option.   
   So TSV is of limited use.   
      
   Problems handling strings is more to be blamed on the lack of   
   sensible wordsets. With my   
       $@ $! $+! $C+ $/ $\ $^   
   wordset, I experience few problems.   
      
   E.g. I consume a bank data file and generate a postscript file   
   with exactly the fields that I want, in the correct order.   
   (In a fraction of the time struggling with spreadsheets would cost.)   
      
   >   
   >Hans Bezemer   
   --   
   The Chinese government is satisfied with its military superiority over USA.   
   The next 5 year plan has as primary goal to advance life expectancy   
   over 80 years, like Western Europe.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)