You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for creating this useful app. I noticed that it currently uses both date and year fields for managing literature entries. However, according to the biblatex documentation, it is better to exclusively use the date field instead of year:
The year of publication. This field is a literal field only when given explicitly in the data (for plain BibTeX compatibility for example). It is however better to use the date field as this is compatible with plain years too and supports many more features (p. 27).
If there is no date field in an entry, biblatex will also consider the fields year and month for backwards compatibility with traditional BibTeX but this is not encouraged as explicit year and month are not parsed for date meta-information markers or times and are used as-is (p. 40).
Using both date and year fields may cause parsing issues in some literature managing environments such as Emacs' bib mode. Therefore, I suggest using exclusively the date field for managing literature entries.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
Thank you for creating this useful app. I noticed that it currently uses both
date
andyear
fields for managing literature entries. However, according to thebiblatex
documentation, it is better to exclusively use thedate
field instead ofyear
:Using both
date
andyear
fields may cause parsing issues in some literature managing environments such as Emacs'bib
mode. Therefore, I suggest using exclusively thedate
field for managing literature entries.Thank you.
The text was updated successfully, but these errors were encountered: