-
-
Notifications
You must be signed in to change notification settings - Fork 61
biblatex has adopted EDTF as a new date format #240
Comments
biblatex 3.6 is now out of beta. Here are a few examples of new EDTF date strings in biblatex that are currently not parsed correctly by
Actual output:
Expected output:
Actual output:
Expected output:
Actual output:
Expected output (time not supported in CSL, needs to be discarded):
Actual output:
Expected output (EDTF uses astronomical year count, with a year '0'; CSL JSON uses BCE/CE year count, without a year '0'; in CSL JSON, '-' is not an actual minus sign but should be understood as shorthand for 'BCE'):
Actual output:
Expected output:
Actual output:
Expected output:
Actual output:
Expected output:
Actual output:
Expected output (see https://web.archive.org/web/20150911220234/http://gsl-nagoya-u.net/http/pub/citeproc-doc.html for CSL JSON details):
Actual output:
Expected output ('uncertain' not supported in CSL, needs to be discarded):
Actual output:
Expected output ('uncertain' not supported in CSL, needs to be discarded):
Actual output:
Expected output (EDTF seasons are 21, 22, 23, 24; CSL seasons are 1, 2, 3, 4):
Actual output:
Expected output:
|
biblatex has adopted a new date format: EDTF Level 0 and 1, which is basically a superset of the ISO 8601-based format biblatex has been using so far.
New biblatex docs on this: https://github.com/plk/biblatex/blob/dev/doc/latex/biblatex/biblatex.tex#L1601 ff.
New elements
Level 0
2001-02-03T09:30:01
2004-01-01T10:10:10Z
2004-01-01T10:10:10+05:00
0
must be mapped to CSL JSON-1
(in order to appear as “1 BCE” in pandoc’s output), and EDTF-99
to CSL JSON-100
etc.Level 1
1984?
2004-06?
2004-06-11?
1984~
1984?~
~
, set the CSL JSON/YAMLcirca
flag.?
, for the time being.199u
19uu
1999-uu
1999-01-uu
1999-uu-uu
199u
to1990/1999
, and19uu
to1900/1999
, and sets flags such asyearindecade
; pandoc-citeproc could do the former, too (but of course not the latter); as to month and dayuu
parts, I’d say pandoc-citeproc could simply ignore these.2004-06-01/unknown
2004-01-01/open
1984~/2004-06
1984/2004-06~
1984?/2004?~
unknown
andopen
.~
anywhere in the string, set the CSL JSON/YAMLcirca
flag.?
, for the time being.y170000002
y-170000002
y
, adjust negative years as above.2001-21
,2001-22
,2001-23
,2001-24
season
element as“Spring”, “Summer”, “Autumn”, “Winter”,[EDIT] “1”, “2”, “3”, “4”, respectively (see citeproc-js specs).Use EDTF for CSL YAML?
Finally, it might be a good idea to start using the EDTF date format in CSL YAML, too. Besides being a widely adopted standard, it’s much shorter (e.g., one line vs seven for a YMD interval).
(I have heard EDTF-friendly noises from the CSL and citeproc-js sides, too; but while we’re relatively free to (re)define CSL YAML, for the time being of course we have to stick to the current CSL JSON format conventions.)
The text was updated successfully, but these errors were encountered: