ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Werner Hennrich <wehe@gmx.at>,
	Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Subject: Re: new page before xtable with repeated headers
Date: Fri, 23 Apr 2021 21:28:11 +0200	[thread overview]
Message-ID: <a8160df5-e5d2-3643-0118-25ae3062719a@xs4all.nl> (raw)
In-Reply-To: <5043cf43-b60a-2e83-d5a8-05dc69b86e29@gmx.at>

On 4/23/2021 11:33 AM, Werner Hennrich wrote:
> Hello everyone,
> 
> I'm having an xtable spanning several pages and need to have its headers 
> repeated.
> 
> For this I've set "split=repeat", but unfortunately this causes the 
> table to start with a new new page leaving the rest of the preceding 
> page empty. Having "split=yes" makes the tabe continue on the previous 
> page as a need it to, but then the header isn't repeated any longer.
> 
> I realize that there has been a very similar question already in 
> https://www.mail-archive.com/ntg-context@ntg.nl/msg93775.html, but my 
> problem happens isolated in a very clean situation w/o any header, 
> floats or the like - and I don't see yet how I can get this working in 
> my situation. Any help is highly appreciated, here is a MWE of my problem:
Always tricky this (on my agenda is to look into the engines page 
builder ...)

You can put this on cont-new.mkxl as test:

\unprotect

\defcsname\??xtableflushsplit\v!repeat\endcsname
   {\doloop
      {\clf_x_table_flush
         method {\v!split}%
         height 
\ifdim\pagegoal=\maxdimen\textheight\else\dimexpr\pagegoal-\pagetotal\relax\fi
       \relax
       \ifcase\c_tabl_x_state
         \exitloop
       \else
         \page
       \fi}}

\protect

Please test a lot! I also needs Wolfgangs opinion on this. Maybe 
preceding whitespace can interfere so maybe we need some 'slack' parameter.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-04-23 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23  9:33 Werner Hennrich
2021-04-23 19:28 ` Hans Hagen [this message]
2021-04-24  7:56   ` Werner Hennrich
     [not found]   ` <97b89634-8d32-db43-ec9f-2fca501b9464@gmail.com>
2021-04-26 13:36     ` Werner Hennrich
2021-05-31  8:50   ` Werner Hennrich
2021-05-31  9:33     ` Hans Hagen
2021-05-31 10:36       ` Werner Hennrich
2021-05-31 10:45         ` Werner Hennrich
2021-05-31 12:07         ` Hans Hagen

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=a8160df5-e5d2-3643-0118-25ae3062719a@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@googlemail.com \
    --cc=wehe@gmx.at \
    /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).