From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] oc-basic: support biblatex date field
Date: Tue, 2 Nov 2021 14:00:47 -0400 [thread overview]
Message-ID: <CAF-FPGMtr_fd1Z3QBkgFB057FbQG5JHYPiCWtKK3nj4sRR1rsg@mail.gmail.com> (raw)
In-Reply-To: <877ddqwiyu.fsf@nicolasgoaziou.fr>
On Tue, Nov 2, 2021 at 1:44 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> "Bruce D'Arcus" <bdarcus@gmail.com> writes:
>
> > This is a tiny change that just checks for a 'date' field if 'year' is
> > nil, and if present, grabs the first four characters.
>
> The date field may also be nil, leading to an error.
Can you please fix that, if the patchis otherwise fine?
> Is there a guarantee that the date field starts with the year?
Not 100% guarantee, but should be close.
The biblatex manual (section 2.3.8 Date and Time Specifications), says
the following:
"Date fields such as the default data model dates date, origdate,
eventdate, and urldate adhere to iso8601-2 Extended Format
specification level 1."
This is an extension to standard 8601 dates, previously known as EDTF
(extended date-time format).
So for the vast majority of cases, yes; the value would be standard 8601 dates.
The exceptions should be very rare open-ended ranged dates; from table 3.
../1997
/1997
I do not, however, have a good knowledge of what people do in the
wild. It just seems like such a critical data field should be
supported.
Bruce
PS - FSF confirmed my copyright assignment today.
next prev parent reply other threads:[~2021-11-02 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 12:27 [PATCH] oc-basic: support biblatex date field Bruce D'Arcus
2021-11-02 17:44 ` Nicolas Goaziou
2021-11-02 18:00 ` Bruce D'Arcus [this message]
2021-11-03 15:16 ` Nicolas Goaziou
2021-11-04 20:47 ` Bruce D'Arcus
2021-11-04 22:03 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF-FPGMtr_fd1Z3QBkgFB057FbQG5JHYPiCWtKK3nj4sRR1rsg@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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/org-mode.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).