ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: YABQ (yet another bib question...)
Date: Fri, 15 Sep 2006 13:34:15 +0100	[thread overview]
Message-ID: <E1GOCtb-0008FR-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Fri, 15 Sep 2006 11:18:03 +0200." <56F339C9-40B5-4D0F-8310-4AB388899CDF@uni-bonn.de>

> 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)"? 

At first I was sure that (2006a) and (2006b) are the right answer for
the list.  Othewise how else could the user know which entry to look
up when they see, say, Hoekwater (2006b) in the text?  But I just
figured out the answer to that question: Users count 'a', 'b',
... starting with the first 2006 entry.  However, I still don't think
it's a good idea to make them do that.  Let's not ask users to do what
computers do very well (counting)!

> 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.

Let me know whether I'm understanding it correctly.  If you have a
numbered reference list, then the year can still end up with a letter
tag, e.g.

1. Taco Hoekwater.  JournalA.  2006a
2. Taco Hoekwater.  JournalB.  2006b

Ah, I hadn't thought of that problem.  You're right, there shouldn't
be a maybeyear in this case since the list number disambiguates the
reference completely.

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

  parent reply	other threads:[~2006-09-15 12:34 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
2006-09-15  9:47           ` Taco Hoekwater
2006-09-15 10:05             ` Thomas A. Schmitz
2006-09-15 12:34           ` Sanjoy Mahajan [this message]
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=E1GOCtb-0008FR-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).