From: Oliver von Criegern <oliver.v.criegern@badw-muenchen.de>
To: ntg-context@ntg.nl
Subject: Re: Line numbering in two column layout conflicts with marking
Date: Mon, 9 Dec 2019 15:18:45 +0100 [thread overview]
Message-ID: <20cae0d0-c71f-c3cd-9525-94c5f206ca8c@badw-muenchen.de> (raw)
In-Reply-To: <eff828ce-f5e3-c8aa-2029-51ffd2a51b91@badw-muenchen.de>
Any suggestions, how to solve this problem?
Am 02.12.19 um 20:06 schrieb Oliver von Criegern:
> Dear list members,
>
> line numbering in a two column layout apparently conflicts with the
> marking mechanism.
>
> Consider the following example:
>
>
> \setupcolumns[n=2]
>
> \setuplinenumbering
> [
> step=5,
> method=page,
> align=flushright,
> ]
>
> \definemarking[Test]
>
> \setupheadertexts[{\fetchmark[Test][top] -- \fetchmark[Test][bottom]}]
>
> \startbuffer
> \dorecurse{12}{words }
> \stopbuffer
>
> \starttext
> \startcolumns
> \startlinenumbering
> \marking[Test]{ONE}ONE \dorecurse{12}{\getbuffer}\par
> \marking[Test]{TWO}TWO \dorecurse{29}{\getbuffer}\par
> \marking[Test]{THREE}THREE \dorecurse{12}{\getbuffer}\par
> \stoplinenumbering
> \stopcolumns
> \stoptext
>
>
> In the result, the header of the first page reads "ONE -- THREE",
> despite marking "THREE" being placed in the third line of the second
> page.
>
> Without linenumbering, the header of the first page reads "ONE --
> TWO", as is to be expected.
>
> Best regards,
> Oliver
>
>
--
Dr. Oliver von Criegern
Referat für IT und Digital Humanities
Bayerische Akademie der Wissenschaften
Alfons-Goppel-Str. 11
80539 München
Tel.: 089-23031-1310
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-12-09 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 19:06 Oliver von Criegern
2019-12-09 14:18 ` Oliver von Criegern [this message]
2019-12-18 16:39 ` Oliver von Criegern
2019-12-23 11:02 ` Wolfgang Schuster
2020-01-07 12:26 ` Oliver von Criegern
2020-01-07 18:40 ` 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=20cae0d0-c71f-c3cd-9525-94c5f206ca8c@badw-muenchen.de \
--to=oliver.v.criegern@badw-muenchen.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).