From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Balancing vertical placement of table
Date: Sun, 31 Jan 2010 16:58:16 +0100 [thread overview]
Message-ID: <4B65A898.5020206@googlemail.com> (raw)
In-Reply-To: <4BC2AD5E-B70C-4A9E-ACAA-D262B73AFC10@enquora.com>
Am 31.01.10 16:50, schrieb Design Department:
>> Is the content for each element short enough to fit on one page
>> or do you have content which needs more pages?
>
> The content always fits on a single page.
Here is a goodie which is only documented in the ConTeXt source.
\setupheadertexts[the header text]
\setupfootertexts[a pretty long left footer text][something right]
\setupbottomtexts[a not so long bottom text][another right thing]
\setuptexttexts [margin][something marginal][indeed]
\startpagelayout[leftpage]
\setupTABLE[offset=overlay]
\setupTABLE[c][1][width=\leftmarginwidth]
\bTABLE
\bTR
\bTD[nx=3,background=color,backgroundcolor=green]
\pagearea[header][text][middle]
\eTD
\eTR
\bTR
\bTD \pagearea[text][margin][left] \eTD
\bTD[nx=2] \pagearea[text] \eTD
\eTR
\bTR
\bTD[nx=3,offset=overlay]
{\bTABLE[width=.5\hsize]
\bTR
\bTD \pagearea[footer][text][left] \eTD
\bTD \pagearea[bottom][text][left] \eTD
\eTR
\eTABLE}
\eTD
\eTR
\eTABLE
\stoppagelayout
\startpagelayout[rightpage]
\setupTABLE[offset=overlay]
\setupTABLE[c][1][width=\rightmarginwidth]
\bTABLE
\bTR
\bTD[nx=3] \pagearea[header][text][middle] \eTD
\eTR
\bTR
\bTD \pagearea[text][margin][left] \eTD
\bTD[nx=2] \pagearea[text] \eTD
\eTR
\bTR
\bTD[nx=3,offset=overlay]
{\bTABLE[width=.5\hsize]
\bTR
\bTD \pagearea[bottom][text][right] \eTD
\bTD \pagearea[footer][text][right] \eTD
\eTR
\eTABLE}
\eTD
\eTR
\eTABLE
\stoppagelayout
\setupcolors[state=start]
\setupbackgrounds[text][background=color,backgroundcolor=blue]
\setupbackgrounds[header][text][background=color,backgroundcolor=red]
\setuppagenumbering[alternative=doublesided,location=]
\setuplayout[method=makeup]
\definetextbackground
[test]
[state=start,
background=color,
backgroundcolor=yellow]
\starttext
\dorecurse{10}{\input tufte \par}
\input tufte \starttest \input tufte \stoptest \input tufte
\starttabulate
\NC test \NC \starttest \input tufte \stoptest \NC \NR
\stoptabulate
\dorecurse{10}{\input tufte \par}
\stoptext
Regards,
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:[~2010-01-31 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 4:29 Design Department
2010-01-31 13:31 ` Wolfgang Schuster
2010-01-31 15:50 ` Design Department
2010-01-31 15:58 ` Wolfgang Schuster [this message]
2010-01-31 16:01 ` Wolfgang Schuster
2010-02-02 17:03 ` Design Department
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=4B65A898.5020206@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).