From: Carsten Fechtmann <fecht@zarm-technik.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: Messy results when using "table" in head and multi-page "tables" in text
Date: Sun, 20 Jan 2008 16:22:10 +0100 [thread overview]
Message-ID: <301CAC1B-F6FD-4A4E-86F5-2D5BB5A2BF05@zarm-technik.de> (raw)
In-Reply-To: <20080120141011.87c42b93.schuster.wolfgang@googlemail.com>
Dear Wolfgang,
I tried that too already, but unfortunately I run into the same problem:
That is, if I use the natural tables in the header, I can't use them
for multi-page tables in the text, as again the results ain't pretty,
to say the least.
Here the ConTeXt to show what happens in that case
(and using your suggestion for the page-head with natural tables)
\setuppagenumbering[location=]
\setupheadertexts[\setups{pagehead}][][\setups{pagehead}][]
\startsetups[pagehead]
\bTABLE[option=stretch,strut=no,offset=.5em]
\bTR
\bTD[align={right,lohi},width=4cm] left \eTD
\bTD[align={middle,lohi},width=6cm] middle \eTD
\bTD[align={left,lohi},width=4cm] right \eTD
\eTR
\eTABLE
\stopsetups
\starttext
\bTABLE[split=repeat,option=stretch,strut=no,offset=.5em]
\bTABLEhead[rulethickness=1pt]
\bTR
\bTH[align={middle,lohi},width=6cm] head \eTH
\eTR
\eTABLEhead
\bTABLEbody%
%\dorecurse{1}{ % works
\dorecurse{10}{ % works NOT
\bTR
\bTD
{\input knuth \par}
\eTD
\eTR
}
\eTABLEbody
\bTABLEfoot
\bTR
\bTH footer \eTH
\eTR
\eTABLEfoot
\eTABLE
\stoptext
The thing is, I rather tell the users of this page-layout NOT to use
the \starttables ... \stoptables for multi-page tables, but rely on
the natural tables for those (which work nicely, even though I
_really_ would like to have a dedicated footer for each page here and
not just one for the last page! Which by the way is something one
doesn't need a dedicated command for, as one could _always_ just place
that part at the end of the body part, as that will be then at the end
of the table, i.e. the right place, no matter how many pages the table
has.)
However, given, that \starttables ... \stoptables doesn't give me the
correct footer in my case anyway, I rather have one type of table that
is quite a bit easier for me and my colleagues to use and adapt for
the multi-page tables, i.e. the 'natural' ones, and therefore keep
using table in the header.
But yes, thanks for the suggestion, unfortunately, TABLE seems to rely
on the same sort of buffer / storage / whatever mechanism, to do it's
multi-page magic....
And that just doesn't work with having the same table-type in the
header, too.
(This is probably also true in case of the footer...)
Overall, things do work, as long as one does use the other type of
table or tables / TABLE in either header or text, but it works NOT
when you use the same in both...
Not quite sure, what's the reason for that or (and more importantly)
what can be done about it
With best regards
Carsten
P.S.: What is interesting is that on the last pages of a multi-page
table things do become sorted out again in either case and everything
looks more or less as it should (i.e. like in the single-page table)
Am 20.01.2008 um 14:10 schrieb Wolfgang Schuster:
> On Sun, 20 Jan 2008 12:37:13 +0100
> Carsten Fechtmann <fecht@zarm-technik.de> wrote:
>
>>
>> Dear ConTeXt experts,
>>
>> I have setup a page layout where I use "table" in the page-head for
>> formatting quite a bit of stuff. (The example below is just a simple
>> as can be basic idea, to show the overall effect)
>> Now - as I can't prevent later users of this layout environment - to
>> not use \starttables ... \stoptables I naturally would like for this
>> to work in the text region as well.
>> This works fine and as advertised (well mostly, see below) as long as
>> the table does not spill over to the next page. In which case, things
>> start to look very messy, indeed.
>>
>> From my (simple) point of view it looks like ConTeXt gets confused
>> about which format to use for which table and tries to do them all at
>> the same place or something.
>>
>> Any chance to get this fixed ?
>
> Use the following setup for the header, it use natural tables.
>
> \startsetups pagehead
>
> \bTABLE[option=stretch,strut=no,offset=.5em]
> \bTR
> \bTD[align={right,lohi},width=4cm] left \eTD
> \bTD[align={middle,lohi},width=6cm] middle \eTD
> \bTD[align={left,lohi},width=4cm] right \eTD
> \eTR
> \eTABLE
>
> \stopsetups
>
>> Thanks in advance
>> Carsten
>>
>> P.S.: There is an additional bug (also concerning the single page
>> version and not related to having a "table" in the pagehead), which
>> puts in an extra (empty) gap in between the end of the tablebody and
>> the tablefoot when the tablefoot starts with \HL (and there is no \HL
>> at the end of tablebody).
>> Things work when putting the \HL at the end of the tablebody, but
>> then
>> no \HL will be put on top of the foot for any intermediate pages of
>> the table, which is certainly not what one would usually want in this
>> case.
>
> I have no solution for this.
>
>> Anyway, here a simple version of this to demonstrate the effect(s)
>>
>> \setuppagenumbering[location=]
>> \setupheadertexts[\setups{pagehead}][][\setups{pagehead}][]
>> \startsetups[pagehead]
>> \SetTableToWidth{\makeupwidth}
>> \starttable[|p(40mm)|p(60mm)|p(40mm)|]
>> \HL
>> \VL \leftaligned{left} \VL \midaligned{middle} \VL
>> \rightaligned{right} \VL\SR
>> \HL
>> \stoptable
>> \stopsetups
>>
>> \starttext
>>
>> \start
>> \SetTableToWidth{\makeupwidth}
>> \setuptables[split=repeat]
>> \starttablehead
>> \HL
>> \VL Head \VL\SR
>> \HL
>> \stoptablehead
>> \starttabletail
>> \HL % This results in an additional bug,
>> % i.e. an extra / unwanted gap
>> \VL Foot \VL\SR
>> \HL
>> \stoptabletail
>> \starttables[|p(.95\textwidth)|]
>> \VL \input knuth \VL\FR
>> %\dorecurse{1}{\VL \input tufte \VL\MR}
>> \dorecurse{10}{\VL \input tufte \VL\MR}
>> \VL \input knuth \VL\LR
>> % \HL % putting \HL here does not introduce
>> % that unwanted gap ...?!?
>> \stoptables
>> \stop
>>
>> \stoptext
>
> 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 : 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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-20 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 11:37 Carsten Fechtmann
2008-01-20 13:10 ` Wolfgang Schuster
2008-01-20 15:22 ` Carsten Fechtmann [this message]
2008-01-20 16:18 ` Wolfgang Schuster
2008-01-20 19:07 ` Carsten Fechtmann
2008-01-21 9:25 ` Wolfgang Schuster
2008-01-21 11:26 ` Peter Rolf
2008-01-21 11:45 ` Peter Rolf
2008-01-23 22:11 ` Carsten Fechtmann
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=301CAC1B-F6FD-4A4E-86F5-2D5BB5A2BF05@zarm-technik.de \
--to=fecht@zarm-technik.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).