Incorrect Code128 BarCode Being Read From Faxed Document

This seems to be a very similar post to Post #281358. I am using a Code128 barcode on a PDF Report. Our business process is that the report is e-mailed to someone off-site, and then it is faxed back in at a later point in time. When we receive the fax attachment on our end and run it through the barcode recognition process, we receive an invalid barcode.

We expect to receive CodeText: 07606060103

But instead we receive CodeText: 0760606010q

The obvious variable here is the Fax Machine. We're not always guaranteed 100% perfect clarity coming back on an inbound fax, expecially when the off-site machine sending the fax can be old and less than sufficient.

Is there anything we can do from a programming perspective to ensure that our BarCodeReader object is reading the correct CodeText from the barcode?

Please see the attached zip for before-fax and after-fax versions of our reports.

We're using: Version 3.9.0

I appreciate your prompt response!

Hi,


Thank you for inquiry.

I just saw the sample code in the last post. Could you please modify the setting hints part as below?

reader.SetHints(RecognitionHints.ImageBinarizationHints.Grayscale
| RecognitionHints.ThresholdHints.AutoCalculateByImage
| RecognitionHints.ImageAccessHints.Exclusive);

| operator should be used to combine multiple recognition hints. After setting hints as above, I was able to get the correct codetext from the barcode.

Hello,

I modified the setting hints as described above, but I am still unable to successfully read the barcode.

I expect to receive the CodeText: 07606060103

But instead I receive the CodeText: 0760606010q

Can you please use the attached PDF and try your test again? I look forward to your prompt response.

Again, we're using version 3.9.0.

Thanks,

Mike

Hi Mike,


Yes, the attached PDF document also gave the expected codetext value “07606060103”.

I have also attached my test application here for your reference.

Thanks for following up, Saqib. Your code sample helped me correct a few items on my end. I'm going to run through a bit more testing on my end with a variation of 100+ unique barcodes to ensure that they are all identified correctly. I'll check back soon. In the meantime, please leave this issue open.

Thanks,

Mike