From: Mark Smith <mark@bbprojects.net>
Subject: Re: bibmodule requests
Date: Thu, 31 Mar 2005 15:52:05 +0200 [thread overview]
Message-ID: <r02010500-1038-116364A1A1EC11D9B3E70011247BA132@[10.0.1.4]> (raw)
In-Reply-To: <424BDF75.9040501@elvenkind.com>
Taco Hoekwater wrote:
>The suffixes are needed because otherwise author,year styles
>cannot differentiate between different publications by one
>author in the same year. The actual implementation is a bit
>clumsy because it was mimicked incompletely from bibtex.
Hmm... then maybe a single field from which the contents are only collected for author,year styles that ask for/need the suffix could be used to hold the citekey unique identifier suffix ?
something like
\authoryearid{a}
?
...just thinking out loud. This might be a nightmare to implement for generating the author,year citations in the text druing a run. That's beyond my ken.
mark.
prev parent reply other threads:[~2005-03-31 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 15:21 Stefano
2005-03-31 8:29 ` Taco Hoekwater
2005-03-31 10:40 ` Mark Smith
2005-03-31 11:31 ` Taco Hoekwater
2005-03-31 12:13 ` Taco Hoekwater
2005-03-31 13:48 ` Mark Smith
2005-03-31 13:52 ` Mark Smith [this message]
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='r02010500-1038-116364A1A1EC11D9B3E70011247BA132@[10.0.1.4]' \
--to=mark@bbprojects.net \
--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).