Is the month field really deprecated?biblatex month fieldDisable month in biblatex bibliography?How to not...
A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?
Why don't electron-positron collisions release infinite energy?
Basic combinations logic doubt in probability
Relation between Frobenius, spectral norm and sum of maxima
What would happen to a modern skyscraper if it rains micro blackholes?
Is the month field really deprecated?
Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)
Why can't I see bouncing of a switch on an oscilloscope?
Do VLANs within a subnet need to have their own subnet for router on a stick?
How does one intimidate enemies without having the capacity for violence?
What defenses are there against being summoned by the Gate spell?
XeLaTeX and pdfLaTeX ignore hyphenation
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Why was the small council so happy for Tyrion to become the Master of Coin?
Has the BBC provided arguments for saying Brexit being cancelled is unlikely?
Explain the parameters before and after @ in the treminal
"which" command doesn't work / path of Safari?
Animated Series: Alien black spider robot crashes on Earth
If Manufacturer spice model and Datasheet give different values which should I use?
If two metric spaces are topologically equivalent (homeomorphic) imply that they are complete?
N.B. ligature in Latex
Can I interfere when another PC is about to be attacked?
Modeling an IPv4 Address
How long does it take to type this?
Is the month field really deprecated?
biblatex 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
asked 8 hours ago
Jonas SteinJonas Stein
3,32442746
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 8 hours ago
Jonas SteinJonas Stein
3,32442746
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 8 hours ago
Jonas SteinJonas Stein
3,32442746
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 8 hours ago
Jonas SteinJonas Stein
3,32442746
asked 8 hours ago
Jonas SteinJonas Stein
3,32442746
asked 8 hours ago
Jonas SteinJonas Stein
3,32442746
asked 8 hours ago
Jonas SteinJonas Stein
3,32442746
asked 8 hours ago
Jonas SteinJonas Stein
3,32442746
3,32442746
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 7 hours ago
moewemoewe
96.4k10117361
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 7 hours ago
moewemoewe
96.4k10117361
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 7 hours ago
moewemoewe
96.4k10117361
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 7 hours ago
moewemoewe
96.4k10117361
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 7 hours ago
moewemoewe
96.4k10117361
edited 7 hours ago
answered 7 hours ago
moewemoewe
96.4k10117361
answered 7 hours ago
moewemoewe
96.4k10117361
answered 7 hours ago
moewemoewe
96.4k10117361
96.4k10117361
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
