[Kleon]

You do realize that a text search on the WH_LFCOLB.pdf comes up with zero results for any text. Right?

OCR doesn't necessarily mean the resulting document is searchable. The software "reads" text and other elements, but what it does to them is up to the user. Making the document searchable doesn't make much sense unless the text is clear and crisp to begin with, which isn't the case here.

[Triple]

oh the ole - OCR that does not produce searchable text...right!

Why didn’t I think of that?

Mac does have an optimize for OCR scan feature - it just does NOTHING like what showed up in the WH_LFCOLB.pdf. (I have tried it several times on similar documents.)

Care to demonstrate what you speculate is happening?

[DiogenesLamp]

OCR doesn't necessarily mean the resulting document is searchable. The software "reads" text and other elements, but what it does to them is up to the user. Making the document searchable doesn't make much sense unless the text is clear and crisp to begin with, which isn't the case here.

If the application is normally used for the searching of an existing database of image files for the purpose of making copies or fabricating new replacement documents, it is reasonable to believe someone might make use of the text searching feature. What is not reasonable, is to believe there is any good explanation for changing pixel size and dynamic range from one character to another. The only reasonable conclusion is that the output document accurately represents the input image files.