Is the month field really deprecated? The 2019 Stack Overflow Developer Survey Results Are Inbiblatex month fieldDisable month in biblatex bibliography?How to not print the day/month of a BibLaTeX reference?Using another entry's date field with biblatexCan JabRef order by date instead of year?Optional fields 2 in JabRef 3.1 are not configurableJabRef 3.2 and automatic formatting on savebiblatex: userdefined date specification for custom entry type possible?How to embed a PDF file specified in the file field via JabRef?Why does biber still complain about contents of a field removed by DeclareSourceMap?
Why do UK politicians seemingly ignore opinion polls on Brexit?
What is the meaning of Triage in Cybersec world?
Is three citations per paragraph excessive for undergraduate research paper?
What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?
Why can Shazam fly?
Earliest use of the term "Galois extension"?
Are there incongruent pythagorean triangles with the same perimeter and same area?
Delete all lines which don't have n characters before delimiter
Loose spokes after only a few rides
Statement true because not provable
Did 3000BC Egyptians use meteoric iron weapons?
Identify This Plant (Flower)
Why isn't airport relocation done gradually?
Falsification in Math vs Science
Do these rules for Critical Successes and Critical Failures seem Fair?
Can a rogue use sneak attack with weapons that have the thrown property even if they are not thrown?
What do the Banks children have against barley water?
What is the closest word meaning "respect for time / mindful"
Deal with toxic manager when you can't quit
Landlord wants to switch my lease to a "Land contract" to "get back at the city"
Should I use my personal e-mail address, or my workplace one, when registering to external websites for work purposes?
What does Linus Torvalds mean when he says that Git "never ever" tracks a file?
If a Druid sees an animal’s corpse, can they wild shape into that animal?
Time travel alters history but people keep saying nothing's changed
Is the month field really deprecated?
The 2019 Stack Overflow Developer Survey Results Are Inbiblatex month fieldDisable month in biblatex bibliography?How to not print the day/month of a BibLaTeX reference?Using another entry's date field with biblatexCan JabRef order by date instead of year?Optional fields 2 in JabRef 3.1 are not configurableJabRef 3.2 and automatic formatting on savebiblatex: userdefined date specification for custom entry type possible?How to embed a PDF file specified in the file field via JabRef?Why does biber still complain about contents of a field removed by DeclareSourceMap?
Jabref 3.8.2 has a tab with Deprecated fields including the field Month.

The Biblatex documentation 3.12 still describes the field month and I could not find a sign of deprecation:

Was it wrong by Jabref to call month deprecated? Is there a misunderstanding?
biblatex bibliographies jabref date
add a comment |
Jabref 3.8.2 has a tab with Deprecated fields including the field Month.

The Biblatex documentation 3.12 still describes the field month and I could not find a sign of deprecation:

Was it wrong by Jabref to call month deprecated? Is there a misunderstanding?
biblatex bibliographies jabref date
add a comment |
Jabref 3.8.2 has a tab with Deprecated fields including the field Month.

The Biblatex documentation 3.12 still describes the field month and I could not find a sign of deprecation:

Was it wrong by Jabref to call month deprecated? Is there a misunderstanding?
biblatex bibliographies jabref date
Jabref 3.8.2 has a tab with Deprecated fields including the field Month.

The Biblatex documentation 3.12 still describes the field month and I could not find a sign of deprecation:

