BARCODEDATA

typedef struct tagBarCodeData 
{ 
   L_UINT uStructSize; 
   L_INT nGroup; 
   L_UINT32 ulType; 
   L_INT nUnits; 
   RECT rcBarLocation; 
   L_INT nSizeofBarCodeData; 
   L_CHAR * pszBarCodeData; 
   L_INT nIndexDuplicate; 
   L_INT nTotalCount; 
   L_INT nDupCount; 
   L_UINT uFlags; 
   L_UINT uDataCode; 
   L_INT nAngle; 
} BARCODEDATA,* pBARCODEDATA; 

This structure contains barcode information.

Comments

This structure will be filled by LBarCode::Read when reading in barcode information.

You can also fill this structure before calling LBarCode::Write to print the barcode symbol on the bitmap.

There is no limitation on the barcode angle, i.e. all angles can be detected,( whereas the deskew command is limited to +/- 20 degrees). It is very useful to detect the document image skew angle to correct the image angle. Provide this angle to deskew the image or rotate the image in the reverse direction.

Australian post barcode strings have a special format to distinguish different fields (i.e. FCC, DPID, and CIF). The string format puts dashes between fields as follows:  FCC-DIPD-CIF, where FCC is a 2-digit field (valid values are 11, 87, 45, 92, 59, 62, and 44), DPID is an 8-digit field representing the address, and CIF (optional) represents the customer information field. For more information, please refer to the standard. This string format applies to both reading and writing.

GS1 Databar (formerly RSS14) Expanded and Expanded Stacked strings need to be written conforming to a string format that indicates a particular encoding method, such as Method 1, Method 0100, or Method 0101. For example, suppose a string (01)00012345678905(10)ABC123 is encoded using Method 1  (i.e. General Identification Data). In this example the 14th digit of the item identification number (jn this case, "5"), if it exists, is considered as a check digit and is ignored. A string that is written without following any of these special encoding formats will be encoded by Method 00 (i.e. General Purpose Data).

When read, an extra digit in curly brackets (i.e. { and }) is added to indicate the linkage bit at the beginning of the string. The curly brackets are not part of the encoded barcode data, and they are not defined in the standard. Rather, they distinguish the linkage digit from other data. For example, if a barcode is written with string (01)00012345678905(10)ABC123 while the linkage bit is set to zero, the read function result will be {0}(01)00012345678905(10)ABC123, where {0} is the linkage digit and the remaining characters are the barcode data.

For a table containing information useful when writing 1D barcode data see https://www.leadtools.com/sdk/barcode/1d-chart.