ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: multiple bibliographies
Date: Tue, 5 Sep 2006 22:53:36 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0609052248010.3872@nqvgln> (raw)
In-Reply-To: <9C0EFBBD-34E8-45C1-928D-9D0AF5907B63@uni-bonn.de>

On Tue, 5 Sep 2006, Thomas A. Schmitz wrote:

> Dear all (and esp. Taco),
> Maybe a bit of background, and please tell me if you think this is a
> stupid idea: every term, I have to prepare lists of references for my
> several classes, and there usually is a lot of repetition and
> overlap. So I'm dreaming of having one big bibtex database and
> producing the lists via assorted \nocite commands. But i usually
> split up these bibliographies into several sections, and I want all
> items numbered in sequence, so I have in my source:
>
> \section{One}
>
> \nocite[myfirst] \nocite[mysecond]
>
> \placepublications
>
> \section{Two}
>
> \nocite[mythird] \nocite[myfourth]
>
> \placepublications
>

I do not know anything about feasibility, but have a suggestion for 
the input syntax. How about if there is

\definecitemethod[one]
\definecitemethod[two]

after which you can do

\cite[method=one][myfirst] or
\nocite[method=one][mysecond]

and also

\cite[method={one,two}][ref]

and so on.

And to obtain a list of bibliographies, do

\placepublications[method=one]


I am not sure whether this is same as how criteria works right now.


Do you think that a syntax like this makes sense?


Aditya

  reply	other threads:[~2006-09-06  2:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 17:44 Thomas A. Schmitz
2006-09-06  2:53 ` Aditya Mahajan [this message]
2006-09-06  6:17   ` Taco Hoekwater
2006-09-07  7:43     ` Thomas A. Schmitz
2006-09-07  8:02       ` Taco Hoekwater
2007-01-15 12:59 Charles Doherty
2007-01-15 13:22 ` Thomas A. Schmitz
2007-01-15 13:51   ` Charles Doherty
2007-01-15 15:55   ` Sanjoy Mahajan
2007-01-15 23:00     ` 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=Pine.WNT.4.63.0609052248010.3872@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).