As the toolkit scans the images in a document, it assigns a “hit-count” to each barcode-like pattern it finds. The hit-count for a very clear barcode will typically be in the region 20 to 100, depending on the size of the barcode and the settings used within the sdk. The PrefOccurrence and MinOccurrence properties specify hit-count levels
2-D barcode formats such as PDF-417 can encode a huge character set, which means that the barcode reader toolkit needs to encode characters outside the normal ASCII range. If the Encoding property is set to 2 then the toolkit will use Unicode encoding, whereby characters can be represented by the string &#N; where N is
UPC-A barcodes are a subset of EAN-13. For example, the UPC-A barcode “016000336100” is the same as the EAN-13 barcode “0016000336100”. In fact, UPC-A barcodes are the sub-set of EAN-13 barcodes that start with a 0. The ReadEAN13 property controls whether any barcodes of type EAN-13 are recognized – and this includes UPC-A, whether or
The SkewTolerance property is used for the detection of barcodes in skewed documents, but it can have a negative impact on the performance of the ScanBarCode command, especially when reading PDf-417 and Datamatrix barcodes. One solution to this problem is to use xml settings, which allow you to store sets of properties which are applied
This document explains how the properties of the toolkit can effect the speed at which PDF documents are processed. The PDF extension allows you to read barcodes from PDF documents. Version 7.4.1 or later… Version 7.4.1 introduced a faster and more accurate method of processing image-only PDF documents (e.g, a PDF document generated as the