I've read some of the similar questions - with $ being produced instead of £. I couldn't find anything that addresses the particular issue I'm currently having though...

LaTeX quite happily produces the £ symbol when I use \pounds. However, I had the need to search the resulting PDF document to track down where this symbol was used - and Adobe Reader's search function duly reported no instances of it, anywhere. On the other hand, if I search for $, it will find all instances of £ without any problems. Is this a known bug/feature (of LaTeX and/or Adobe Reader)? Is there anything I can do to overcome it? MWE below...


  • I don't have Adobe Reader, so can't check this. (It works fine in xpdf and evince.) But try \usepackage[T1]{fontenc}. – pst Apr 2 '14 at 10:37
  • 1
    @ArTourter --- I don't think this is a duplicate of the linked question. Moreover, your deleted answer fixes the problem on my machine. – Ian Thompson Apr 2 '14 at 10:38
  • @IanThompson I deleted my answer and pointed out to the duplicate since the problem and the answer are pretty much the same. the font is different, but the underlying problem is identical. – ArTourter Apr 2 '14 at 12:11
  • 1
    @ArTourter I voted to undelete your answer. Although the solution is the same, the symptoms are different enough to warrant a separate answer. – Andrew Swann Apr 2 '14 at 17:51

You should change the font encoding to T1 for this to work. Simply add


to your preamble

  • Thankyou, that works perfectly. Which leaves me now wondering why it is necessary. Is it a bug in LaTeX? If I type(set) a £ symbol (and more to the point, the £ symbol is what is 'printed'), why does it not get interpreted as such when I search the PDF document? – JustinT Apr 3 '14 at 20:39
  • 1
    This is not so much a bug as a caveat inherited due to historical reasons. There is a rather good explanation on wikibook about this (en.wikibooks.org/wiki/LaTeX/Fonts#Font_encoding). Basically, originally, LaTeX output was mostly postscript and the original encoding (OT1) was created so the output looked correct. The pdf format only came out later and with it new requirements. the encguide.pdf in your distro should also give you a more in depth idea of the concept of font encoding. – ArTourter Apr 3 '14 at 21:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.