Deviations
165
Encoding limits for bar codes
This deviation concerns firmware-imposed limits on certain bar codes. These limits are less than the
original LXK BCC, but are needed to prevent corruption of bar code images.
This table details the new limits:
Encoding limits for Codabar bar codes
In the absence of start/stop characters, if users attempt to encode a Codabar bar code with
non-numeric characters, then the !Err: 12 Invalid Character error message appears.
When using the optional start/stop characters, characters between the start and stop characters
should be numeric, or any of the following non-numeric characters: - , $ , : , / , +. Otherwise, the
!Err: 12 Invalid Character error message appears.
If an attempt is made to encode a Codabar barcode with only one character and this character is a
numeric character, then a Codabar barcode is generated. If an attempt is made to encode a Codabar
barcode with no characters present, then the !Err: 15 String too Short error message
appears.
PostScript barcodepath operator
The PostScript operator barcodepath does not work as on previous Lexmark Bar Code options. The
barcodepath operator used to obtain the outline of the bar code that results from doing a
barcodeshow with the same arguments. Because all bar codes are now generated as images, the
barcodepath operator does not return any useful information.
Any further use of the barcodepath operator should be discontinued.
Uploading formsets when the OFIS data filter is disabled
When the OFIS data filter is disabled, uploading formsets that contain OFIS tags to Forms Manager
will result in one of two scenarios:
Bar code symbology Parameter New limit
ISBN Bar Widths 0x0100
Swiss Post Bar Heights 0x1000
ISBN Bar Heights 0x2000
ISSN Bar Heights 0x2000
ISBN Space Widths 0x0100
ISSN Bar Widths 0x0100
ISSN Space Widths 0x0100
To Next Page
Loading...
Need help?
General