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

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: Bar code symbology Parameter ISBN Bar Widths Swiss Post Bar Heights ISBN Bar Heights ISSN Bar Heights ISBN Space Widths ISSN Bar Widths ISSN Space Widths New limit 0x0100 0x1000 0x2000 0x2000 0x0100 0x0100 0x0100 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: Deviations 165