Re: [NTG-context] CSV scanners built in ConTeXt - feature or bug?

2015-02-26 Thread Jaroslav Hajtmar
Hans and Alan, Thanks for the reply. Now it works properly. I would like to ask if you're planning to fix file util-prs.lua in a future release of standalone ConTeXt. As for me, I'd rather vote for as the default option other option, ie which does not stop on a blank line ie. not how it's setup

Re: [NTG-context] CSV scanners built in ConTeXt - feature or bug?

2015-02-26 Thread Alan BRASLAU
On Thu, 26 Feb 2015 10:47:29 +0100 Hans Hagen wrote: > i'm not sure about the default as the standard might demand quit at > empty line so that needs to be figured out (not by me therefore by > you) Stop on empty line is a very MetaPost-like feature. I don't have an opinion as to what should b

Re: [NTG-context] CSV scanners built in ConTeXt - feature or bug?

2015-02-26 Thread Hans Hagen
On 2/26/2015 1:40 AM, Jaroslav Hajtmar wrote: \starttext \startluacode local mycsvsplitter = utilities.parsers.rfc4180splitter{ separator = ",", quote = '"', } local crap = io.loaddata("data.txt") -- with header variant local tablerows, columnname = mycsvsplitter(crap,true) inspect(t

[NTG-context] CSV scanners built in ConTeXt - feature or bug?

2015-02-25 Thread Jaroslav Hajtmar
Hi ConTeXist A few days ago Hans pointed me builtin CSV splitter. I tried to test it sure will come in handy for my needs. I found that if the CSV file contain a blank line, then it stops processing the file (see my minimal example). It is clear to me that the incorrectness of file format (eg.