From: MASON Peter J <Peter_MASON@rta.nsw.gov.au>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: spreading natural tables across the page
Date: Tue, 10 Apr 2007 08:48:53 +1000 [thread overview]
Message-ID: <B46993C748ACD6438DDCD6BA16AA6595016BE786@centx302.corp.rta.nsw.gov.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2233 bytes --]
Thankyou, but I'm seeking a little more. This example gives columns of equal width. I need to be able to control width for each col, viz some I want tight fitting, others not. Seems that I can do this if I'm explicit about setting width= per column, but with Latex using "tabular*" I didn't need to set width explicitly for each col. Does this make sense? If so then howto?
-----Original Message-----
From: ntg-context-bounces@ntg.nl [mailto:ntg-context-bounces@ntg.nl]On Behalf Of Wolfgang Schuster
Sent: Thursday, 5 April 2007 4:16 PM
To: mailing list for ConTeXt users
Subject: Re: [NTG-context] spreading natural tables across the page
2007/4/5, MASON Peter J < Peter_MASON@rta.nsw.gov.au>:
I'm trying to have my tables extend across the full (\textwidth) of the page. In LaTeX I was using tabular*, specifying a \textwidth for width, and with approp use of @{\extracolsep\fill}} bu am not having any success. Basically, in ConteXT I want odd columns to act as labels and be tight fitting but even cols to be the values an NOT be tight-fitting, within a page-wide table, ie some tight, some not. As well, I' d like not to be explicitly specifying column width.
I saw examples using option=stretch somewhere but am not able to get my use of same happening. As well, I' d like not to be explicitly specifying column width. Could a kind person please point me to an example of this usage.
Thanks.
Hi Peter,
\starttext
\bTABLE[option=stretch]
\bTR
\bTD Left \eTD
\bTD Right \eTD
\eTR
\eTABLE
\stoptext
Wolfgang
IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it. Views expressed in this message are those of the individual sender, and are not necessarily the views of the RTA. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient.
[-- Attachment #1.2: Type: text/html, Size: 3414 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2007-04-09 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 22:48 MASON Peter J [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 1:41 MASON Peter J
2007-04-05 6:16 ` Wolfgang Schuster
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=B46993C748ACD6438DDCD6BA16AA6595016BE786@centx302.corp.rta.nsw.gov.au \
--to=peter_mason@rta.nsw.gov.au \
--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).