ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Oliver von Criegern <oliver.v.criegern@badw-muenchen.de>
To: ntg-context@ntg.nl
Subject: Cross references to column numbers
Date: Mon, 12 Aug 2019 15:26:31 +0200	[thread overview]
Message-ID: <5c966e41-354a-a10e-0df4-7e1507d44419@badw-muenchen.de> (raw)

Dear list members,

how can I create cross references to column numbers?

I have a two column layout with column numbers in the header instead of 
page numbers (actually, these column numbers are calculated from the 
page numbers). Now I want to create a cross reference that returns the 
column number of the target. How can I achieve this?

Of course, I can get the page number with \pagereference (for the 
target) and \at (for the reference), but for calculating the column 
number (according to what I did in the header), I would also need to 
know whether the target is in the left or in the right column, and I 
can't see how I can get this information.

For an example, see the question posted by me at stackexchange:
https://tex.stackexchange.com/questions/502944/context-cross-references-to-column-numbers

Besides, I am wondering, regarding the generally very regular and 
consistent naming of commands in ConTeXt, why this is not so in the case 
of references. For example, to refer to a page, I need \pagereference 
(for the target) and \at (for the reference); to refer to a line, I need 
\someline (for the target) and \inline (for the reference), but only if 
I want it to automatically add the word "line" or something else before 
the number, otherwise I have to use \inlinerange. It took me some time 
to find that out. Wouldn't it be easier to have just one command for the 
target and another one for the reference, and everything else, as 
counters and headers to be returned, text to be added etc. to be 
configured by options?

Best regards,
Oliver.


___________________________________________________________________________________
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:[~2019-08-12 13:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 13:26 Oliver von Criegern [this message]
2019-09-02 16:46 ` Oliver von Criegern
2019-09-09 20:05   ` Henri Menke
2019-09-10 11:16     ` Hans Hagen
2019-09-10 16:52       ` Oliver von Criegern
2019-09-10 20:05       ` Henning Hraban Ramm
2019-11-12 12:02       ` Oliver von Criegern
2019-11-15 14:44         ` Oliver von Criegern
2019-11-15 15:31           ` Taco Hoekwater
2019-11-15 15:36             ` Taco Hoekwater
2019-11-15 19:22           ` Pablo Rodriguez
2019-11-16  8:59             ` 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=5c966e41-354a-a10e-0df4-7e1507d44419@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).