Undefined control sequence. datalist etc
I am currently writing my bachelor thesis and have to use latex for it. In the past I have never used latex in my whole life. Still things running good but I have to use latexdiff with the --flatten parameter, which is working great it dumps all the differences between two versions of my thesis into a single file.
On compiling there sadly is a problem with citations, latexdiff converts my literature database .db file into an inline datalist. But this datalist can't be compiled, because for some strange reason latex doesn't know the commands.
Errors like:
Undefined control sequence. datalist
Undefined control sequence. entry
Undefined control sequence. name
appearing in the log.
The file is generated automatically by latexdiff, so I don't expect any errors in there, unless there is some bug in latexdiff?
I am using biblatex:
usepackage[backend=bibtex]{biblatex}
For managing latex package versions I am using MiKTeX 2.9 and I updated all packages today, so every package is using the newest version.
Can anyone please help me what I am doing wrong?
biblatex bibtex citing
asked Feb 14 at 20:42
Dominik KDominik K
2015
add a comment |
I am currently writing my bachelor thesis and have to use latex for it. In the past I have never used latex in my whole life. Still things running good but I have to use latexdiff with the --flatten parameter, which is working great it dumps all the differences between two versions of my thesis into a single file.
On compiling there sadly is a problem with citations, latexdiff converts my literature database .db file into an inline datalist. But this datalist can't be compiled, because for some strange reason latex doesn't know the commands.
Errors like:
Undefined control sequence. datalist
Undefined control sequence. entry
Undefined control sequence. name
appearing in the log.
The file is generated automatically by latexdiff, so I don't expect any errors in there, unless there is some bug in latexdiff?
I am using biblatex:
usepackage[backend=bibtex]{biblatex}
For managing latex package versions I am using MiKTeX 2.9 and I updated all packages today, so every package is using the newest version.
Can anyone please help me what I am doing wrong?
biblatex bibtex citing
asked Feb 14 at 20:42
Dominik KDominik K
2015
2
datalist and the other command are only defined locally when the bbl is read.
– Ulrike Fischer
Feb 14 at 21:40
@Ulrike Fischer So this is nothing which should be put into a .tex file?
– Dominik K
Feb 14 at 22:07
No, outside of the bbl it doesn't make sense.
– Ulrike Fischer
Feb 14 at 22:26
add a comment |
I am currently writing my bachelor thesis and have to use latex for it. In the past I have never used latex in my whole life. Still things running good but I have to use latexdiff with the --flatten parameter, which is working great it dumps all the differences between two versions of my thesis into a single file.
On compiling there sadly is a problem with citations, latexdiff converts my literature database .db file into an inline datalist. But this datalist can't be compiled, because for some strange reason latex doesn't know the commands.
Errors like:
Undefined control sequence. datalist
Undefined control sequence. entry
Undefined control sequence. name
appearing in the log.
The file is generated automatically by latexdiff, so I don't expect any errors in there, unless there is some bug in latexdiff?
I am using biblatex:
usepackage[backend=bibtex]{biblatex}
For managing latex package versions I am using MiKTeX 2.9 and I updated all packages today, so every package is using the newest version.
Can anyone please help me what I am doing wrong?
biblatex bibtex citing
asked Feb 14 at 20:42
Dominik KDominik K
2015
I am currently writing my bachelor thesis and have to use latex for it. In the past I have never used latex in my whole life. Still things running good but I have to use latexdiff with the --flatten parameter, which is working great it dumps all the differences between two versions of my thesis into a single file.
On compiling there sadly is a problem with citations, latexdiff converts my literature database .db file into an inline datalist. But this datalist can't be compiled, because for some strange reason latex doesn't know the commands.
Errors like:
Undefined control sequence. datalist
Undefined control sequence. entry
Undefined control sequence. name
appearing in the log.
The file is generated automatically by latexdiff, so I don't expect any errors in there, unless there is some bug in latexdiff?
I am using biblatex:
usepackage[backend=bibtex]{biblatex}
For managing latex package versions I am using MiKTeX 2.9 and I updated all packages today, so every package is using the newest version.
Can anyone please help me what I am doing wrong?
biblatex bibtex citing
biblatex bibtex citing
asked Feb 14 at 20:42
Dominik KDominik K
2015
asked Feb 14 at 20:42
Dominik KDominik K
2015
asked Feb 14 at 20:42
Dominik KDominik K
2015
asked Feb 14 at 20:42
Dominik KDominik K
2015
asked Feb 14 at 20:42
Dominik KDominik K
2015
2015
2
datalist and the other command are only defined locally when the bbl is read.
– Ulrike Fischer
Feb 14 at 21:40
@Ulrike Fischer So this is nothing which should be put into a .tex file?
– Dominik K
Feb 14 at 22:07
No, outside of the bbl it doesn't make sense.
– Ulrike Fischer
Feb 14 at 22:26
add a comment |
2
datalist and the other command are only defined locally when the bbl is read.
– Ulrike Fischer
Feb 14 at 21:40
@Ulrike Fischer So this is nothing which should be put into a .tex file?
– Dominik K
Feb 14 at 22:07
No, outside of the bbl it doesn't make sense.
– Ulrike Fischer
Feb 14 at 22:26
2
2
datalist and the other command are only defined locally when the bbl is read.
– Ulrike Fischer
Feb 14 at 21:40
datalist and the other command are only defined locally when the bbl is read.
– Ulrike Fischer
Feb 14 at 21:40
@Ulrike Fischer So this is nothing which should be put into a .tex file?
– Dominik K
Feb 14 at 22:07
@Ulrike Fischer So this is nothing which should be put into a .tex file?
– Dominik K
Feb 14 at 22:07
No, outside of the bbl it doesn't make sense.
– Ulrike Fischer
Feb 14 at 22:26
No, outside of the bbl it doesn't make sense.
– Ulrike Fischer
Feb 14 at 22:26
add a comment |
1 Answer
1
active
oldest
votes
latexdiff's --flatten option does not only flatten input and include, it also writes the .bbl file into the document. That works well for BibTeX-based bibliographies, where the .bbl file contains code that can be typeset directly at the place where bibliography is issued. But it does not work for biblatex, where the .bbl contains the entry data in a machine-readable, but not typesettable format, and where the file is loaded at a particular point at the beginning of the document and not just where bibliography is placed.
It is possible to include biblatex's .bbl into a .tex file, but it requires a bit of extra work (see for example Biblatex: submitting to a journal) and I would say that it is in general not worth the effort.
Until latexdiff becomes aware of biblatex and handles it differently, you can do one of the following things
- Ignore the fact that the
.bblbit in the diff output is not compilable. Review it in the source before you compile the diff file and then comment it out. - Use
addbibresource{<filename>.bib}instead ofbibliography{<filename>}.latexdiffdoes not recognise thebiblatexcommand and does not try to input the.bblthere.
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
@DominikK I rejected the edit removing the.bibfile extension fromaddbibresource, because the extension is required with that command (as opposed tobibliographywhere the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.
– moewe
Feb 15 at 12:23
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
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%2f474940%2fundefined-control-sequence-datalist-etc%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
latexdiff's --flatten option does not only flatten input and include, it also writes the .bbl file into the document. That works well for BibTeX-based bibliographies, where the .bbl file contains code that can be typeset directly at the place where bibliography is issued. But it does not work for biblatex, where the .bbl contains the entry data in a machine-readable, but not typesettable format, and where the file is loaded at a particular point at the beginning of the document and not just where bibliography is placed.
It is possible to include biblatex's .bbl into a .tex file, but it requires a bit of extra work (see for example Biblatex: submitting to a journal) and I would say that it is in general not worth the effort.
Until latexdiff becomes aware of biblatex and handles it differently, you can do one of the following things
- Ignore the fact that the
.bblbit in the diff output is not compilable. Review it in the source before you compile the diff file and then comment it out. - Use
addbibresource{<filename>.bib}instead ofbibliography{<filename>}.latexdiffdoes not recognise thebiblatexcommand and does not try to input the.bblthere.
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
@DominikK I rejected the edit removing the.bibfile extension fromaddbibresource, because the extension is required with that command (as opposed tobibliographywhere the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.
– moewe
Feb 15 at 12:23
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
add a comment |
latexdiff's --flatten option does not only flatten input and include, it also writes the .bbl file into the document. That works well for BibTeX-based bibliographies, where the .bbl file contains code that can be typeset directly at the place where bibliography is issued. But it does not work for biblatex, where the .bbl contains the entry data in a machine-readable, but not typesettable format, and where the file is loaded at a particular point at the beginning of the document and not just where bibliography is placed.
It is possible to include biblatex's .bbl into a .tex file, but it requires a bit of extra work (see for example Biblatex: submitting to a journal) and I would say that it is in general not worth the effort.
Until latexdiff becomes aware of biblatex and handles it differently, you can do one of the following things
- Ignore the fact that the
.bblbit in the diff output is not compilable. Review it in the source before you compile the diff file and then comment it out. - Use
addbibresource{<filename>.bib}instead ofbibliography{<filename>}.latexdiffdoes not recognise thebiblatexcommand and does not try to input the.bblthere.
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
@DominikK I rejected the edit removing the.bibfile extension fromaddbibresource, because the extension is required with that command (as opposed tobibliographywhere the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.
– moewe
Feb 15 at 12:23
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
add a comment |
latexdiff's --flatten option does not only flatten input and include, it also writes the .bbl file into the document. That works well for BibTeX-based bibliographies, where the .bbl file contains code that can be typeset directly at the place where bibliography is issued. But it does not work for biblatex, where the .bbl contains the entry data in a machine-readable, but not typesettable format, and where the file is loaded at a particular point at the beginning of the document and not just where bibliography is placed.
It is possible to include biblatex's .bbl into a .tex file, but it requires a bit of extra work (see for example Biblatex: submitting to a journal) and I would say that it is in general not worth the effort.
Until latexdiff becomes aware of biblatex and handles it differently, you can do one of the following things
- Ignore the fact that the
.bblbit in the diff output is not compilable. Review it in the source before you compile the diff file and then comment it out. - Use
addbibresource{<filename>.bib}instead ofbibliography{<filename>}.latexdiffdoes not recognise thebiblatexcommand and does not try to input the.bblthere.
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
latexdiff's --flatten option does not only flatten input and include, it also writes the .bbl file into the document. That works well for BibTeX-based bibliographies, where the .bbl file contains code that can be typeset directly at the place where bibliography is issued. But it does not work for biblatex, where the .bbl contains the entry data in a machine-readable, but not typesettable format, and where the file is loaded at a particular point at the beginning of the document and not just where bibliography is placed.
It is possible to include biblatex's .bbl into a .tex file, but it requires a bit of extra work (see for example Biblatex: submitting to a journal) and I would say that it is in general not worth the effort.
Until latexdiff becomes aware of biblatex and handles it differently, you can do one of the following things
- Ignore the fact that the
.bblbit in the diff output is not compilable. Review it in the source before you compile the diff file and then comment it out. - Use
addbibresource{<filename>.bib}instead ofbibliography{<filename>}.latexdiffdoes not recognise thebiblatexcommand and does not try to input the.bblthere.
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
answered Feb 15 at 6:59
moewemoewe
91.6k10114346
91.6k10114346
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
@DominikK I rejected the edit removing the.bibfile extension fromaddbibresource, because the extension is required with that command (as opposed tobibliographywhere the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.
– moewe
Feb 15 at 12:23
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
add a comment |
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
@DominikK I rejected the edit removing the.bibfile extension fromaddbibresource, because the extension is required with that command (as opposed tobibliographywhere the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.
– moewe
Feb 15 at 12:23
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
I am a bit dissappointed that latex has no better way to really view all the diffs between two revsions. Microsoft Word is a lot more powerful in this matter. But thanks for the good solution I hope my professor will accecpt this way.
– Dominik K
Feb 15 at 12:21
@DominikK I rejected the edit removing the
.bib file extension from addbibresource, because the extension is required with that command (as opposed to bibliography where the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.– moewe
Feb 15 at 12:23
@DominikK I rejected the edit removing the
.bib file extension from addbibresource, because the extension is required with that command (as opposed to bibliography where the file extension must not be given). On some systems it may work without the extension, but that is only accidental and not guaranteed.– moewe
Feb 15 at 12:23
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
Ok you are the boss, thanks again.
– Dominik K
Feb 15 at 12:24
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%2f474940%2fundefined-control-sequence-datalist-etc%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
datalist and the other command are only defined locally when the bbl is read.
– Ulrike Fischer
Feb 14 at 21:40
@Ulrike Fischer So this is nothing which should be put into a .tex file?
– Dominik K
Feb 14 at 22:07
No, outside of the bbl it doesn't make sense.
– Ulrike Fischer
Feb 14 at 22:26