Protect names from being abbreviated
LaTeX thinks the name of organisations are first names, which are abbreviated using my bibliography style.
@Misc{BundesministeriumfuerUmwelt,
author = {Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)},
title = {Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {11.2016},}
Therefore comes out as
N. u.n.S. B. Bundesministerium für Umwelt, Klimaschutzplan 2050.
klimaschutzpolitische grundsätze und ziele der bundesregierung.
Using
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
How can the name be protected in a case like this?
Also, I would like to know if there is a simpler way of protecting the capitalizations of the references titles than putting everything in curly brackets.
biblatex ieee-style
add a comment |
LaTeX thinks the name of organisations are first names, which are abbreviated using my bibliography style.
@Misc{BundesministeriumfuerUmwelt,
author = {Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)},
title = {Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {11.2016},}
Therefore comes out as
N. u.n.S. B. Bundesministerium für Umwelt, Klimaschutzplan 2050.
klimaschutzpolitische grundsätze und ziele der bundesregierung.
Using
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
How can the name be protected in a case like this?
Also, I would like to know if there is a simpler way of protecting the capitalizations of the references titles than putting everything in curly brackets.
biblatex ieee-style
add a comment |
LaTeX thinks the name of organisations are first names, which are abbreviated using my bibliography style.
@Misc{BundesministeriumfuerUmwelt,
author = {Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)},
title = {Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {11.2016},}
Therefore comes out as
N. u.n.S. B. Bundesministerium für Umwelt, Klimaschutzplan 2050.
klimaschutzpolitische grundsätze und ziele der bundesregierung.
Using
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
How can the name be protected in a case like this?
Also, I would like to know if there is a simpler way of protecting the capitalizations of the references titles than putting everything in curly brackets.
biblatex ieee-style
LaTeX thinks the name of organisations are first names, which are abbreviated using my bibliography style.
@Misc{BundesministeriumfuerUmwelt,
author = {Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)},
title = {Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {11.2016},}
Therefore comes out as
N. u.n.S. B. Bundesministerium für Umwelt, Klimaschutzplan 2050.
klimaschutzpolitische grundsätze und ziele der bundesregierung.
Using
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
How can the name be protected in a case like this?
Also, I would like to know if there is a simpler way of protecting the capitalizations of the references titles than putting everything in curly brackets.
biblatex ieee-style
biblatex ieee-style
edited Mar 10 at 13:54
moewe
94k10115354
94k10115354
asked Mar 10 at 13:36
cheesuscheesus
275
275
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
So-called corporate authors need to be protected by a pair of curly braces to avoid that BibTeX or Biber tries to parse the name as the name of a person with family and given names. See Using a 'corporate author' in the "author" field of a bibliographic entry (spelling out the name in full). So you need
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
biblatex-ieee
applies sentence casing to some titles and so "Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung" will be converted to "Klimaschutzplan 2050. klimaschutzpolitische grundsätze und ziele der bundesregierung". The English rules of sentence case that biblatex
applies here make no sense of a German text, so the best we can do is tell biblatex
that this is a German title that should not need any case changes. This is done by adding
langid = {ngerman},
to the entry. In case you do have an English title where sentence casing should apply, but you need to protect a few proper names or acronyms from case change, you will, however, need curly braces again. See BibTeX loses capitals when creating .bbl file.
Finally, note that date = {11.2016},
is the wrong input format for date
-like fields. biblatex
expects date input in YYYY-MM-DD
format of ISO 8601. So
date = {2016-11},
would be the expected input.
Putting this all together
documentclass[british]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{bmu,
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
title = {Klimaschutzplan 2050},
subtitle = {Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {2016-11},
langid = {ngerman},
}
end{filecontents}
addbibresource{jobname.bib}
addbibresource{biblatex-examples.bib}
begin{document}
cite{sigfridsson,bmu}
printbibliography
end{document}
Note that BibTeX is considered a legacy backend now and that only Biber supports all of biblatex
's features. So you may want to consider switching from backend=bibtex
to backend=biber
. See Biblatex with Biber: Configuring my editor to avoid undefined citations for help on getting your editor to run Biber instead of BibTeX for you. bibtex vs. biber and biblatex vs. natbib has a bit of background, so does Question mark or bold citation key instead of citation number.
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%2f478732%2fprotect-names-from-being-abbreviated%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
So-called corporate authors need to be protected by a pair of curly braces to avoid that BibTeX or Biber tries to parse the name as the name of a person with family and given names. See Using a 'corporate author' in the "author" field of a bibliographic entry (spelling out the name in full). So you need
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
biblatex-ieee
applies sentence casing to some titles and so "Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung" will be converted to "Klimaschutzplan 2050. klimaschutzpolitische grundsätze und ziele der bundesregierung". The English rules of sentence case that biblatex
applies here make no sense of a German text, so the best we can do is tell biblatex
that this is a German title that should not need any case changes. This is done by adding
langid = {ngerman},
to the entry. In case you do have an English title where sentence casing should apply, but you need to protect a few proper names or acronyms from case change, you will, however, need curly braces again. See BibTeX loses capitals when creating .bbl file.
Finally, note that date = {11.2016},
is the wrong input format for date
-like fields. biblatex
expects date input in YYYY-MM-DD
format of ISO 8601. So
date = {2016-11},
would be the expected input.
Putting this all together
documentclass[british]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{bmu,
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
title = {Klimaschutzplan 2050},
subtitle = {Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {2016-11},
langid = {ngerman},
}
end{filecontents}
addbibresource{jobname.bib}
addbibresource{biblatex-examples.bib}
begin{document}
cite{sigfridsson,bmu}
printbibliography
end{document}
Note that BibTeX is considered a legacy backend now and that only Biber supports all of biblatex
's features. So you may want to consider switching from backend=bibtex
to backend=biber
. See Biblatex with Biber: Configuring my editor to avoid undefined citations for help on getting your editor to run Biber instead of BibTeX for you. bibtex vs. biber and biblatex vs. natbib has a bit of background, so does Question mark or bold citation key instead of citation number.
add a comment |
So-called corporate authors need to be protected by a pair of curly braces to avoid that BibTeX or Biber tries to parse the name as the name of a person with family and given names. See Using a 'corporate author' in the "author" field of a bibliographic entry (spelling out the name in full). So you need
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
biblatex-ieee
applies sentence casing to some titles and so "Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung" will be converted to "Klimaschutzplan 2050. klimaschutzpolitische grundsätze und ziele der bundesregierung". The English rules of sentence case that biblatex
applies here make no sense of a German text, so the best we can do is tell biblatex
that this is a German title that should not need any case changes. This is done by adding
langid = {ngerman},
to the entry. In case you do have an English title where sentence casing should apply, but you need to protect a few proper names or acronyms from case change, you will, however, need curly braces again. See BibTeX loses capitals when creating .bbl file.
Finally, note that date = {11.2016},
is the wrong input format for date
-like fields. biblatex
expects date input in YYYY-MM-DD
format of ISO 8601. So
date = {2016-11},
would be the expected input.
Putting this all together
documentclass[british]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{bmu,
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
title = {Klimaschutzplan 2050},
subtitle = {Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {2016-11},
langid = {ngerman},
}
end{filecontents}
addbibresource{jobname.bib}
addbibresource{biblatex-examples.bib}
begin{document}
cite{sigfridsson,bmu}
printbibliography
end{document}
Note that BibTeX is considered a legacy backend now and that only Biber supports all of biblatex
's features. So you may want to consider switching from backend=bibtex
to backend=biber
. See Biblatex with Biber: Configuring my editor to avoid undefined citations for help on getting your editor to run Biber instead of BibTeX for you. bibtex vs. biber and biblatex vs. natbib has a bit of background, so does Question mark or bold citation key instead of citation number.
add a comment |
So-called corporate authors need to be protected by a pair of curly braces to avoid that BibTeX or Biber tries to parse the name as the name of a person with family and given names. See Using a 'corporate author' in the "author" field of a bibliographic entry (spelling out the name in full). So you need
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
biblatex-ieee
applies sentence casing to some titles and so "Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung" will be converted to "Klimaschutzplan 2050. klimaschutzpolitische grundsätze und ziele der bundesregierung". The English rules of sentence case that biblatex
applies here make no sense of a German text, so the best we can do is tell biblatex
that this is a German title that should not need any case changes. This is done by adding
langid = {ngerman},
to the entry. In case you do have an English title where sentence casing should apply, but you need to protect a few proper names or acronyms from case change, you will, however, need curly braces again. See BibTeX loses capitals when creating .bbl file.
Finally, note that date = {11.2016},
is the wrong input format for date
-like fields. biblatex
expects date input in YYYY-MM-DD
format of ISO 8601. So
date = {2016-11},
would be the expected input.
Putting this all together
documentclass[british]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{bmu,
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
title = {Klimaschutzplan 2050},
subtitle = {Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {2016-11},
langid = {ngerman},
}
end{filecontents}
addbibresource{jobname.bib}
addbibresource{biblatex-examples.bib}
begin{document}
cite{sigfridsson,bmu}
printbibliography
end{document}
Note that BibTeX is considered a legacy backend now and that only Biber supports all of biblatex
's features. So you may want to consider switching from backend=bibtex
to backend=biber
. See Biblatex with Biber: Configuring my editor to avoid undefined citations for help on getting your editor to run Biber instead of BibTeX for you. bibtex vs. biber and biblatex vs. natbib has a bit of background, so does Question mark or bold citation key instead of citation number.
So-called corporate authors need to be protected by a pair of curly braces to avoid that BibTeX or Biber tries to parse the name as the name of a person with family and given names. See Using a 'corporate author' in the "author" field of a bibliographic entry (spelling out the name in full). So you need
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
biblatex-ieee
applies sentence casing to some titles and so "Klimaschutzplan 2050. Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung" will be converted to "Klimaschutzplan 2050. klimaschutzpolitische grundsätze und ziele der bundesregierung". The English rules of sentence case that biblatex
applies here make no sense of a German text, so the best we can do is tell biblatex
that this is a German title that should not need any case changes. This is done by adding
langid = {ngerman},
to the entry. In case you do have an English title where sentence casing should apply, but you need to protect a few proper names or acronyms from case change, you will, however, need curly braces again. See BibTeX loses capitals when creating .bbl file.
Finally, note that date = {11.2016},
is the wrong input format for date
-like fields. biblatex
expects date input in YYYY-MM-DD
format of ISO 8601. So
date = {2016-11},
would be the expected input.
Putting this all together
documentclass[british]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[backend=bibtex, style=ieee,doi=false,isbn=false,url=false]{biblatex}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{bmu,
author = {{Bundesministerium für Umwelt, Naturschutz und nukleare Sicherheit (BMU)}},
title = {Klimaschutzplan 2050},
subtitle = {Klimaschutzpolitische Grundsätze und Ziele der Bundesregierung},
date = {2016-11},
langid = {ngerman},
}
end{filecontents}
addbibresource{jobname.bib}
addbibresource{biblatex-examples.bib}
begin{document}
cite{sigfridsson,bmu}
printbibliography
end{document}
Note that BibTeX is considered a legacy backend now and that only Biber supports all of biblatex
's features. So you may want to consider switching from backend=bibtex
to backend=biber
. See Biblatex with Biber: Configuring my editor to avoid undefined citations for help on getting your editor to run Biber instead of BibTeX for you. bibtex vs. biber and biblatex vs. natbib has a bit of background, so does Question mark or bold citation key instead of citation number.
answered Mar 10 at 13:53
moewemoewe
94k10115354
94k10115354
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%2f478732%2fprotect-names-from-being-abbreviated%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