From: "Martin Kolarík" <martin@mii.cz>
Subject: RE: problem with tables
Date: Wed, 12 Mar 2003 12:58:54 +0100 [thread overview]
Message-ID: <000001c2e88e$c10e5fe0$2197fac3@mii.cz> (raw)
In-Reply-To: <5.1.0.14.1.20030312124558.024a2220@server-1>
:-) yes, the autumn version allowed this :-)
I do not need grouping for this simple case, this is only an extracted
minimal example. The real situation occurs in relative complex table typeset
automatically from CSV -- CSV content is loaded, parsed, recomputed, stored
into some toks and reused/typeset more times. As I remember the grouping
causing error in my case is \startcolor[] \stopcolor.
Now I dig into problem and I'll send you more info (I forgot the cause :-)
Thanks,
Martin
> -----Original Message-----
> From: ntg-context-admin@ntg.nl [mailto:ntg-context-admin@ntg.nl]On
> Behalf Of Hans Hagen
> Sent: Wednesday, March 12, 2003 12:46 PM
> To: ntg-context@ntg.nl
> Subject: RE: [NTG-context] problem with tables
>
>
> At 12:37 PM 3/12/2003 +0100, you wrote:
> >Sure,
> >
> >but this? (I've added grouping, it must be present to get error)
> >
> >\setupTABLE[c][1][aligncharacter=yes]
> >
> >\bTABLE
> >\bTR \bTD \bgroup 123,0 \egroup \eTD \eTR
> >\bTR \bTD 13,0 \eTD \eTR
> >\bTR \bTD 3,0 \eTD \eTR
> >\eTABLE
>
> hm, why do you need the grouping? The string is parsed, so grouping like
> this will spoil thing s
>
> Hans
>
> -------------------------------------------------------------------------
> Hans Hagen | PRAGMA ADE | pragma@wxs.nl
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
> -------------------------------------------------------------------------
> information: http://www.pragma-ade.com/roadmap.pdf
> documentation: http://www.pragma-ade.com/showcase.pdf
> -------------------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2003-03-12 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 13:26 Martin Kolařík
2003-02-14 15:07 ` Hans Hagen
2003-02-17 9:10 ` Martin Kolarík
2003-03-01 8:37 ` Martin Kolařík
2003-03-11 23:43 ` Hans Hagen
2003-03-12 10:26 ` Martin Kolarík
2003-03-12 11:19 ` Hans Hagen
2003-03-12 11:37 ` Martin Kolarík
2003-03-12 11:46 ` Hans Hagen
2003-03-12 11:58 ` Martin Kolarík [this message]
2003-03-12 12:48 ` Hans Hagen
2003-03-12 12:30 ` Martin Kolarík
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 13:25 Martin Kolařík
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='000001c2e88e$c10e5fe0$2197fac3@mii.cz' \
--to=martin@mii.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).