Is the month field really deprecated?
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
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
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
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
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
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
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 20 hours ago
Jonas SteinJonas Stein
3,34142746
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
asked 20 hours ago
Jonas SteinJonas Stein
3,34142746
3,34142746
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
answered 20 hours ago
moewemoewe
96.5k10118362
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
answered 20 hours ago
moewemoewe
96.5k10118362
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
answered 20 hours ago
moewemoewe
96.5k10118362
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
answered 20 hours ago
moewemoewe
96.5k10118362
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
answered 20 hours ago
moewemoewe
96.5k10118362
edited 19 hours ago
answered 20 hours ago
moewemoewe
96.5k10118362
answered 20 hours ago
moewemoewe
96.5k10118362
answered 20 hours ago
moewemoewe
96.5k10118362
96.5k10118362
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
