Lexmark X925 Forms and Bar Code Card Technical Reference Guide - Page 71

Human-readable text, Compressed data formats, Checksum calculation, FontName

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

Page 71 highlights

This currentpoint positioning is applicable with or without accompanying human-readable text and also considers any specified quiet zones to be within the bounding box. Human-readable text Human-readable text can be specified with one-dimensional bar codes under the following provisions: • The typeface to be used is specified with the /FontName key. • The specified text is automatically centered on the bar code. • Text is automatically scaled based on the width and height of the bar code and on the method of embedding used. Because two-dimensional bar codes are capable of encoding thousands of characters, human-readable interpretation of the data may not be practical. Alternatively, descriptive text rather than literal text may be printed with the symbol. If printed, any character size and font available may be selected, and the text may be printed anywhere desired near the symbol. The text must not interfere with the bar code symbol or its quiet zones. Compressed data formats Some bar code symbologies, such as UPC-E and Code 128, use compressed data formats. The Forms and Bar Code Card accepts data for these symbologies in either compressed or uncompressed format. The incoming data is analyzed to determine if it is compressed or not, and if required, compression is automatically performed before printing the bar code. Checksum calculation Some bar code symbologies define checksum characters as a requirement of the data format. When this is the case, the Forms and Bar Code Card performs the checksum calculation and automatically places the character(s) per the symbology specifications. Fixed length data formats can be sent with or without checksum characters. PostScript emulation 68

  • 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
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
PostScript emulation
68
This currentpoint positioning is applicable with or without accompanying human-readable text and
also considers any specified quiet zones to be within the bounding box.
Human-readable text
Human-readable text can be specified with one-dimensional bar codes under the following
provisions:
•
The typeface to be used is specified with the
/FontName
key.
•
The specified text is automatically centered on the bar code.
•
Text is automatically scaled based on the width and height of the bar code and on the method
of embedding used.
Because two-dimensional bar codes are capable of encoding thousands of characters,
human-readable interpretation of the data may not be practical. Alternatively, descriptive text rather
than literal text may be printed with the symbol. If printed, any character size and font available may
be selected, and the text may be printed anywhere desired near the symbol. The text must not
interfere with the bar code symbol or its quiet zones.
Compressed data formats
Some bar code symbologies, such as UPC-E and Code 128, use compressed data formats. The
Forms and Bar Code Card accepts data for these symbologies in either compressed or
uncompressed format. The incoming data is analyzed to determine if it is compressed or not, and if
required, compression is automatically performed before printing the bar code.
Checksum calculation
Some bar code symbologies define checksum characters as a requirement of the data format. When
this is the case, the Forms and Bar Code Card performs the checksum calculation and automatically
places the character(s) per the symbology specifications. Fixed length data formats can be sent with
or without checksum characters.