From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Cc: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>, <ntg-context@ntg.nl>
Subject: Re: [ConTeXt] Footnoteproblems, bTABLE problems
Date: Thu, 3 Jan 2002 20:09:35 +0100 (CET) [thread overview]
Message-ID: <Pine.BSF.4.30.0201031615370.28125-100000@george.physik.fu-berlin.de> (raw)
In-Reply-To: <5.1.0.14.1.20020103130332.03d9e468@server-1>
Hi Hans,
> Hi impatient Tobias ...
;-) Well at the moment I'm really under pressure, but you seem to be under
pressure as well.
(Here the question was asked: LaTeX is still more stable, isn't it? And I
have the feeling that this is not completely wrong ...)
> i fixed that (aproximation btw); there are a few places in context where
> multiple passes over content are done, i such cases one can use
> \iftrialtypesetting to catch unwanted behavior. I kind of built it into
> TABLE now, so your case should work;
It does :-)
> >c) I use TABLE with nr and nc. nr works ok, but for nc the text cannot
> >extend the width of one cell (the border is usually drawn correctly)
>
> for that i need a minimal example (and time)
here comes one. By the way the time problem applies also to me ...
but I hope that I can work around that problem.
Tobias
Example:
--------------
\bTABLE
\bTR
\bTH foo \eTH
\bTH This is a very, very, very really long cell \eTH
\eTR
\bTR
\bTD[nc=2] This is also a very, very, very really long combined cell\eTD
\eTR
\eTABLE
\bye
----------------
The first column is very wide, but need to be if the text of the [nc=2]
cell would also be shown under the second column.
next prev parent reply other threads:[~2002-01-03 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.30.0201031144440.53705-100000@jerry.physik.fu-b erlin.de>
2002-01-03 12:11 ` Hans Hagen
2002-01-03 19:09 ` Tobias Burnus [this message]
[not found] ` <Pine.BSF.4.30.0201031615370.28125-100000@george.physik.fu- berlin.de>
2002-01-04 9:24 ` Hans Hagen
2002-01-03 10:51 Tobias Burnus
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=Pine.BSF.4.30.0201031615370.28125-100000@george.physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--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).