From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: natural table splitting bug
Date: Fri, 26 Oct 2007 15:12:55 +0200 [thread overview]
Message-ID: <4721E7D7.4050202@gmx.net> (raw)
In-Reply-To: <6703815B292B664DBAEC55EE3192386A20BC51@poseidon.in.dynetics.com>
Hi Michael,
Santy, Michael schrieb:
> In our XML->ConTeXt->PDF workflow, we've encountered a few intermittent
> problems when using split natural tables. I'm not able to post the
> original documents in which the problems are manifesting, but below is a
> document that reproduces one of the problems. The first page of the
> document is full of text, pushing a split natural table with five rows
> and a header to the top of the second page. However, only the first row
> appears on the second page, and the rest of the table is continued on
> the third page.
>
> I'm using a stock ConTeXt 9/28 distribution, but this problem can also
> be reproduced on live.contextgarden.net.
>
> Can someone please tell me what I'm doing wrong or help me debug this
> problem? These natural table bugs are the only thing stopping us >from
> deploying our ConTeXt workflow.
>
> Cheers,
> Mike Santy
>
>
> \setuppapersize[letter][letter]
>
> \showframe
>
> \starttext
>
> \def\blah{
the 'error' is already on the first page (text expands over it's lower
border).
Simply try
\def\blah{%
and see what happens. Spurious spaces can be cruel :)
Best wishes, Peter
> Now is the time for all good men to come to the aid of their %
> country. The quick brown fox jumped over the lazy dog.
> }
> \dorecurse{28}{\blah}
>
> \placetable[split]{Broken Split Table}{
> \setupTABLE[split=repeat]
> \bTABLE
> \bTABLEhead
> \bTR[style=\bf]
> \bTD Header A \eTD
> \bTD Header B \eTD
> \eTR
> \eTABLEhead
> \bTABLEbody
> \dorecurse{5}{
> \bTR
> \bTD A \eTD
> \bTD B \eTD
> \eTR
> }
> \eTABLEbody
> \eTABLE
> }
>
> \stoptext
>
>
> ------------------------------------------------------------------------
>
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________
prev parent reply other threads:[~2007-10-26 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 12:32 Santy, Michael
2007-10-26 13:12 ` Peter Rolf [this message]
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=4721E7D7.4050202@gmx.net \
--to=indiego@gmx.net \
--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).