Text incorrectly interpreted as EAN8 barcode

Aspose.BarCode Product Family
1

Even at the HighQuality setting, Aspose is interpreting text in the attached image as being an EAN8 barcode

barcode_rasterized_alt.png.trimmed.png (7.9 KB)

I’ve marked the area in red that it seems to be “scanning” during this process. Seems like a bug…

barcode_ecd1ecbe-a3f0-4904-9aa6-d52d86660bf5_EAN8_22922311_1d199e62-b67b-4f63-b218-5c01bd1e323c_cropped.png (2.5 KB)

In total, Aspose finds 3 “barcodes” in this file, when it should only have found two: a DataMatrix and an EAN13.

2

@sferda,

We will evaluate your issue and get back to you soon.

3

@sferda,

I was able to reproduce the issue as you mentioned by using your barcode image with the following sample code:
e.g.
Sample code:

 var bmp1 = "g:\\test2\\barcode_rasterized_alt.png.trimmed.png";
using (Aspose.BarCode.BarCodeRecognition.BarCodeReader reader1 = new Aspose.BarCode.BarCodeRecognition.BarCodeReader(bmp1, Aspose.BarCode.BarCodeRecognition.DecodeType.AllSupportedTypes))
{
    Console.WriteLine(reader1.ReadBarCodes().Length);//3

    foreach (Aspose.BarCode.BarCodeRecognition.BarCodeResult result1 in reader1.ReadBarCodes())
    {
        // Read symbology type and code text
        Console.WriteLine("Symbology Type: " + result1.CodeType);
        Console.WriteLine("CodeText: " + result1.CodeText);
    }
}

output:

Symbology Type: DataMatrix
CodeText: 21061374
Symbology Type: EAN8
CodeText: 22922311
Symbology Type: EAN13
CodeText: 8700216004718

We need to evaluate your issue in details. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): BARCODENET-38821

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

4

Is there an ETA to this issue being addressed?

5

This is fake recognition because text sometimes is recognized as barcode. The problem is related with weak checksum in EAN/UPCA barcodes. We will update our fake detector engine, but it is not critical task and these tasks is fixed immediately only if they come from Paid Support.