We often receive emails suggesting that the SDK is outputting incorrect characters at the start or end of a Codabar barcode. This is normally down to confusion over how codabar characters should be interpreted at the end of a barcode….<\/p>\n
Codabar barcodes can start and end with with of 4 patterns:<\/p>\n
<\/p>\n
bars 0100, Spaces 011 = a or A or t or T<\/p>\n
Bars 0001, Spaces 110 = b or B or n or N<\/p>\n
Bars 0001, Spaces 011 = c or C or *<\/p>\n
Bars 0010, Spaces 011 = d or D or e or E<\/p>\n
<\/p>\n
The SDK has the policy of using “a” or “b” or “c” or “d” at the start and “t” or “n” or “*” or “e” at the end, but this behavior can be changed through use of the ShowCodabarStartStop property…<\/p>\n
0 = Don’t display start\/stop characters<\/p>\n
1 =\u00a0Use “a” or “b” or “c” or “d” at the start and “t” or “n” or “*” or “e” at the end (default)<\/p>\n
2 =\u00a0Use “A” or “B” or “C” or “D” at the start and “T” or “N” or “*” or “E” at the end<\/p>\n
3 =\u00a0Use “A” or “B” or “C” or “D” at the start and end.<\/p>\n
<\/p>\n
So if you have a Codabar barcode that has the printed text A12345A underneath then the following values of\u00a0ShowCodabarStartStop will output the text….<\/p>\n
0 = 12345<\/p>\n
1 = a12345t<\/p>\n
2 = A12345T<\/p>\n
3 = A12345A<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
We often receive emails suggesting that the SDK is outputting incorrect characters at the start or end of a Codabar barcode. This is normally down to confusion over how codabar characters should be interpreted at the end of a barcode…. Codabar barcodes can start and end with with of 4 patterns: bars 0100, Spaces<\/p>\n