unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: 36252@debbugs.gnu.org
Subject: bug#36252: 26.1; bibtex-generate-autokey does not use use date field
Date: Sun, 06 Dec 2020 09:25:38 +0000	[thread overview]
Message-ID: <874kkzl20d.fsf@yandex.com> (raw)
In-Reply-To: <20190616202330.immdadcg24qedysq@zeta.rak.ac>

Hello,
>>>>> Patrick M Niedzielski <patrick@pniedzielski.net> writes:

    > Lars Ingebrigtsen <larsi@gnus.org> skribis:
    >> Lars Ingebrigtsen <larsi@gnus.org> writes: This was five weeks
    >> ago, and there was no response, so I'm closing this bug report.
    >> If progress can be made here, please respond to the debbugs mail
    >> address, and we'll reopen the bug report.

    > I’d like to reopen this bug, and submit the attached patch which I
    > believe fixes the issue. This patch teaches
    > ‘bibtex-generate-autokey’ to prefer an ISO8601-formatted ‘date’
    > field when present, and fall back to a ‘year’, and is implemented
    > using Lars’ ISO8601 parsing functions.

    > Just some implementation notes: I don’t believe Ryan’s original
    > patch works as documented when ‘bibtex-autokey-use-crossref’ is
    > non-nil.  In this case, his patch would seem to prefer a
    > crossref’d entry’s ‘year’ field to a local entry’s ‘date’
    > field. More concretely, with the following BibLaTeX,

    >  @misc{doe1995some, title = {Some work}, author = {John Doe}, year
    > = {1995}, date = {1995-01-01}, } @misc{, title = {Another work},
    > author = {Anon Y. Mous}, date = {1990-03-12}, crossref = {entry1},
    > }

    > When generating a key for entry2, the original patch would prefer
    > using the year 1995 to the year 1990, which is unintuitive. The
    > attached patch implements a different behavior instead, in which
    > an entry’s own ‘year/date’ field are prefered to the crossref’d
    > entry’s ‘year/date’ field. In the above case,
    > ‘bibtex-generate-autokey’ will generate a entry key with the year
    > 1990 rather than 1995.

    > Additionally, we prefer to use the ‘date’ field when present over
    > the ‘year’ field. This behavior is probably more correct, since
    > BibLaTeX deprecated the ‘year’ field in favor of its own ‘date’
    > field, which only should occur in BibLaTeX-flavor files. Note that
    > this is a breaking change from the prior behavior, but only when
    > an entry has incompatible ‘date’ and ‘year’ fields.  If a file is
    > meant to support both BibTeX and BibLaTeX, the ‘date’ and ‘year’
    > fields should contain the same information.

I am a heavy user of bibtex, but I am puzzled over the 'date'
field. Publications have a 'year' ok, sometimes a 'month', but never
have I seen a 'day'. So how would a user enter (YYYY-MM-DD)? Is it
perhaps the date of entry of the record in to the file? Sorry to butt
in, but I am curious.

Best wishes,

Colin Baxter.






  reply	other threads:[~2020-12-06  9:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 20:23 bug#36252: 26.1; bibtex-generate-autokey does not use use date field Ryan Kavanagh
2019-07-06 14:52 ` Lars Ingebrigtsen
2019-07-06 14:55 ` Lars Ingebrigtsen
2019-07-15  0:34   ` Ryan Kavanagh
2019-07-15  7:24     ` Lars Ingebrigtsen
2019-09-16 21:01       ` Lars Ingebrigtsen
2020-08-10 11:01         ` Lars Ingebrigtsen
2020-09-14 15:02           ` Lars Ingebrigtsen
2020-12-05  9:20             ` Patrick M. Niedzielski
2020-12-06  9:25               ` Colin Baxter [this message]
2020-12-07  6:18                 ` Roland Winkler
2020-12-06 13:19               ` Lars Ingebrigtsen
2020-12-07  6:20                 ` Roland Winkler
2020-12-07 15:14                   ` Lars Ingebrigtsen
2020-12-11 15:04                   ` Roland Winkler

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kkzl20d.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=36252@debbugs.gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).