ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [
Date: Thu, 21 Nov 2013 11:40:05 -0500	[thread overview]
Message-ID: <528E3765.5050802@sil.org> (raw)

In a thread from July
(http://context.markmail.org/thread/6tgzusw45whaqghi), Marco Patzer
raised some questions that we have too. They were somewhat answered, but
I'm still not clear on what the meanings of the keywords are.

On Jul 8, 2013 4:08:33 pm Hans wrote:
> On 7/9/2013 12:30 AM, Marco Patzer wrote:
> >/ On 2013–07–08 Hans Hagen wrote:
> />/
> />>>/ I expect the markings on the left and right to be the same and show
> />>>/ A–C on the first page and D–E on the second one. Looks like a bug to
> />>>/ me.
> />>/
> />>/ use top and bottom
> />/
> />/ This works. Thanks.
> />/
> />>/ -- previous : last before sync
> />>/ -- next     : first after sync
> />>/
> />>/ -- top      : first in sync
> />>/ -- bottom   : last in sync
> />>/
> />>/ -- first    : first not top in sync
> />>/ -- last     : last not bottom in sync
> />/
> />/ That is exactly what's in the wiki (Command/getmarking). To my
> />/ defence: The manual (chapter 12.4) is outdated, it lists:
> />/
> />/    previous - the last of the previous page
> />/    first    - the first of the actual page
> />/    last     - the last of the actual page
> />/    both     - first — last
> />/    all      - previous — first — last
> />/
> />/ I have no idea what “first not top in sync” means, in contrast to
> />/ “first of the actual page”, which is quite clear but wrong on a
> />/ current MkIV.
> /
> old tex terminology ... in mkiv i don't use the build-in-tex marks at 
> all (too much juggling needed to get things right)

So I'm wondering ... Hans, since the descriptions you posted are old tex
terminology, what do previous/next/top/bottom/first/last/etc. mean in
current terminology?
I agree with Marco that the descriptions in the ref manual are much
easier to understand, but appear to be wrong; and do not include top/bottom.
I'll be happy to update the ref manual and the wiki if I can get clear
and accurate information.

We have run many examples here, including the ones on the getmarking
wiki page, trying to understand what these keywords mean.
top/bottom do appear to do what we need in an MWE, but are not working
for us in the real document, and knowing the meaning of these keywords
would be very helpful in troubleshooting the problem.

Thanks,
Lars

___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2013-11-21 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 16:40 Lars Huttar [this message]
2013-11-21 18:01 ` bug: \getmarking with mixedcolumns Lars Huttar
2013-11-21 18:53   ` Lars Huttar
2013-11-22 21:34   ` Hans Hagen
2013-11-22 21:43     ` Lars Huttar
2013-11-26 21:54     ` Lars Huttar
2013-11-27 16:08     ` bug in beta: \tab results in text overlap Lars Huttar
2013-11-27 16:47       ` Lars Huttar
2013-11-27 21:07       ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
1999-11-17 10:03 % Haseloff, Lutz

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=528E3765.5050802@sil.org \
    --to=lars_huttar@sil.org \
    --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).