Was it wrong by Jabref to call month deprecated? Is there a misunderstanding?
biblatex bibliographies jabref date
biblatex bibliographies jabref date
asked Apr 7 at 9:35
Jonas SteinJonas Stein
3,34042746
3,34042746
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Depends on your definition of 'deprecated', I'd say. The biblatex documentation does not literally say month (or year, where the situation is the same) is deprecated.
But the documentation of the year field ends with
It is however better to use the
datefield as this is compatible with plain years too and supports many more features.
and similarly the documentation for month says
It is however better to use the
datefield as this supports many more features.
To me that seems sufficient reason for JabRef to place both of these fields in the 'deprecated' section and prefer date instead when it is in biblatex mode.
It is unlikely that year and month will cease to work in biblatex, because that would be a backwards compatibility nightmare. But as far as I am concerned I'd definitely recommend date over year and month (if you don't need compatibility with classic BibTeX).
The next version of biblatex will have slightly more explicit advice on year/month vs date in the docs: https://github.com/plk/biblatex/commit/7d7c682f9ec7f06aadd4f176dcfcdadb9afe33ea
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483642%2fis-the-month-field-really-deprecated%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Depends on your definition of 'deprecated', I'd say. The biblatex documentation does not literally say month (or year, where the situation is the same) is deprecated.
But the documentation of the year field ends with
It is however better to use the
datefield as this is compatible with plain years too and supports many more features.
and similarly the documentation for month says
It is however better to use the
datefield as this supports many more features.
To me that seems sufficient reason for JabRef to place both of these fields in the 'deprecated' section and prefer date instead when it is in biblatex mode.
It is unlikely that year and month will cease to work in biblatex, because that would be a backwards compatibility nightmare. But as far as I am concerned I'd definitely recommend date over year and month (if you don't need compatibility with classic BibTeX).
The next version of biblatex will have slightly more explicit advice on year/month vs date in the docs: https://github.com/plk/biblatex/commit/7d7c682f9ec7f06aadd4f176dcfcdadb9afe33ea
add a comment |
Depends on your definition of 'deprecated', I'd say. The biblatex documentation does not literally say month (or year, where the situation is the same) is deprecated.
But the documentation of the year field ends with
It is however better to use the
datefield as this is compatible with plain years too and supports many more features.
and similarly the documentation for month says
It is however better to use the
datefield as this supports many more features.
To me that seems sufficient reason for JabRef to place both of these fields in the 'deprecated' section and prefer date instead when it is in biblatex mode.
It is unlikely that year and month will cease to work in biblatex, because that would be a backwards compatibility nightmare. But as far as I am concerned I'd definitely recommend date over year and month (if you don't need compatibility with classic BibTeX).
The next version of biblatex will have slightly more explicit advice on year/month vs date in the docs: https://github.com/plk/biblatex/commit/7d7c682f9ec7f06aadd4f176dcfcdadb9afe33ea
add a comment |
Depends on your definition of 'deprecated', I'd say. The biblatex documentation does not literally say month (or year, where the situation is the same) is deprecated.
But the documentation of the year field ends with
It is however better to use the
datefield as this is compatible with plain years too and supports many more features.
and similarly the documentation for month says
It is however better to use the
datefield as this supports many more features.
To me that seems sufficient reason for JabRef to place both of these fields in the 'deprecated' section and prefer date instead when it is in biblatex mode.
It is unlikely that year and month will cease to work in biblatex, because that would be a backwards compatibility nightmare. But as far as I am concerned I'd definitely recommend date over year and month (if you don't need compatibility with classic BibTeX).
The next version of biblatex will have slightly more explicit advice on year/month vs date in the docs: https://github.com/plk/biblatex/commit/7d7c682f9ec7f06aadd4f176dcfcdadb9afe33ea
Depends on your definition of 'deprecated', I'd say. The biblatex documentation does not literally say month (or year, where the situation is the same) is deprecated.
But the documentation of the year field ends with
It is however better to use the
datefield as this is compatible with plain years too and supports many more features.
and similarly the documentation for month says
It is however better to use the
datefield as this supports many more features.
To me that seems sufficient reason for JabRef to place both of these fields in the 'deprecated' section and prefer date instead when it is in biblatex mode.
It is unlikely that year and month will cease to work in biblatex, because that would be a backwards compatibility nightmare. But as far as I am concerned I'd definitely recommend date over year and month (if you don't need compatibility with classic BibTeX).
The next version of biblatex will have slightly more explicit advice on year/month vs date in the docs: https://github.com/plk/biblatex/commit/7d7c682f9ec7f06aadd4f176dcfcdadb9afe33ea
edited Apr 7 at 10:13
answered Apr 7 at 9:54
moewemoewe
96.6k10118362
96.6k10118362
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483642%2fis-the-month-field-really-deprecated%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown