ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Joey McCollum <jmccollum20140511@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Right-to-left pagecolumns and markings in ConTeXt
Date: Tue, 28 Apr 2020 13:05:51 -0400	[thread overview]
Message-ID: <CAGxRUG9ba3XwpcV+V0wbW0hHnBC0Sv+CJb52T0eLdyshkMAq0Q@mail.gmail.com> (raw)
In-Reply-To: <d0543d7e-3c48-1392-05df-4a9652c07134@xs4all.nl>


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

Thanks! Replacing "top" and "bottom" with "column:top" and "column:bottom"
didn't make the MWE work, but once you pointed out that the locations of
the marks to be fetched had to be column-specific, I started looking
through the mailing list and found something that worked. I just had to
change the \fetchmark calls in my MWE to \getmarking[TestMark][1][top] and
\getmarking[TestMark][2][bottom].

On Tue, Apr 28, 2020 at 10:32 AM Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 4/28/2020 2:09 PM, Joey McCollum wrote:
>
> > Is there some way I can improve my syntax to avoid this issue, or is it
> > just a bug that needs to be fixed? I've tried fetching other marks
> > (e.g., first and last), but the only marks that ConTeXt seems to find
> > are the ones for the left column.
> column:top etc
>
> -----------------------------------------------------------------
>                                            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
>
> ___________________________________________________________________________________
>

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

[-- 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-04-28 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 12:09 Joey McCollum
2020-04-28 13:34 ` Hans Hagen
2020-04-29 13:39   ` Joey McCollum
2020-04-28 14:32 ` Hans Hagen
2020-04-28 17:05   ` Joey McCollum [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=CAGxRUG9ba3XwpcV+V0wbW0hHnBC0Sv+CJb52T0eLdyshkMAq0Q@mail.gmail.com \
    --to=jmccollum20140511@gmail.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).