From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Chapter-wise bibliographies and multi-chapter citations
Date: Sat, 15 Apr 2006 10:28:49 +0200 [thread overview]
Message-ID: <4440AEC1.7070901@elvenkind.com> (raw)
In-Reply-To: <e1pn6e$2ob$1@sea.gmane.org>
Johannes Graumann wrote:
>
> I run into the problem, that shared citations (in this case 'garrels:96'
> and 'gavin:06' are only printed following the first '\placepublications'
> call and not the second. I'm collating multiple publications into a thesis
> and since they all deal with similar themes, there's a lot of overlap. My
> university requires chapter-specific complete bibliographies, so the status
> quo is bad for me.
Unfortunately, this is not something I can fix quickly, because
ConTeXt's list mechanism does not support it. I have to rewrite
large parts of the module for this to work, and that takes time.
When is your deadline?
Taco
next prev parent reply other threads:[~2006-04-15 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 2:48 Johannes Graumann
2006-04-15 8:28 ` Taco Hoekwater [this message]
2006-04-15 21:08 ` Johannes Graumann
2006-04-16 10:03 ` Taco Hoekwater
2006-04-16 14:46 ` Johannes Graumann
2006-04-17 8:40 ` Hans Hagen
2006-04-17 8:58 ` Taco Hoekwater
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=4440AEC1.7070901@elvenkind.com \
--to=taco@elvenkind.com \
--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).