ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: wrong page for annotation and \pagenumber
Date: Tue, 16 Jun 2020 13:46:28 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.77.987.2006161345460.1528@nqv-guvaxcnq> (raw)
In-Reply-To: <e170d80a-6936-4954-0732-31f0046e5915@gmx.es>

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

On Tue, 16 Jun 2020, Pablo Rodriguez wrote:

> On 6/16/20 4:58 PM, Wolfgang Schuster wrote:
>> Pablo Rodriguez schrieb am 16.06.2020 um 16:31:
>>> [...]
>>> I’m afraid that you get the same result, so there may be a bug there.
>>
>> There is no bug. When you take a look at my pagenumber example you see a
>> few lines at the top show the number of the previous page, this happens
>> because TeX collects more than necessary which means in your example
>> above the layer is placed when TeX was still on the first page.
>
> Many thanks for your reply, Wolfgang.
>
> I’m afraid that TeX is too tricky for me in that case (or I simply think
> that it is misbehaving there).
>
>> In your example you can add \testpage to \section to force a page break
>> when there isn't enough space available to place the heading, this moves
>> also the layer placement to the next page.
>
> I’m afraid this doesn’t work with my real document.
>
> I need another approach. This sample reflects my problem:
>
>  \setupinteraction[state=start]
>  %~ \showframe\showgrid
>  \starttext
>    \dorecurse{41}{one line\par}
>
>    \ \comment[location={rightmargin}]{comment}
>  \stoptext
>
> Since layers are problematic for the task, I insert the comments right
> after the text (which actually comes from \xmlflush{#1} [XML sources]).
>
> I’m afraid that the paragraph before \comment comes from \xmlflush, so I
> cannot avoid it.
>
> This is unproblematic for most cases, but the sample above displays the
> problem of adding a comment in a new paragraph. It might add a new page.
>
> To avoid this issue: how could I prevent the pagebreak before \comment
> and the addition of a pagebreak above?
>
> If that were possible, I could add a \blank[-2*line] that would place
> the comment right.

Try

\removeunwantedwhitespace

or

\blank[samepage]

Aditya

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

___________________________________________________________________________________
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:[~2020-06-16 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 12:52 Pablo Rodriguez
2020-06-15 14:09 ` Wolfgang Schuster
2020-06-15 15:29   ` Pablo Rodriguez
2020-06-16  2:53 ` Rudolf Bahr
2020-06-16 14:31   ` Pablo Rodriguez
2020-06-16 14:58     ` Wolfgang Schuster
2020-06-16 17:30       ` Pablo Rodriguez
2020-06-16 17:46         ` Aditya Mahajan [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=nycvar.YAK.7.77.987.2006161345460.1528@nqv-guvaxcnq \
    --to=adityam@umich.edu \
    --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).