Warning with footnotes: “name{Hfootnote.xx} has been referenced but does not exist”
First, some general details about my document: I'm using the scrbook
class and the hyperref
package. The document is split up into different source files (though this fact should not matter in this case).
I constantly get a warning for all of my footnotes (180 in total):
Document.tex:0. name{Hfootnote.xx} has been referenced but does not exist, replaced by a fixed one.
where the xx
is replaced by the number of the footnote in the compiled document and is running from 1 to 180 (in my case with 180 footnotes).
The numbering of the footnotes is correct and they appear in the compiled PDF as they should.
The only problem is, that the reference in the document is wrong. Clicking on the index of a footnote (in the text) always brings one to the very first page of the document.
What have I already tried/checked?
none of the footnotes is in a table or caption
numerous recompiling does not solve any of the warnings
some footnotes do contain
url{}
but by far not all
Does anybody have got some hints what else I should check?
hyperref footnotes warnings
add a comment |
First, some general details about my document: I'm using the scrbook
class and the hyperref
package. The document is split up into different source files (though this fact should not matter in this case).
I constantly get a warning for all of my footnotes (180 in total):
Document.tex:0. name{Hfootnote.xx} has been referenced but does not exist, replaced by a fixed one.
where the xx
is replaced by the number of the footnote in the compiled document and is running from 1 to 180 (in my case with 180 footnotes).
The numbering of the footnotes is correct and they appear in the compiled PDF as they should.
The only problem is, that the reference in the document is wrong. Clicking on the index of a footnote (in the text) always brings one to the very first page of the document.
What have I already tried/checked?
none of the footnotes is in a table or caption
numerous recompiling does not solve any of the warnings
some footnotes do contain
url{}
but by far not all
Does anybody have got some hints what else I should check?
hyperref footnotes warnings
1
Welcome to TeX.SX. I took the liberty to shorten the title a little bit, so that it fits better in the site layout.
– Martin Scharrer♦
Apr 20 '11 at 16:41
3
It would be very good if you add a minimal working example (MWE) that illustrates your problem, i.e. create a minimized version of your document which still shows the warnings. You can do this by making a copy and remove all unrelated text and packages. You might even find the cause during this, because often it is some incompatibility with some other package.
– Martin Scharrer♦
Apr 20 '11 at 16:43
1
Thank you @Martin. Ulrike's hint was somehow easier and faster ;) Nevertheless, the MWE-method you mentioned is worth a try for other problems.
– Torbjörn
Apr 20 '11 at 16:57
1
K.: Sure if you already found the error there is no need for that effort any longer. See the MWE link above for more tips.
– Martin Scharrer♦
Apr 20 '11 at 16:59
3
Although the problem was solved, I want to add something: "numerous recompiling does not solve any of the warnings": Sometimes it can also be helpful to delete the auxiliary files and then recompile.
– Stephen
Aug 12 '11 at 14:42
add a comment |
First, some general details about my document: I'm using the scrbook
class and the hyperref
package. The document is split up into different source files (though this fact should not matter in this case).
I constantly get a warning for all of my footnotes (180 in total):
Document.tex:0. name{Hfootnote.xx} has been referenced but does not exist, replaced by a fixed one.
where the xx
is replaced by the number of the footnote in the compiled document and is running from 1 to 180 (in my case with 180 footnotes).
The numbering of the footnotes is correct and they appear in the compiled PDF as they should.
The only problem is, that the reference in the document is wrong. Clicking on the index of a footnote (in the text) always brings one to the very first page of the document.
What have I already tried/checked?
none of the footnotes is in a table or caption
numerous recompiling does not solve any of the warnings
some footnotes do contain
url{}
but by far not all
Does anybody have got some hints what else I should check?
hyperref footnotes warnings
First, some general details about my document: I'm using the scrbook
class and the hyperref
package. The document is split up into different source files (though this fact should not matter in this case).
I constantly get a warning for all of my footnotes (180 in total):
Document.tex:0. name{Hfootnote.xx} has been referenced but does not exist, replaced by a fixed one.
where the xx
is replaced by the number of the footnote in the compiled document and is running from 1 to 180 (in my case with 180 footnotes).
The numbering of the footnotes is correct and they appear in the compiled PDF as they should.
The only problem is, that the reference in the document is wrong. Clicking on the index of a footnote (in the text) always brings one to the very first page of the document.
What have I already tried/checked?
none of the footnotes is in a table or caption
numerous recompiling does not solve any of the warnings
some footnotes do contain
url{}
but by far not all
Does anybody have got some hints what else I should check?
hyperref footnotes warnings
hyperref footnotes warnings
edited Apr 20 '11 at 16:39
Martin Scharrer♦
199k45633818
199k45633818
asked Apr 20 '11 at 16:34
TorbjörnTorbjörn
4011511
4011511
1
Welcome to TeX.SX. I took the liberty to shorten the title a little bit, so that it fits better in the site layout.
– Martin Scharrer♦
Apr 20 '11 at 16:41
3
It would be very good if you add a minimal working example (MWE) that illustrates your problem, i.e. create a minimized version of your document which still shows the warnings. You can do this by making a copy and remove all unrelated text and packages. You might even find the cause during this, because often it is some incompatibility with some other package.
– Martin Scharrer♦
Apr 20 '11 at 16:43
1
Thank you @Martin. Ulrike's hint was somehow easier and faster ;) Nevertheless, the MWE-method you mentioned is worth a try for other problems.
– Torbjörn
Apr 20 '11 at 16:57
1
K.: Sure if you already found the error there is no need for that effort any longer. See the MWE link above for more tips.
– Martin Scharrer♦
Apr 20 '11 at 16:59
3
Although the problem was solved, I want to add something: "numerous recompiling does not solve any of the warnings": Sometimes it can also be helpful to delete the auxiliary files and then recompile.
– Stephen
Aug 12 '11 at 14:42
add a comment |
1
Welcome to TeX.SX. I took the liberty to shorten the title a little bit, so that it fits better in the site layout.
– Martin Scharrer♦
Apr 20 '11 at 16:41
3
It would be very good if you add a minimal working example (MWE) that illustrates your problem, i.e. create a minimized version of your document which still shows the warnings. You can do this by making a copy and remove all unrelated text and packages. You might even find the cause during this, because often it is some incompatibility with some other package.
– Martin Scharrer♦
Apr 20 '11 at 16:43
1
Thank you @Martin. Ulrike's hint was somehow easier and faster ;) Nevertheless, the MWE-method you mentioned is worth a try for other problems.
– Torbjörn
Apr 20 '11 at 16:57
1
K.: Sure if you already found the error there is no need for that effort any longer. See the MWE link above for more tips.
– Martin Scharrer♦
Apr 20 '11 at 16:59
3
Although the problem was solved, I want to add something: "numerous recompiling does not solve any of the warnings": Sometimes it can also be helpful to delete the auxiliary files and then recompile.
– Stephen
Aug 12 '11 at 14:42
1
1
Welcome to TeX.SX. I took the liberty to shorten the title a little bit, so that it fits better in the site layout.
– Martin Scharrer♦
Apr 20 '11 at 16:41
Welcome to TeX.SX. I took the liberty to shorten the title a little bit, so that it fits better in the site layout.
– Martin Scharrer♦
Apr 20 '11 at 16:41
3
3
It would be very good if you add a minimal working example (MWE) that illustrates your problem, i.e. create a minimized version of your document which still shows the warnings. You can do this by making a copy and remove all unrelated text and packages. You might even find the cause during this, because often it is some incompatibility with some other package.
– Martin Scharrer♦
Apr 20 '11 at 16:43
It would be very good if you add a minimal working example (MWE) that illustrates your problem, i.e. create a minimized version of your document which still shows the warnings. You can do this by making a copy and remove all unrelated text and packages. You might even find the cause during this, because often it is some incompatibility with some other package.
– Martin Scharrer♦
Apr 20 '11 at 16:43
1
1
Thank you @Martin. Ulrike's hint was somehow easier and faster ;) Nevertheless, the MWE-method you mentioned is worth a try for other problems.
– Torbjörn
Apr 20 '11 at 16:57
Thank you @Martin. Ulrike's hint was somehow easier and faster ;) Nevertheless, the MWE-method you mentioned is worth a try for other problems.
– Torbjörn
Apr 20 '11 at 16:57
1
1
K.: Sure if you already found the error there is no need for that effort any longer. See the MWE link above for more tips.
– Martin Scharrer♦
Apr 20 '11 at 16:59
K.: Sure if you already found the error there is no need for that effort any longer. See the MWE link above for more tips.
– Martin Scharrer♦
Apr 20 '11 at 16:59
3
3
Although the problem was solved, I want to add something: "numerous recompiling does not solve any of the warnings": Sometimes it can also be helpful to delete the auxiliary files and then recompile.
– Stephen
Aug 12 '11 at 14:42
Although the problem was solved, I want to add something: "numerous recompiling does not solve any of the warnings": Sometimes it can also be helpful to delete the auxiliary files and then recompile.
– Stephen
Aug 12 '11 at 14:42
add a comment |
3 Answers
3
active
oldest
votes
Well the following works fine. So you should try to find out what your document is doing differently.
documentclass{scrbook}
usepackage{hyperref}
begin{document}
abcnewpage abcfootnote{blub}
end{document}
My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote.
1
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
3
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
1
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
add a comment |
I ran into a similar problem. Same warning, and same result (footnote links point always point to first page). Turns out, there’s some weird interaction between setspace
and hyperref
. The solution is to make sure setspace
is loaded before hyperref
:
documentclass{book}
usepackage{setspace}
usepackage{hyperref}
begin{document}
Hi.footnote{Yolo}
end{document}
Otherwise, if you swap the order, it will cause that same warning.
Note: bookmark
also uses hyperref
under the hood so a similar problem can arise even if you don’t use hyperref
explicitly.
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
add a comment |
I had this issue as well, so I went with the footnotemark[n]
where I placed the footnote, then later on in the document: footnotetext[n]{text}
.
I think it was because of the command I placed the footnote in, that it was not working as expected. Outside of the tabular
and textit
brackets, footnote
worked fine.
2
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
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%2f16268%2fwarning-with-footnotes-namehfootnote-xx-has-been-referenced-but-does-not-exi%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
Well the following works fine. So you should try to find out what your document is doing differently.
documentclass{scrbook}
usepackage{hyperref}
begin{document}
abcnewpage abcfootnote{blub}
end{document}
My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote.
1
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
3
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
1
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
add a comment |
Well the following works fine. So you should try to find out what your document is doing differently.
documentclass{scrbook}
usepackage{hyperref}
begin{document}
abcnewpage abcfootnote{blub}
end{document}
My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote.
1
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
3
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
1
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
add a comment |
Well the following works fine. So you should try to find out what your document is doing differently.
documentclass{scrbook}
usepackage{hyperref}
begin{document}
abcnewpage abcfootnote{blub}
end{document}
My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote.
Well the following works fine. So you should try to find out what your document is doing differently.
documentclass{scrbook}
usepackage{hyperref}
begin{document}
abcnewpage abcfootnote{blub}
end{document}
My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote.
answered Apr 20 '11 at 16:49
Ulrike FischerUlrike Fischer
188k7292673
188k7292673
1
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
3
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
1
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
add a comment |
1
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
3
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
1
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
1
1
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
Wow! Thank you a lot @Ulrike! That was the problem. I was loading hyperref prior to packages as fancyhdr, epstopdf and graphicx.
– Torbjörn
Apr 20 '11 at 16:55
3
3
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
"My guess is that you are not following the rule "load hyperref as the last package" and that something is redefining footnote" this was the clue that I found the problem in my code as well, I googled and came to this question and answer, thanks very much for you guys. I think an expert knowledge based on EXPERIENCE is always helpful.
– user11443
Feb 4 '12 at 4:19
1
1
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@Mammatt: thank your for your comment. It was posted as answer, so I converted it to a comment to Ulrike's answer. A Q&A site is different to forums, which work with threads.
– Stefan Kottwitz♦
Feb 4 '12 at 8:49
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
@UlrikeFischer: Load it before cleveref?
– user877329
Jul 25 '15 at 14:32
add a comment |
I ran into a similar problem. Same warning, and same result (footnote links point always point to first page). Turns out, there’s some weird interaction between setspace
and hyperref
. The solution is to make sure setspace
is loaded before hyperref
:
documentclass{book}
usepackage{setspace}
usepackage{hyperref}
begin{document}
Hi.footnote{Yolo}
end{document}
Otherwise, if you swap the order, it will cause that same warning.
Note: bookmark
also uses hyperref
under the hood so a similar problem can arise even if you don’t use hyperref
explicitly.
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
add a comment |
I ran into a similar problem. Same warning, and same result (footnote links point always point to first page). Turns out, there’s some weird interaction between setspace
and hyperref
. The solution is to make sure setspace
is loaded before hyperref
:
documentclass{book}
usepackage{setspace}
usepackage{hyperref}
begin{document}
Hi.footnote{Yolo}
end{document}
Otherwise, if you swap the order, it will cause that same warning.
Note: bookmark
also uses hyperref
under the hood so a similar problem can arise even if you don’t use hyperref
explicitly.
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
add a comment |
I ran into a similar problem. Same warning, and same result (footnote links point always point to first page). Turns out, there’s some weird interaction between setspace
and hyperref
. The solution is to make sure setspace
is loaded before hyperref
:
documentclass{book}
usepackage{setspace}
usepackage{hyperref}
begin{document}
Hi.footnote{Yolo}
end{document}
Otherwise, if you swap the order, it will cause that same warning.
Note: bookmark
also uses hyperref
under the hood so a similar problem can arise even if you don’t use hyperref
explicitly.
I ran into a similar problem. Same warning, and same result (footnote links point always point to first page). Turns out, there’s some weird interaction between setspace
and hyperref
. The solution is to make sure setspace
is loaded before hyperref
:
documentclass{book}
usepackage{setspace}
usepackage{hyperref}
begin{document}
Hi.footnote{Yolo}
end{document}
Otherwise, if you swap the order, it will cause that same warning.
Note: bookmark
also uses hyperref
under the hood so a similar problem can arise even if you don’t use hyperref
explicitly.
answered May 12 '17 at 2:01
RufflewindRufflewind
34447
34447
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
add a comment |
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
In my case, this was complicated by the fact that the documentclass loaded hyperref. Here is a workaround I found that doesn't require modifying the class: tex.stackexchange.com/a/462612/123144
– Zach Boyd
Dec 10 '18 at 18:33
add a comment |
I had this issue as well, so I went with the footnotemark[n]
where I placed the footnote, then later on in the document: footnotetext[n]{text}
.
I think it was because of the command I placed the footnote in, that it was not working as expected. Outside of the tabular
and textit
brackets, footnote
worked fine.
2
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
add a comment |
I had this issue as well, so I went with the footnotemark[n]
where I placed the footnote, then later on in the document: footnotetext[n]{text}
.
I think it was because of the command I placed the footnote in, that it was not working as expected. Outside of the tabular
and textit
brackets, footnote
worked fine.
2
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
add a comment |
I had this issue as well, so I went with the footnotemark[n]
where I placed the footnote, then later on in the document: footnotetext[n]{text}
.
I think it was because of the command I placed the footnote in, that it was not working as expected. Outside of the tabular
and textit
brackets, footnote
worked fine.
I had this issue as well, so I went with the footnotemark[n]
where I placed the footnote, then later on in the document: footnotetext[n]{text}
.
I think it was because of the command I placed the footnote in, that it was not working as expected. Outside of the tabular
and textit
brackets, footnote
worked fine.
edited Aug 15 '13 at 2:29
dustin
9,9361459162
9,9361459162
answered Aug 15 '13 at 2:19
NuclearPeonNuclearPeon
1413
1413
2
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
add a comment |
2
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
2
2
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format.
– texenthusiast
Aug 15 '13 at 5:44
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%2f16268%2fwarning-with-footnotes-namehfootnote-xx-has-been-referenced-but-does-not-exi%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
1
Welcome to TeX.SX. I took the liberty to shorten the title a little bit, so that it fits better in the site layout.
– Martin Scharrer♦
Apr 20 '11 at 16:41
3
It would be very good if you add a minimal working example (MWE) that illustrates your problem, i.e. create a minimized version of your document which still shows the warnings. You can do this by making a copy and remove all unrelated text and packages. You might even find the cause during this, because often it is some incompatibility with some other package.
– Martin Scharrer♦
Apr 20 '11 at 16:43
1
Thank you @Martin. Ulrike's hint was somehow easier and faster ;) Nevertheless, the MWE-method you mentioned is worth a try for other problems.
– Torbjörn
Apr 20 '11 at 16:57
1
K.: Sure if you already found the error there is no need for that effort any longer. See the MWE link above for more tips.
– Martin Scharrer♦
Apr 20 '11 at 16:59
3
Although the problem was solved, I want to add something: "numerous recompiling does not solve any of the warnings": Sometimes it can also be helpful to delete the auxiliary files and then recompile.
– Stephen
Aug 12 '11 at 14:42