Problem searching some PDF files in Acrobat Reader – Non-ASCII characters

Question

Acrobat Reader cannot search some .pdf files.  I have put an example document up on Scribd here.
Any attempt to search for any word that can be clearly seen to be in the document fails with “No matches were found.”
This example document is NOT a scanned document – words and characters can be selected.
A hex display tool shows that the characters in a PDF document that can be successfully searched are in the ASCII/1252 range (A=0x41, etc).
Copying and pasting characters in the example document to a hex display tool shows that the characters in the document are not in the ASCII range.
For example the letters A to Z in the example document are in the range ‘A’ = 0xDF (decimal 223), ‘B’ = 0xDE (decimal 222), through to ‘Z’ = 0xC6 (decimal 198).
However, characters in these non-ASCII ranges are displayed perfectly by Acrobat Reader, as can be see if the example document is opened.
Therefore, as Acrobat Reader knows what these characters are, it doesn’t seem unreasonable to say that it should be able to search for and find them.
Tests were performed using Acrobat Reader X v10.1.4.
Can anyone say what this problem is?

Answer 1

Hi Pat, thanks for your reply. 
Your reference to the title of that page being 'HARNESSES' indicates that, when you view that document in Adobe Reader, you are seeing 'HARNESSES', not
"ØßÎÒÛÍÍÛÍ".  And that the remainder of the document is similarly being displayed in readable English language.
Yes as you say, you can search for 'ß' and get hits on 'A' (to use that as an example) in the example document.
But the need to form a word to be searched for into whatever code mapping this is using (for example having to enter "ØßÎÒÛÍÍ" for HARNESSES - I'm not even sure how that would be entered from a keyboard) doesn't seem to be very convenient.
Its clear the example document is using some code mapping other than ASCII / Windows-1252 (which has 'A' as 0x41).  But it is also clear that Adobe Reader knows what that mapping is, and knows to use it, as its displaying (for example) 'A' for the code 0xDF. 
So I guess the question is - why isn't Adobe Reader's knowledge of this mapping being extended to its search input?