ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Xan <dxpublica@telefonica.net>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TABLE in TABLE
Date: Sun, 09 May 2010 15:01:42 +0200	[thread overview]
Message-ID: <4BE6B236.9070304@telefonica.net> (raw)
In-Reply-To: <4BE6B0A1.3090906@googlemail.com>

Thanks for the technical and simple explanation

Xan.

En/na Wolfgang Schuster ha escrit:
> Am 09.05.10 14:37, schrieb Xan:
>> Thanks all of you.
>> In other kind of ideas: is it a bug? Why we need {} for embed tables 
>> and not for embed itemizes in itemizes for example?
>
> It has to do with the way how TABLE is implemented, each cell is 
> defined as
>
> \def\bTD#1\eTD{...}
>
> this means when TeX sees a \bTD in the input it grabs everything till 
> the \eTD,
> let's take a loo at this example
>
> \bTABLE \bTR
>     \bTD
>       \bTABLE \bTR
>         \bTD text \eTD
>       \eTR \eTABLE
>     \eTD
> \eTR \eTABLE
>
> The \bTD from the outer table reads everything till the \eTD from the 
> inner table
> and what ends up as real content for the table cell where you wanted 
> another table is
>
> \bTABLE \bTR
>   \bTD text
>
> As you can see the \bTD as delimiting \eTD to end the cell and this is 
> what
> cause the error message you get. The braces ({...}) as suggested from 
> the others
> help in this case because the hide the \eTD from the outer table and 
> buffers
> as suggested from Taco are another way to get around this.
>
> Wolfgang
>

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-05-09 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09 11:42 Xan
2010-05-09 12:01 ` Taco Hoekwater
2010-05-09 12:03 ` Peter Münster
2010-05-09 12:37 ` Xan
2010-05-09 12:54   ` Wolfgang Schuster
2010-05-09 13:01     ` Xan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-10 18:31 Peter Münster
2006-04-10 20:31 ` Hans Hagen
2006-04-10 20:48   ` Peter Münster
2006-04-10 20:54     ` Hans Hagen

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=4BE6B236.9070304@telefonica.net \
    --to=dxpublica@telefonica.net \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@googlemail.com \
    /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).