ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: YABQ (yet another bib question...)
Date: Fri, 15 Sep 2006 11:18:03 +0200	[thread overview]
Message-ID: <56F339C9-40B5-4D0F-8310-4AB388899CDF@uni-bonn.de> (raw)
In-Reply-To: <450A5CE5.5070307@elvenkind.com>


On Sep 15, 2006, at 9:57 AM, Taco Hoekwater wrote:

> The problem with redefining \maybeyear is that it affects all
> citations equally: when you have three Knuth records with the
> same year and two Tuftes with the same year in the database, then
> if you use only one of Knuths but both Tuftes, you can no longer
> see which one of the Tuftes you were citing.
>
> I could add an interface setting, so that you would do not have to
> resort to using \def, but it would be much better if I could fix
> the problem internally. Needs some thinking, though
>
> Taco

Yes, I see the difficulty. I don't know enough about bibtex styles  
and habits in general, but I'm just wondering if \maybeyear should be  
used in a different way - in my discipline, I think it would.  
Consider this example:

Hoekwater, First article, journalA, vol. 5 (2006)

Hoekwater, Second article, journalB, vol. 10 (2006)

IMHO, bibtex should now generate keys such as Hoek2006a and Hoek2006b  
or authoryear references like Hoekwater (2006a) and Hoekwater  
(2006b), but it should not (!) append the "a" and "b" to the years in  
the bibliographic list itself. But I may be wrong here - what do you  
and other users say? Should the (2006) in the example above come out  
as "(2006a)" and "(2006b)"? And as I was suggesting: if you use  
numered references, I think it would be best to just switch maybeyear  
off completely, so my suggestion would be to have a switch "maybeyear  
= on/off" for  the \setuppublicationlist.

Best

Thomas

  reply	other threads:[~2006-09-15  9:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 20:53 Thomas A. Schmitz
2006-09-08 22:40 ` Sanjoy Mahajan
2006-09-10 13:30   ` Taco Hoekwater
2006-09-14 21:46     ` Thomas A. Schmitz
2006-09-15  7:57       ` Taco Hoekwater
2006-09-15  9:18         ` Thomas A. Schmitz [this message]
2006-09-15  9:47           ` Taco Hoekwater
2006-09-15 10:05             ` Thomas A. Schmitz
2006-09-15 12:34           ` Sanjoy Mahajan
2006-09-15 13:09             ` Thomas A. Schmitz
2006-09-15 14:45               ` Taco Hoekwater
2006-09-11  8:28   ` Thomas A. Schmitz
2006-09-11 17:11     ` Taco Hoekwater
2006-09-11 19:05       ` Thomas A. Schmitz
2006-09-11 19:30     ` Sanjoy 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=56F339C9-40B5-4D0F-8310-4AB388899CDF@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).