From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: reference formatting
Date: Thu, 22 Jun 2006 17:13:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.63.0606221634390.21815@rrpf4327h07.ratva.hzvpu.rqh> (raw)
In-Reply-To: <1A225B6D-F10C-49B1-BBF1-A3FF63C49975@science.uva.nl>
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.
Don't know about this.
> 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
{..}
This is what core-ref.tex says
%D \placefigure
%D [here][three calls]
%D {Three alternatives reference calls.}
%D {\startcombination[1*3]
%D {\framed{\type{ \in }}} {a}
%D {\framed{\type{ \at }}} {b}
%D {\framed{\type{\goto}}} {c}
%D \stopcombination}
%D
%D \startbuffer
%D \in figure[fig:three calls]
%D \in{figure}[fig:three calls]
%D \in figure a[fig:three calls]
%D \in{figure}{a}[fig:three calls]
%D figure~\in[fig:three calls]
%D \stopbuffer
%D
%D \typebuffer
%D
%D This turns up as:
%D
%D \startlines
%D \getbuffer
%D \stoplines
I was not aware of that the braces around figure can be omitted!
Aditya
next prev parent reply other threads:[~2006-06-22 21:13 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 [this message]
2006-06-23 9:04 ` Hans van der Meer
2006-06-23 14:43 ` Aditya Mahajan
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.GSO.4.63.0606221634390.21815@rrpf4327h07.ratva.hzvpu.rqh \
--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).