From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: bibmodule requests
Date: Thu, 31 Mar 2005 13:31:01 +0200 [thread overview]
Message-ID: <424BDF75.9040501@elvenkind.com> (raw)
In-Reply-To: <r02010500-1038-3F7C90EBA1D111D9B3E70011247BA132@[10.0.1.4]>
Mark Smith wrote:
>
> Put another way, what is the rationale behind having e.g.:
>
> y=2005a instead of y=2005
> and:
> \pubyear{2005\maybeyear{a}} instead of \pubyear{2005}
> ?
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.
> Another minor question: why are the text contents of the abstract field hard-wrapped ?
Because they were so in the original bib file.
Taco
next prev parent reply other threads:[~2005-03-31 11:31 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 [this message]
2005-03-31 12:13 ` Taco Hoekwater
2005-03-31 13:48 ` Mark Smith
2005-03-31 13:52 ` Mark Smith
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=424BDF75.9040501@elvenkind.com \
--to=taco@elvenkind.com \
--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).