The LDD SDK includes two bar code read packages: a premium Windows native package, and a lower-cost Java package. The following tables compare the details of each package:
Premium package | Value package | |
|---|---|---|
LDD script objects | ||
License fees | Required for each LDD server installation | Included in system cost |
Code | Windows native (.NET or COM) | Java |
Performance | Faster | Slower |
Solution template project | TestBarcodeRead | TestBCRead |
Ideal scan resolution | 300 dpi | 300 dpi |
Expected quality | Excellent, Good, Fair, or Poor | Interval between scanned pixel rows, 1–100 |
Reading from a specified zone | Yes | No |
Automatic detection of one-dimensional codes | Yes | No |
Checksum validation | Yes | Yes |
Fixed length | Yes | No |
Minimum length | Yes | No |
Page number | Yes | No |
Coordinates | Yes | Yes |
Multiple codes with directional sorting | Yes | Yes |
The LDD SDK includes two bar code write packages: a premium Windows native package, and an open source, Java-based Barbecue. The following tables compare the details of each package:
Premium | Barbecue | |
|---|---|---|
Codabar | Yes | Yes |
Code 25 | Yes | Yes |
Code 25 Interleaved | Yes | Yes |
Code 39 | Yes | Yes |
Code 93 | Yes | No |
Code 128 | Yes | Yes |
Code 128A | Yes | Yes |
Code 128B | Yes | Yes |
Code 128C | Yes | Yes |
EAN 8 | Yes | No |
EAN 8 + 2 | Yes | No |
EAN 8 + 5 | Yes | No |
EAN 13 | Yes | Yes |
EAN 13 + 2 | Yes | No |
EAN 13 + 5 (Bookland) | Yes | Yes |
GS1-128 (formerly UCC/EAN-128) Note: The GS-128 symbology is specified for the field using the constant | Yes | Yes |
GS1-DataMatrix | Yes | Yes |
ITF-14 | Yes | No |
POSTNET | Yes | Yes |
QR Code | Yes | No |
UPC-A | Yes | Yes |
UPC-E | Yes | No |
USPS Intelligent Mail | Yes | No |
Premium | Barbecue | |
|---|---|---|
PDF417 | Yes | No |
LDD optionally includes an optical character recognition (OCR) module to retrieve text from scanned documents, enabling them for searching, editing, and indexing. Entire documents, specific pages of documents, or specific areas of pages can be stored as text documents.
The following table lists the features of the OCR module:
Feature | Details |
|---|---|
Supported languages |
|
Dictionaries | Each language has one associated dictionary. The search order of language dictionaries can be configured in a script. |
Supported text types |
|
Supported input text size | 10 points–220 points |
Default output fonts | The following selections are made for default output fonts based on the input font:
Output fonts can be changed to any supported TrueType fonts within a script, after the OCR operation, and before the text is exported to a document. |
Zoning |
|
Available output formats |
|
Document color | Supported for input:
Supported for output:
|
Resolution | Input is accepted from documents scanned at 150–600 dpi. For best resolution, scan documents at 300 dpi. |
Image-processing capabilities | The following image-processing tasks are available:
|
The accuracy of the OCR module depends on the following original document factors:
Media type—More-reflective specialty media may result in poor-quality scanned images.
Document condition—Aged, wrinkled, or creased documents may result in poor-quality scanned images.
Document image quality—Low resolution or color depth of the scanned image or poor print quality in the scanned document may result in poor-quality scanned images.
Document alignment—Skewed or slightly rotated documents, such as pages fed through a misaligned ADF may cause difficulty in reading the scanned image.