From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: ntg-context@ntg.nl
Subject: Re: CSV scanners built in ConTeXt - feature or bug?
Date: Thu, 26 Feb 2015 14:26:22 +0100 [thread overview]
Message-ID: <54EF1EFE.8020908@gyza.cz> (raw)
In-Reply-To: <20150226122000.7ebc5153@iram-ha-003840.extra.cea.fr>
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 now (ie
personally I'd rather vote strict=true would mean process all lines of
CSV file and strict=false mean stop processing on blank line), but I
will take into account whatever alternative and consequently I would
take into account this options for my own library.
Alan writes about this behavior as like metapost feature. Personally, I
think that the CSV file is basically a plain text file and a blank line
in it has its place. The end of the text file is usually marked by <eof>
character, so I guess there's no reason to terminate processing before
the file really ends.
Jaroslav Hajtmar
Dne 26.2.2015 v 12:20 Alan BRASLAU napsal(a):
> On Thu, 26 Feb 2015 10:47:29 +0100
> Hans Hagen <pragma@wxs.nl> 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 be expected for CSV, but
> MP thus allows one to pick-off sets of data by successive reads to one
> file.
>
> Alan
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-02-26 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 0:40 Jaroslav Hajtmar
2015-02-26 9:47 ` Hans Hagen
2015-02-26 11:20 ` Alan BRASLAU
2015-02-26 13:26 ` Jaroslav Hajtmar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54EF1EFE.8020908@gyza.cz \
--to=hajtmar@gyza.cz \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).