From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Interfering frames in natural tables
Date: Tue, 22 May 2012 14:00:01 +0200 [thread overview]
Message-ID: <1160222B-37F2-4BB9-B395-3DE08D99763A@googlemail.com> (raw)
In-Reply-To: <20120522131757.1556b56d@Zewz>
Am 22.05.2012 um 13:17 schrieb Marco:
> Hi,
>
> the frames are interfering in the following example. How to avoid
> the 2pt-2-column bottom rule also be drawn at the top?
>
> \startsetups table
> \setupTABLE [frame=off]
> \setupTABLE [row] [first] [topframe=on]
> \setupTABLE [1] [first] [bottomframe=on, rulethickness=2pt]
> \stopsetups
\setupTABLE [row] [first] [topframe=on]
\setupTABLE [1,2] [2] [topframe=on,rulethickness=2pt]
> \starttext
> \bTABLE [setups=table]
> \bTR\bTD[nc=2] Lorem \eTD\eTR
> \bTR\bTD Ipsum \eTD\bTD Dolor \eTD\bTD Sit \eTD\eTR
> \bTR\bTD aaaaaa \eTD\bTD bbbbbbbb \eTD\bTD ccccccc \eTD\eTR
> \bTR\bTD dddd \eTD\bTD eeeeeeee \eTD\bTD fffff \eTD\eTR
> \eTABLE
> \stoptext
>
>
> Side question: Is it safe not to use setups and shorten the example?
Yes, the setups key was added only to separate the table settings from the content.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-22 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 11:17 Marco
2012-05-22 11:25 ` Marco
2012-05-22 11:37 ` Sander Maijers
2012-05-22 11:58 ` luigi scarso
2012-05-22 11:59 ` Marco
2012-05-22 12:00 ` Wolfgang Schuster [this message]
2012-05-22 12:15 ` Marco
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=1160222B-37F2-4BB9-B395-3DE08D99763A@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).