Lexmark CX622 Forms and Bar Code Card P4.2 Technical Reference - Page 135

Appendix F - Deviations, Code 93 uppercase vs. lowercase, Codabar uppercase vs. lowercase, Maximum

Get Lexmark CX622 PDF manuals and user guides View all Lexmark CX622 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 135 highlights

Lexmark Confidential until announced Appendix F - Deviations 135 Appendix F - Deviations Code 93 uppercase vs. lowercase The Forms and Bar Code Card firmware converts any Code 93 lowercase input to uppercase before submission to the BCE. This firmware generates the proper uppercase characters within the bar code. Notes: • The Code 93 bar code uses the same encoding as Code 39. • HP BarDIMM Pro and Forms and Bar Code Card convert lowercase "a" to "z" character input to uppercase, and the bar code scan contains only uppercase. • The HRT is printed as lowercase, reflecting the input data, rather than the actual bar code encoded data. • The BCE does not support lowercase "a" to "z" character input, does not convert to uppercase, and operates according to the specifications noted previously. Codabar uppercase vs. lowercase The Forms and Bar Code Card firmware converts any Codabar lowercase start and stop input to uppercase before submission to the BCE. This firmware generates the proper uppercase start and stop bar code characters. Notes: • The Codabar bar code uses two bar and space widths-narrow and double-wide. The single narrow inter-character space separates each character that contains exactly four bars and three spaces. Due to the encoding, each bar code character width may vary slightly depending on the character being encoded. A single start and stop brackets the numeric data encoded within the bar code. • HP BarDIMM Pro and Forms and Bar Code Card convert lowercase start and stop character input to uppercase. The bar code image is encoded with uppercase characters for the start and stop characters. • The HRT start and stop characters are printed as lowercase, reflecting the input data, rather than the actual bar code encoded data. • The BCE does not support lowercase "a" to "z" start and stop character input, and does not convert to uppercase. It also does not operate according to the specifications noted previously. Maximum encodable character length The BCE allocates memory for a requested bar code on a per-symbology basis. It does not allocate memory on a symbol-by-symbol basis as it builds the bar code. Rather, it allocates the entire memory block needed at once for each bar code it generates. It uses this technique to reduce the overhead of memory allocation and ensure good performance. Because the BCE allocates a finite amount of memory per bar code, input data with a large amount of encodable data generates a garbled bar code image. The image does not have well-formed bars and spaces, or sometimes, the data generates a code 19 NotEnoughMemory error.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
Appendix F - Deviations
Code 93 uppercase vs. lowercase
The Forms and Bar Code Card firmware converts any Code 93 lowercase input to uppercase before submission
to the BCE. This firmware generates the proper uppercase characters within the bar code.
Notes:
•
The Code 93 bar code uses the same encoding as Code 39.
•
HP BarDIMM Pro and Forms and Bar Code Card convert lowercase “a” to “z” character input to
uppercase, and the bar code scan contains only uppercase.
•
The HRT is printed as lowercase, reflecting the input data, rather than the actual bar code encoded data.
•
The BCE does not support lowercase “a” to “z” character input, does not convert to uppercase, and
operates according to the specifications noted previously.
Codabar uppercase vs. lowercase
The Forms and Bar Code Card firmware converts any Codabar lowercase start and stop input to uppercase
before submission to the BCE. This firmware generates the proper uppercase start and stop bar code
characters.
Notes:
•
The Codabar bar code uses two bar and space widths—narrow and double-wide. The single narrow
inter-character space separates each character that contains exactly four bars and three spaces. Due to
the encoding, each bar code character width may vary slightly depending on the character being
encoded. A single start and stop brackets the numeric data encoded within the bar code.
•
HP BarDIMM Pro and Forms and Bar Code Card convert lowercase start and stop character input to
uppercase. The bar code image is encoded with uppercase characters for the start and stop characters.
•
The HRT start and stop characters are printed as lowercase, reflecting the input data, rather than the
actual bar code encoded data.
•
The BCE does not support lowercase "a" to "z" start and stop character input, and does not convert to
uppercase. It also does not operate according to the specifications noted previously.
Maximum encodable character length
The BCE allocates memory for a requested bar code on a per-symbology basis. It does not allocate memory
on a symbol-by-symbol basis as it builds the bar code. Rather, it allocates the entire memory block needed at
once for each bar code it generates. It uses this technique to reduce the overhead of memory allocation and
ensure good performance.
Because the BCE allocates a finite amount of memory per bar code, input data with a large amount of encodable
data generates a garbled bar code image. The image does not have well-formed bars and spaces, or sometimes,
the data generates a
code 19 NotEnoughMemory
error.
Lexmark Confidential until announced
Appendix F - Deviations
135