ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Geert Dobbels <dobbels.geert@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: xtable headers and handlecsv loop
Date: Fri, 3 Apr 2020 15:16:19 +0200	[thread overview]
Message-ID: <80a76f26-d10c-ce56-9f25-5a2c7d78e87f@gmail.com> (raw)
In-Reply-To: <f8b65adc-4ca4-6e29-02ee-f3dbb36bc2c7@gmx.es>

Pablo,

Gracias, your suggestion with \rownums works.  I will try this one too,
since it is a simpler solution.  By the way, All information I have
about handlecsv comes from the PDF file you wrote.  \rownums and \lineno
are not explained in this document.  Do you know of documentation that
describes those aspects ?

Geert


On 03/04/2020 13:34, Pablo Rodriguez wrote:
> On 4/3/20 12:31 PM, Pablo Rodriguez wrote:
>> On 4/3/20 11:57 AM, Geert Dobbels wrote:
>>> [...]
>>> So in my second \doloopfromto I give the second argument a number
>>> high enough to be sure it reads all the lines. It works fine, but I
>>> would like to know if there is a way to read the number of lines in
>>> the csv file to use the exact number of lines, instead of guessing.
>> If \numrows doesn’t fit your needs, please provide a CSV file with fake
>> data. I cannot guess why a second loop might be required.
> Hi Geert,
>
> this approach is simpler:
>
>     \starttext
>     \startxtable
>     \startxtablehead[head]
>     \doloopif{\lineno}{<}{2}{\getbuffer[loop]}
>     \stopxtablehead
>     \startxtablebody
>     \doloopif{\lineno}{>}{1}{\getbuffer[loop]}
>     \stopxtablebody
>     \stopxtable
>     \stoptext
>
> Only loop header with CSV lines numbered below 2, and loop boody with
> CSV lines numbered above 1.
>
> Pablo
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-04-03 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  9:57 Geert Dobbels
2020-04-03 10:18 ` Wolfgang Schuster
2020-04-03 13:36   ` Geert Dobbels
2020-04-03 10:31 ` Pablo Rodriguez
2020-04-03 11:34   ` Pablo Rodriguez
2020-04-03 13:16     ` Geert Dobbels [this message]
2020-04-03 13:53       ` Pablo Rodriguez

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=80a76f26-d10c-ce56-9f25-5a2c7d78e87f@gmail.com \
    --to=dobbels.geert@googlemail.com \
    --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).