I am writing a report and when I use the basic footnote command I get a strange 9 before the footnote number and the text. This happens for all the footnotes. I attach the picture in the link.

enter image description here

I just use \footnotemark and \footnotetext, but the same happens with \footnote.

Any ideas?





\alignauthor asdfasdf\\

\footnotetext[1]{footnote text \cite{asd} asdf.}

I realised that after removing the \usepackage{setspace} works again. Files:


closed as too localized by lockstep, zeroth, Martin Schröder, Claudio Fiandrino, diabonas Mar 23 '13 at 11:56

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Welcome to TeX.sx! Please add a minimal working example (MWE) that illustrates your problem. It will be much easier for us to reproduce your situation and find out what the issue is when we see compilable code, starting with \documentclass{...} and ending with \end{document}. – cyberSingularity Jan 21 '13 at 16:18
  • There is the example, and I attach both files (the cls file and the trial). – Ekhiotz Jan 21 '13 at 16:30
  • 2
    I get no strange number. Why are you splitting the footnote in the two parts? Just \footnote will do, in that case. And you probably don't need the optional argument to \footnotetext in any case. – egreg Jan 21 '13 at 16:54
  • Works for me even with \usepackage{setspace} and I get ^{1} footnote text [?] asdf. and not 9^{2}text for your example. – Stephen Jan 21 '13 at 18:23
  • We are not able to reproduce your problem, so it is hard to know what is causing it. Perhaps you could check your TeX distribution is up-to-date, and add the output of \listfiles in case it is caused by differing package versions, but I do not consider it likely. If removing setspace resolves things for you, do you really need to keep it? – cyberSingularity Jan 22 '13 at 0:09

Browse other questions tagged or ask your own question.