From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: TABLE problems
Date: Sat, 21 Jul 2007 18:24:51 +0200 [thread overview]
Message-ID: <20070721182451.e69ce0fb.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <46A15F1C.10308.81F982@wwl.musensturm.de>
On Sat, 21 Jul 2007 01:19:24 +0200
"Wolfgang Werners-Lucchini" <wwl@musensturm.de> wrote:
> Hallo,
>
> I have two problems/questions with the following tables:
>
> 1. Should'nt all the columns be .2\textwidth, as in the last table?
> 2. Why expands column width to \textwidth in the second table?
> Has to do with \type{} and/or color!
> 3. Why behaves table 1 (with \type{}) as table 3 (whitout \type{})?
> Wolfgang
Hi Wolfgang,
sorry, no to your questions but the following setup works:
\setupTABLE[row][odd][background=color,backgroundcolor=lightgray]
\setupTABLE[width=.2\textwidth]
why do you repeat the setup command for every table, the first one is
global and should work for every table in your document, unless you
make a setup local within a group or a float.
Wolfgang
> \setupcolors[state=start]
> \starttext
> \input tufte
>
> \setupTABLE[row][odd][background=color,backgroundcolor=lightgray,
> width=.2\textwidth]
> \bTABLE
> \bTR \bTD \type{short} \eTD \bTD reads the whole file \eTD \eTR
> \bTR \bTD kurz \eTD \bTD reads a string with up to num characters
> \eTD \eTR
> \eTABLE
>
> \input tufte
>
> \setupTABLE[row][odd][background=color,backgroundcolor=lightgray,
> width=.2\textwidth]
> \bTABLE
> \bTR \bTD short \eTD \bTD reads the whole file \eTD \eTR
> \bTR \bTD \type{kurz} \eTD \bTD reads a string with up to num
> characters \eTD \eTR
> \eTABLE
>
> \input tufte
>
> \setupTABLE[row][odd][background=color,backgroundcolor=lightgray,
> width=.2\textwidth]
> \bTABLE
> \bTR \bTD short \eTD \bTD reads the whole file \eTD \eTR
> \bTR \bTD kurz \eTD \bTD reads a string with up to num characters
> \eTD \eTR
> \eTABLE
>
> \input tufte
>
> \setupTABLE[row][odd][background=color,backgroundcolor=lightgray,
> width=.2\textwidth]
> \bTABLE
> \bTR \bTD kurz \eTD \bTD reads a string with up to num characters
> \eTD \eTR
> \eTABLE
>
> \input tufte
> \stoptext
>
>
> ___________________________________________________________________________________
> 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 : https://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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-07-21 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 23:19 Wolfgang Werners-Lucchini
2007-07-21 16:24 ` Wolfgang Schuster [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=20070721182451.e69ce0fb.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@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).