ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bibliography - maybeyear
Date: Fri, 29 Nov 2013 12:22:54 +0100	[thread overview]
Message-ID: <5298790E.1060408@uni-bonn.de> (raw)
In-Reply-To: <52977F43.9020304@wxs.nl>

On 11/28/2013 06:37 PM, Hans Hagen wrote:
>> Hello,
>>
>> Using
>>    \setuppublications [alternative=num]
>> for example, should not append letters to the publication years when
>> encountering multiple publications by the same author(s) per year.
>>
>> So, in the use of bibliographies, I have not understood how to control
>> \maybeyear.
>>
>> In the bibl-xxx.tex files, it is defined as
>>    \def\maybeyear#1{#1}
>> or
>>    \def\maybeyear#1{}
>> as needed. Perhaps this is for mkii.
>>
>> In bibl-bib.mkiv, one has
>>    \appendtoks
>>       \doifelse{\bibtexpublicationsparameter\c!maybeyear}\v!off
>>         {\let\maybeyear\gobbleoneargument}
>>         {\let\maybeyear\firstofoneargument}%
>>    \to \everysetupbibtexlistplacement
>> which seems to then use the keyword maybeyear.
>>
>> I guess that
>>    \setupbibtexpublications [maybeyear=off]
>> in my source would turn off the appended letters, but this is not
>> correct. I have tried many variants (\setuppublications, \setupbibtex).
>> What am I misunderstanding? Or is this a bug?
>
> \setuppublicationlist
>    [maybeyear=off]

maybeyear is one of the areas that need fixing. The simple on/off 
mechanism is not sufficient, because the behavior needs to be more complex:

1. If the citation style does not use the year as a key, do not append 
letters.

2. If the citation style uses year as key and only one publication/year 
of an author is quoted and listed (even if there are several in the bib 
file) do not append letter.

3. Append letter if citation style uses year AND more than one 
publication/year for given author is quoted and listed.

I assume that in order for this to work, Hans will have to rewrite the 
code which produces the .bbl file from the bib. Right now, AFAICS, the 
.bbl contains the entire .bib database. It should only contain the 
entries which are cited.

Alan, does that make sense to you?

Thomas
___________________________________________________________________________________
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:[~2013-11-29 11:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  8:12 Alan Braslau
2013-11-20 12:38 ` Hans Hagen
2013-11-20 12:53   ` Alan Braslau
2013-11-28 17:37 ` Hans Hagen
2013-11-29 11:22   ` Thomas A. Schmitz [this message]
2013-11-29 21:20     ` Alan Braslau

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=5298790E.1060408@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).