ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \textreference
Date: Sat, 26 Jul 2014 12:14:23 +0200	[thread overview]
Message-ID: <53D37F7F.50604@wxs.nl> (raw)
In-Reply-To: <53C2C8E6.6030809@FU-Berlin.DE>

On 7/13/2014 7:59 PM, Herbert Voss wrote:
> I thought that \textreference will print its text (Foo) in
> difference to \reference. With current minimal I can see no
> difference between both.
>
> \starttext
> \textreference[foo]{Foo}
> \reference[bar]{Bar}
>
> \about[foo] and \about[bar] \atpage[bar]
> \stoptext

\starttext

\textreference[foo]{Foo}
\reference[bar]{Bar}

about foo: \about[foo] \par
about bar: \about[bar] \par
in foo: \in{in}[foo] \par
in bar: \in{in}[bar] \par
at page foo: \at{page}[foo] \par
at page bar: \at{page}[bar] \par

\stoptext

(\atpage doesn't show a page when on the same page)

The distinction between \pagereference, \textreference and \reference is 
sort of historical and relates to efficiency (in mkii):

\pagereference : only stores the pagenumber
\textreference : only stores the text
\reference     : stores pagenumber and text

In mkiv the last two are the same now but they still can have different 
rendering (currently the rendering is aliased). Maybe we should just 
alias \reference to \textreference by now as I don't see that part 
change (the distinction was kept when mkiv was still new). So in fact we 
have just two commands now.

(\setreference[label][...] is a new one .. it reminds me that i should 
start checking for left-over experiments and kind of freeze the low 
level implementation ... these were among the first mechanisms redone)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2014-07-26 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 17:59 \textreference Herbert Voss
2014-07-26 10:14 ` Hans Hagen [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=53D37F7F.50604@wxs.nl \
    --to=pragma@wxs.nl \
    --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).