Biber/BibLaTeX printbibliography causes “undefined control sequence” in the proceeding line
up vote
8
down vote
favorite
I'm using biblatex with biber as the backend to write my document. Without printbibliography, all the citations work perfectly well, and appear in the document, so I assume that my bibliography.bib file is fine. The problem comes, however, when I include the line printbibliography at the end of my document (just before end{document}): suddenly every time I try to compile I get "undefined control sequence" referencing whatever line is after printbibliography.
Following suggestions elsewhere on the internet, I combed my document for "smart" quotation marks, and other weird characters, but there aren't any. My citations are downloaded from ADSABS, with the occasional @ONLINE resource, too. As I said, though, all the references work fine, it's just the printbibliography command that bails.
To illustrate (I'm not going to paste the entire document here unless someone thinks it will be helpful):
usepackage[style=authoryear-icomp,sorting=anyt]{biblatex}
addbibresource{bibliography.bib}
...
printbibliography
biblatex errors biber
edited Apr 26 '15 at 18:53
lockstep
189k52585719
asked Mar 27 '14 at 12:56
GTF
191117
add a comment |
up vote
8
down vote
favorite
I'm using biblatex with biber as the backend to write my document. Without printbibliography, all the citations work perfectly well, and appear in the document, so I assume that my bibliography.bib file is fine. The problem comes, however, when I include the line printbibliography at the end of my document (just before end{document}): suddenly every time I try to compile I get "undefined control sequence" referencing whatever line is after printbibliography.
Following suggestions elsewhere on the internet, I combed my document for "smart" quotation marks, and other weird characters, but there aren't any. My citations are downloaded from ADSABS, with the occasional @ONLINE resource, too. As I said, though, all the references work fine, it's just the printbibliography command that bails.
To illustrate (I'm not going to paste the entire document here unless someone thinks it will be helpful):
usepackage[style=authoryear-icomp,sorting=anyt]{biblatex}
addbibresource{bibliography.bib}
...
printbibliography
biblatex errors biber
edited Apr 26 '15 at 18:53
lockstep
189k52585719
asked Mar 27 '14 at 12:56
GTF
191117
2
Welcome to TeX.SX! Please make your code compilable (if possible), or at least complete it withdocumentclass{...}, the requiredusepackage's,begin{document}, andend{document}. That may seem tedious to you, but think of the extra work it represents for TeX.SX users willing to give you a hand. Help them help you: remove that one hurdle between you and a solution to your problem.
– Benedikt Bauer
Mar 27 '14 at 13:44
1
i'd start by looking at the.bblfile to make sure nothing is wrong there -- all brace groups closed, that sort of thing, and also, whether the control sequence cited as "undefined" occurs in that file.
– barbara beeton
Mar 27 '14 at 14:01
1
Normally ifbiblatexfails atprintbibliographyit's not abiblatexproblem but a problem with the.bibfile. The problem does not become apparent in the citations though because not all entry fields are evaluated at cite-time. A MWE (and the error message: which command?) would greatly help us find the problem. In searching for it you might very well find out where the problem lies yourself. (Try for example only to cite one entry from the.bibfile and print the bibliography, if that works that entry is not the culprit, try another one).
– moewe
Mar 27 '14 at 14:13
So @moewe I took your advice and made an MWE at gist.github.com/gfarrell/9892791. I've copied my document's original preamble exactly. I've included a citation for every bib entry. This MWE doesn't die onprintbibliography, but it doesn't properly cite anything either. All the citations are just printed as the citation keys, and the references section isn't populated (see compiled PDF here: cl.ly/2f1e3T243o1n). I've tried multiple runs but no cigar. It seems I can't even create a proper MWE...
– GTF
Mar 31 '14 at 13:59
(OK, ignore the problem with the MWE, Biber was throwing a hissy fit - fixed using bit.ly/1gHp3Bm) I'll go through the citations to see what breaks.
– GTF
Mar 31 '14 at 14:10
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I'm using biblatex with biber as the backend to write my document. Without printbibliography, all the citations work perfectly well, and appear in the document, so I assume that my bibliography.bib file is fine. The problem comes, however, when I include the line printbibliography at the end of my document (just before end{document}): suddenly every time I try to compile I get "undefined control sequence" referencing whatever line is after printbibliography.
Following suggestions elsewhere on the internet, I combed my document for "smart" quotation marks, and other weird characters, but there aren't any. My citations are downloaded from ADSABS, with the occasional @ONLINE resource, too. As I said, though, all the references work fine, it's just the printbibliography command that bails.
To illustrate (I'm not going to paste the entire document here unless someone thinks it will be helpful):
usepackage[style=authoryear-icomp,sorting=anyt]{biblatex}
addbibresource{bibliography.bib}
...
printbibliography
biblatex errors biber
edited Apr 26 '15 at 18:53
lockstep
189k52585719
asked Mar 27 '14 at 12:56
GTF
191117
I'm using biblatex with biber as the backend to write my document. Without printbibliography, all the citations work perfectly well, and appear in the document, so I assume that my bibliography.bib file is fine. The problem comes, however, when I include the line printbibliography at the end of my document (just before end{document}): suddenly every time I try to compile I get "undefined control sequence" referencing whatever line is after printbibliography.
Following suggestions elsewhere on the internet, I combed my document for "smart" quotation marks, and other weird characters, but there aren't any. My citations are downloaded from ADSABS, with the occasional @ONLINE resource, too. As I said, though, all the references work fine, it's just the printbibliography command that bails.
To illustrate (I'm not going to paste the entire document here unless someone thinks it will be helpful):
usepackage[style=authoryear-icomp,sorting=anyt]{biblatex}
addbibresource{bibliography.bib}
...
printbibliography
biblatex errors biber
biblatex errors biber
edited Apr 26 '15 at 18:53
lockstep
189k52585719
asked Mar 27 '14 at 12:56
GTF
191117
edited Apr 26 '15 at 18:53
lockstep
189k52585719
asked Mar 27 '14 at 12:56
GTF
191117
edited Apr 26 '15 at 18:53
lockstep
189k52585719
edited Apr 26 '15 at 18:53
lockstep
189k52585719
edited Apr 26 '15 at 18:53
lockstep
189k52585719
189k52585719
asked Mar 27 '14 at 12:56
GTF
191117
asked Mar 27 '14 at 12:56
GTF
191117
asked Mar 27 '14 at 12:56
GTF
191117
191117
2
Welcome to TeX.SX! Please make your code compilable (if possible), or at least complete it withdocumentclass{...}, the requiredusepackage's,begin{document}, andend{document}. That may seem tedious to you, but think of the extra work it represents for TeX.SX users willing to give you a hand. Help them help you: remove that one hurdle between you and a solution to your problem.
– Benedikt Bauer
Mar 27 '14 at 13:44
1
i'd start by looking at the.bblfile to make sure nothing is wrong there -- all brace groups closed, that sort of thing, and also, whether the control sequence cited as "undefined" occurs in that file.
– barbara beeton
Mar 27 '14 at 14:01
1
Normally ifbiblatexfails atprintbibliographyit's not abiblatexproblem but a problem with the.bibfile. The problem does not become apparent in the citations though because not all entry fields are evaluated at cite-time. A MWE (and the error message: which command?) would greatly help us find the problem. In searching for it you might very well find out where the problem lies yourself. (Try for example only to cite one entry from the.bibfile and print the bibliography, if that works that entry is not the culprit, try another one).
– moewe
Mar 27 '14 at 14:13
So @moewe I took your advice and made an MWE at gist.github.com/gfarrell/9892791. I've copied my document's original preamble exactly. I've included a citation for every bib entry. This MWE doesn't die onprintbibliography, but it doesn't properly cite anything either. All the citations are just printed as the citation keys, and the references section isn't populated (see compiled PDF here: cl.ly/2f1e3T243o1n). I've tried multiple runs but no cigar. It seems I can't even create a proper MWE...
– GTF
Mar 31 '14 at 13:59
(OK, ignore the problem with the MWE, Biber was throwing a hissy fit - fixed using bit.ly/1gHp3Bm) I'll go through the citations to see what breaks.
– GTF
Mar 31 '14 at 14:10
add a comment |
2
Welcome to TeX.SX! Please make your code compilable (if possible), or at least complete it withdocumentclass{...}, the requiredusepackage's,begin{document}, andend{document}. That may seem tedious to you, but think of the extra work it represents for TeX.SX users willing to give you a hand. Help them help you: remove that one hurdle between you and a solution to your problem.
– Benedikt Bauer
Mar 27 '14 at 13:44
1
i'd start by looking at the.bblfile to make sure nothing is wrong there -- all brace groups closed, that sort of thing, and also, whether the control sequence cited as "undefined" occurs in that file.
– barbara beeton
Mar 27 '14 at 14:01
1
Normally ifbiblatexfails atprintbibliographyit's not abiblatexproblem but a problem with the.bibfile. The problem does not become apparent in the citations though because not all entry fields are evaluated at cite-time. A MWE (and the error message: which command?) would greatly help us find the problem. In searching for it you might very well find out where the problem lies yourself. (Try for example only to cite one entry from the.bibfile and print the bibliography, if that works that entry is not the culprit, try another one).
– moewe
Mar 27 '14 at 14:13
So @moewe I took your advice and made an MWE at gist.github.com/gfarrell/9892791. I've copied my document's original preamble exactly. I've included a citation for every bib entry. This MWE doesn't die onprintbibliography, but it doesn't properly cite anything either. All the citations are just printed as the citation keys, and the references section isn't populated (see compiled PDF here: cl.ly/2f1e3T243o1n). I've tried multiple runs but no cigar. It seems I can't even create a proper MWE...
– GTF
Mar 31 '14 at 13:59
(OK, ignore the problem with the MWE, Biber was throwing a hissy fit - fixed using bit.ly/1gHp3Bm) I'll go through the citations to see what breaks.
– GTF
Mar 31 '14 at 14:10
2
2
Welcome to TeX.SX! Please make your code compilable (if possible), or at least complete it with
documentclass{...}, the required usepackage's, begin{document}, and end{document}. That may seem tedious to you, but think of the extra work it represents for TeX.SX users willing to give you a hand. Help them help you: remove that one hurdle between you and a solution to your problem.– Benedikt Bauer
Mar 27 '14 at 13:44
Welcome to TeX.SX! Please make your code compilable (if possible), or at least complete it with
documentclass{...}, the required usepackage's, begin{document}, and end{document}. That may seem tedious to you, but think of the extra work it represents for TeX.SX users willing to give you a hand. Help them help you: remove that one hurdle between you and a solution to your problem.– Benedikt Bauer
Mar 27 '14 at 13:44
1
1
i'd start by looking at the
.bbl file to make sure nothing is wrong there -- all brace groups closed, that sort of thing, and also, whether the control sequence cited as "undefined" occurs in that file.– barbara beeton
Mar 27 '14 at 14:01
i'd start by looking at the
.bbl file to make sure nothing is wrong there -- all brace groups closed, that sort of thing, and also, whether the control sequence cited as "undefined" occurs in that file.– barbara beeton
Mar 27 '14 at 14:01
1
1
Normally if
biblatex fails at printbibliography it's not a biblatex problem but a problem with the .bib file. The problem does not become apparent in the citations though because not all entry fields are evaluated at cite-time. A MWE (and the error message: which command?) would greatly help us find the problem. In searching for it you might very well find out where the problem lies yourself. (Try for example only to cite one entry from the .bib file and print the bibliography, if that works that entry is not the culprit, try another one).– moewe
Mar 27 '14 at 14:13
Normally if
biblatex fails at printbibliography it's not a biblatex problem but a problem with the .bib file. The problem does not become apparent in the citations though because not all entry fields are evaluated at cite-time. A MWE (and the error message: which command?) would greatly help us find the problem. In searching for it you might very well find out where the problem lies yourself. (Try for example only to cite one entry from the .bib file and print the bibliography, if that works that entry is not the culprit, try another one).– moewe
Mar 27 '14 at 14:13
So @moewe I took your advice and made an MWE at gist.github.com/gfarrell/9892791. I've copied my document's original preamble exactly. I've included a citation for every bib entry. This MWE doesn't die on
printbibliography, but it doesn't properly cite anything either. All the citations are just printed as the citation keys, and the references section isn't populated (see compiled PDF here: cl.ly/2f1e3T243o1n). I've tried multiple runs but no cigar. It seems I can't even create a proper MWE...– GTF
Mar 31 '14 at 13:59
So @moewe I took your advice and made an MWE at gist.github.com/gfarrell/9892791. I've copied my document's original preamble exactly. I've included a citation for every bib entry. This MWE doesn't die on
printbibliography, but it doesn't properly cite anything either. All the citations are just printed as the citation keys, and the references section isn't populated (see compiled PDF here: cl.ly/2f1e3T243o1n). I've tried multiple runs but no cigar. It seems I can't even create a proper MWE...– GTF
Mar 31 '14 at 13:59
(OK, ignore the problem with the MWE, Biber was throwing a hissy fit - fixed using bit.ly/1gHp3Bm) I'll go through the citations to see what breaks.
– GTF
Mar 31 '14 at 14:10
(OK, ignore the problem with the MWE, Biber was throwing a hissy fit - fixed using bit.ly/1gHp3Bm) I'll go through the citations to see what breaks.
– GTF
Mar 31 '14 at 14:10
add a comment |
3 Answers
3
active
oldest
votes
up vote
7
down vote
I had a similar issue. I pinpointed the problem to be in the .bib file. My advice is to carefully examine your .bib file for possible
ambiguous syntax. In my case, the problematic syntax was:
...
title = {A 70~kW stationary fuel cell system},
...
The undefined control sequence issue was resolved, when this was changed to the following (i.e., the expression with the tilde was enclosed in the curly braces):
...
title = {A {70~kW} stationary fuel cell system},
...
A short comment (maybe someone will find it useful). In my case, the issue occurred after the matlab-prettifier package was loaded, which also loads the listings package. Until these packages were load, I had experienced no issues whatsoever.
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
add a comment |
up vote
5
down vote
accepted
The problem in the bibliography.bib file (https://gist.github.com/gfarrell/9892791) was an undefined control sequence after all: ADSABS inserts control sequences for journals like aap.
Removing these and replacing them with the actual journal names fixes the problem.
(If anyone knows a package that defines all of these it would be quite helpful).
answered Mar 31 '14 at 14:16
GTF
191117
2
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
add a comment |
up vote
0
down vote
I had the same problem from a bibtex entry which was imported by DOI (using Jabref).
In one article's title there was a {textquotesingle} included. This caused biblatex to break.
After removing it, the compilation worked again.
answered Dec 7 at 14:14
loki
17018
1
In a short test I ran{textquotesingle}seemed to work in thetitlefield if comped with Biber (indeed Biber converts it to{'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if thetextcompis not loaded, sincetextquotesingleis not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.
– moewe
Dec 7 at 14:37
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
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',
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%2f168023%2fbiber-biblatex-printbibliography-causes-undefined-control-sequence-in-the-pro%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
I had a similar issue. I pinpointed the problem to be in the .bib file. My advice is to carefully examine your .bib file for possible
ambiguous syntax. In my case, the problematic syntax was:
...
title = {A 70~kW stationary fuel cell system},
...
The undefined control sequence issue was resolved, when this was changed to the following (i.e., the expression with the tilde was enclosed in the curly braces):
...
title = {A {70~kW} stationary fuel cell system},
...
A short comment (maybe someone will find it useful). In my case, the issue occurred after the matlab-prettifier package was loaded, which also loads the listings package. Until these packages were load, I had experienced no issues whatsoever.
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
add a comment |
up vote
7
down vote
I had a similar issue. I pinpointed the problem to be in the .bib file. My advice is to carefully examine your .bib file for possible
ambiguous syntax. In my case, the problematic syntax was:
...
title = {A 70~kW stationary fuel cell system},
...
The undefined control sequence issue was resolved, when this was changed to the following (i.e., the expression with the tilde was enclosed in the curly braces):
...
title = {A {70~kW} stationary fuel cell system},
...
A short comment (maybe someone will find it useful). In my case, the issue occurred after the matlab-prettifier package was loaded, which also loads the listings package. Until these packages were load, I had experienced no issues whatsoever.
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
add a comment |
up vote
7
down vote
up vote
7
down vote
I had a similar issue. I pinpointed the problem to be in the .bib file. My advice is to carefully examine your .bib file for possible
ambiguous syntax. In my case, the problematic syntax was:
...
title = {A 70~kW stationary fuel cell system},
...
The undefined control sequence issue was resolved, when this was changed to the following (i.e., the expression with the tilde was enclosed in the curly braces):
...
title = {A {70~kW} stationary fuel cell system},
...
A short comment (maybe someone will find it useful). In my case, the issue occurred after the matlab-prettifier package was loaded, which also loads the listings package. Until these packages were load, I had experienced no issues whatsoever.
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
I had a similar issue. I pinpointed the problem to be in the .bib file. My advice is to carefully examine your .bib file for possible
ambiguous syntax. In my case, the problematic syntax was:
...
title = {A 70~kW stationary fuel cell system},
...
The undefined control sequence issue was resolved, when this was changed to the following (i.e., the expression with the tilde was enclosed in the curly braces):
...
title = {A {70~kW} stationary fuel cell system},
...
A short comment (maybe someone will find it useful). In my case, the issue occurred after the matlab-prettifier package was loaded, which also loads the listings package. Until these packages were load, I had experienced no issues whatsoever.
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
edited Apr 26 '15 at 22:11
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
answered Apr 26 '15 at 17:53
Andrej Debenjak
30134
30134
add a comment |
add a comment |
up vote
5
down vote
accepted
The problem in the bibliography.bib file (https://gist.github.com/gfarrell/9892791) was an undefined control sequence after all: ADSABS inserts control sequences for journals like aap.
Removing these and replacing them with the actual journal names fixes the problem.
(If anyone knows a package that defines all of these it would be quite helpful).
answered Mar 31 '14 at 14:16
GTF
191117
2
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
add a comment |
up vote
5
down vote
accepted
The problem in the bibliography.bib file (https://gist.github.com/gfarrell/9892791) was an undefined control sequence after all: ADSABS inserts control sequences for journals like aap.
Removing these and replacing them with the actual journal names fixes the problem.
(If anyone knows a package that defines all of these it would be quite helpful).
answered Mar 31 '14 at 14:16
GTF
191117
2
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
The problem in the bibliography.bib file (https://gist.github.com/gfarrell/9892791) was an undefined control sequence after all: ADSABS inserts control sequences for journals like aap.
Removing these and replacing them with the actual journal names fixes the problem.
(If anyone knows a package that defines all of these it would be quite helpful).
answered Mar 31 '14 at 14:16
GTF
191117
The problem in the bibliography.bib file (https://gist.github.com/gfarrell/9892791) was an undefined control sequence after all: ADSABS inserts control sequences for journals like aap.
Removing these and replacing them with the actual journal names fixes the problem.
(If anyone knows a package that defines all of these it would be quite helpful).
answered Mar 31 '14 at 14:16
GTF
191117
answered Mar 31 '14 at 14:16
GTF
191117
answered Mar 31 '14 at 14:16
GTF
191117
answered Mar 31 '14 at 14:16
GTF
191117
191117
2
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
add a comment |
2
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
2
2
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
Another possible cause, which I experienced after switching from bibtex to biblatex, is the use of fancy quotes (') and hyphens (-). After replacing these with plain text the errors went away.
– jsaven
Dec 6 '16 at 10:57
add a comment |
up vote
0
down vote
I had the same problem from a bibtex entry which was imported by DOI (using Jabref).
In one article's title there was a {textquotesingle} included. This caused biblatex to break.
After removing it, the compilation worked again.
answered Dec 7 at 14:14
loki
17018
1
In a short test I ran{textquotesingle}seemed to work in thetitlefield if comped with Biber (indeed Biber converts it to{'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if thetextcompis not loaded, sincetextquotesingleis not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.
– moewe
Dec 7 at 14:37
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
add a comment |
up vote
0
down vote
I had the same problem from a bibtex entry which was imported by DOI (using Jabref).
In one article's title there was a {textquotesingle} included. This caused biblatex to break.
After removing it, the compilation worked again.
answered Dec 7 at 14:14
loki
17018
1
In a short test I ran{textquotesingle}seemed to work in thetitlefield if comped with Biber (indeed Biber converts it to{'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if thetextcompis not loaded, sincetextquotesingleis not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.
– moewe
Dec 7 at 14:37
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the same problem from a bibtex entry which was imported by DOI (using Jabref).
In one article's title there was a {textquotesingle} included. This caused biblatex to break.
After removing it, the compilation worked again.
answered Dec 7 at 14:14
loki
17018
I had the same problem from a bibtex entry which was imported by DOI (using Jabref).
In one article's title there was a {textquotesingle} included. This caused biblatex to break.
After removing it, the compilation worked again.
answered Dec 7 at 14:14
loki
17018
answered Dec 7 at 14:14
loki
17018
answered Dec 7 at 14:14
loki
17018
answered Dec 7 at 14:14
loki
17018
17018
1
In a short test I ran{textquotesingle}seemed to work in thetitlefield if comped with Biber (indeed Biber converts it to{'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if thetextcompis not loaded, sincetextquotesingleis not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.
– moewe
Dec 7 at 14:37
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
add a comment |
1
In a short test I ran{textquotesingle}seemed to work in thetitlefield if comped with Biber (indeed Biber converts it to{'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if thetextcompis not loaded, sincetextquotesingleis not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.
– moewe
Dec 7 at 14:37
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
1
1
In a short test I ran
{textquotesingle} seemed to work in the title field if comped with Biber (indeed Biber converts it to {'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if the textcomp is not loaded, since textquotesingle is not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.– moewe
Dec 7 at 14:37
In a short test I ran
{textquotesingle} seemed to work in the title field if comped with Biber (indeed Biber converts it to {'}, which may or may not be a good idea). If compiled with BibTeX, the command is not converted and may be reported as unknown if the textcomp is not loaded, since textquotesingle is not defined in the LaTeX kernel for all encodings, see tex.stackexchange.com/q/202166/35864.– moewe
Dec 7 at 14:37
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
Thanks for the effort. I did not check for missing packages.
– loki
Dec 7 at 14:40
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f168023%2fbiber-biblatex-printbibliography-causes-undefined-control-sequence-in-the-pro%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
2
Welcome to TeX.SX! Please make your code compilable (if possible), or at least complete it with
documentclass{...}, the requiredusepackage's,begin{document}, andend{document}. That may seem tedious to you, but think of the extra work it represents for TeX.SX users willing to give you a hand. Help them help you: remove that one hurdle between you and a solution to your problem.– Benedikt Bauer
Mar 27 '14 at 13:44
1
i'd start by looking at the
.bblfile to make sure nothing is wrong there -- all brace groups closed, that sort of thing, and also, whether the control sequence cited as "undefined" occurs in that file.– barbara beeton
Mar 27 '14 at 14:01
1
Normally if
biblatexfails atprintbibliographyit's not abiblatexproblem but a problem with the.bibfile. The problem does not become apparent in the citations though because not all entry fields are evaluated at cite-time. A MWE (and the error message: which command?) would greatly help us find the problem. In searching for it you might very well find out where the problem lies yourself. (Try for example only to cite one entry from the.bibfile and print the bibliography, if that works that entry is not the culprit, try another one).– moewe
Mar 27 '14 at 14:13
So @moewe I took your advice and made an MWE at gist.github.com/gfarrell/9892791. I've copied my document's original preamble exactly. I've included a citation for every bib entry. This MWE doesn't die on
printbibliography, but it doesn't properly cite anything either. All the citations are just printed as the citation keys, and the references section isn't populated (see compiled PDF here: cl.ly/2f1e3T243o1n). I've tried multiple runs but no cigar. It seems I can't even create a proper MWE...– GTF
Mar 31 '14 at 13:59
(OK, ignore the problem with the MWE, Biber was throwing a hissy fit - fixed using bit.ly/1gHp3Bm) I'll go through the citations to see what breaks.
– GTF
Mar 31 '14 at 14:10