ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Murphy <michael.murphy@uni-ulm.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Mutiple citations doesn't work with compress=no + interaction
Date: Wed, 09 Jun 2010 14:31:30 +0200	[thread overview]
Message-ID: <4C0F89A2.5090008@uni-ulm.de> (raw)
In-Reply-To: <4C0F74DC.9050607@elvenkind.com>

On 09/06/10 13:02, Taco Hoekwater wrote:
> Michael Murphy wrote:
>>
>> Thanks for the code, but that turns out not to help. The problem seems
>> to be when I want to have references in footnotes (see attached
>> minimal example).
>
> Ok, now I see. Attached is a new version of min_bib_fn.tex that fixes
> citations in footnotes. However ... something totally weird happens
> in the current context and beta's: the footnote appears to be repeated
> inside the body text.
>
> For some reason I do not understand, \placepublications also seems to
> process the footnote list (and because there is no proper definition
> for handling them, rubbish appears on the top of the publication list).
>
> This problem is not caused by the \cite inside the \footnote, nor by the
> redefinition of \cite, it happens without those as well.

Thanks, that works a treat. I also noticed the thing with the footnote, 
but it doesn't happen in my main document, so I wondered if it had 
something to do with the minimal setup. But you're right, it seems to 
always happen with \placepublications.

Anyway, I've now modified things slightly so that I can still use the 
optional forms of \cite (like \cite[authoryear]), so my file now looks like

\setupinteraction[state=start]

\usemodule[bib]

\setuppublications[refcommand=authoryears, criterium=all]

\let\NORMALcite\cite
\newif\ifSEEN
\unexpanded\def\cite[#1]{\strictdoifnextoptionalelse{\NORMALcite[#1]}%
   {\domycite[#1]}}
\def\domycite#1[#2]{\SEENfalse
   \def\processitem##1{\ifSEEN, \else\SEENtrue \fi \NORMALcite[##1]}%
   (\processcommalist[#2]\processitem )}

\setupcite[authoryears][compress=no,left=,right=]
\setupcite[authoryear][compress=no]

...

Of course, the other disadvantage of this at present is that I don't get 
'and' separating the last two references when I use \domycite. But I can 
live with that (on screen at least, for printing I can revert to the old 
behaviour).

-- 
Michael Murphy
___________________________________________________________________________________
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:[~2010-06-09 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 15:34 Michael Murphy
2010-06-08 18:47 ` taco
2010-06-09  9:21   ` Michael Murphy
2010-06-09  9:24     ` Taco Hoekwater
2010-06-09  9:34       ` Michael Murphy
2010-06-09 11:02         ` Taco Hoekwater
2010-06-09 12:31           ` Michael Murphy [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=4C0F89A2.5090008@uni-ulm.de \
    --to=michael.murphy@uni-ulm.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).