ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Duncan Hothersall <dh@capdm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Position of overflowing TABLE after split
Date: Tue, 19 Nov 2024 17:02:55 +0000	[thread overview]
Message-ID: <CAN8fp9UOT8=z9YAMWRH0N9DRjBXDJ5ZYjHo__P2DY2NE0fGa1A@mail.gmail.com> (raw)
In-Reply-To: <fd7734aa-e577-4bbf-9bd3-b79a2c4b0278@vonhirschfeld.eu>


[-- Attachment #1.1: Type: text/plain, Size: 1897 bytes --]

If your document is set up as double-sided
(\setuplayout[alternative=doublesided] or similar) then I think this is the
expected behaviour, since the margins flip on odd and even pages. You could
set up as single-sided to prevent this but you may be relying on the
double-sided setup for other things (page numbers, headers and footers for
example).

Duncan

On Tue, 19 Nov 2024 at 15:11, Niklas von Hirschfeld <niklas@vonhirschfeld.eu>
wrote:

> Hi there,
>
> when having an overflowing TABLE in width (e.g. with the TABLE option
> 'textwidth=\dimexpr\textwidth+\rightmarginwidth\relax') the position
> (horizontal) changes after a split.
>
> Before the first split the table overflows into the right margin. After
> that the position changes and it's overflowing into the left margin.
>
> Here is a minimal example:
>
> \startplacetable[location={split}]
> \bTABLE[option=stretch,split=yes,textwidth=\dimexpr\textwidth+\rightmarginwidth+\rightmargindistance\relax]
>
>
>   \dorecurse{100}{
>        \bTR
>          \bTD Cell 1 \eTD
>          \bTD Cell 2 \eTD
>          \bTD Cell 3 \eTD
>        \eTR
>      }
> \eTABLE
> \stopplacetable
>
> Is this behavior expected?
>
> I would like the position to be the same as before the split,
> overflowing into the right margin, how could I achieve this.
>
>
> Thank you and best regards
>
> Niklas von Hirschfeld
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive  : https://github.com/contextgarden/context
> wiki     : https://wiki.contextgarden.net
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2919 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-11-19 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 15:02 [NTG-context] " Niklas von Hirschfeld
2024-11-19 17:02 ` Duncan Hothersall [this message]
2024-11-20 21:01   ` [NTG-context] " Niklas von Hirschfeld

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='CAN8fp9UOT8=z9YAMWRH0N9DRjBXDJ5ZYjHo__P2DY2NE0fGa1A@mail.gmail.com' \
    --to=dh@capdm.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).