ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: reference formatting
Date: Fri, 23 Jun 2006 10:43:48 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0606231041410.3668@nqvgln> (raw)
In-Reply-To: <184E4960-99BB-4926-8048-F085173EAC17@science.uva.nl>

On Fri, 23 Jun 2006, Hans van der Meer wrote:

>
> On Jun 22, 2006, at 23:13, Aditya Mahajan wrote:
>
>>
>>
>> On Thu, 22 Jun 2006, Hans van der Meer wrote:
>>
>>> With \definereferenceformat[pin][left=(,right=)] it is possible to
>>> typeset
>>> references with
>>> 	\pin[ref] and get "(ref)"
>>>
>>> I have two questions in this respect:
>>>
>>> 1. is it possible to change the general setup in the same way,
>>> 	e.g. let \in[ref] do the same as \pin[ref] here.
>>> 	The left and right are not in setupreferencing.
>>
>
> I finally came up with this, a bit of a kludge I admit:
> \let\originalin=\in
> \definereferenceformat[parenthesizedin][left=(,right=),command=
> \originalin]
> \let\in=\parenthesizedin

Be careful with this. There are two places in the source that use \in 
command. You will get parenthesis around them also.

If you do not use those commands (\inline and I do not remember the 
second one, I checked that yesterday), then even

\definereferenceformat[in][left=(,right=)] should work.



>>> 2. some strange interchange takes place when using \pin{A}{B}[ref].
>>> 	Instead of the expected "A (ref) B" one gets "A (refB);
>>> 	it therefore seems the right parenthesis from the setup comes too
>>> late in play.
>>
>> As I understand referencing, this is the expected behaviour. I think
>> that \in{..}{..}[...] was for things like
>>
>> As seen in \in{Figure}{a}[fig]...
>>
>> that is when you want to refer to a subfigure (or a subformula).
>> That is
>> why there is no space between the number and the content in the second
>> {..}
>>
>
> I has not understood it that way, but thought it was meant to enclose
> the whole reference. I see the point now.
>
> Hans van der Meer
>
>
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
>

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

      reply	other threads:[~2006-06-23 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 14:13 Hans van der Meer
2006-06-22 21:13 ` Aditya Mahajan
2006-06-23  9:04   ` Hans van der Meer
2006-06-23 14:43     ` Aditya Mahajan [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=Pine.WNT.4.63.0606231041410.3668@nqvgln \
    --to=adityam@umich.edu \
    --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).