Lexmark MX826 Forms and Bar Code Card P4.2 Technical Reference - Page 138
PDF417 capacity, MaxiCode separators and structured appends, MaxiCode typeface call method
View all Lexmark MX826 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 138 highlights
Lexmark Confidential until announced Appendix F - Deviations 138 If you allocate space for these particular bar codes, and they do not fit on the right side, then there are two options: • Use the PCL B and S parameters to shrink the bar code in size. • Escalate the issue for a field fix. PDF417 capacity The introduction of the AIM PDF417 specification defines the maximum data characters per symbol (at ECC0) for PDF417: • 1850 text characters • 2710 digits • 1108 bytes The total number of codewords in the data region of a single PDF417 symbol cannot exceed 928. All input data must conform to the AIM PDF417 specification, and any input data over the maximum length must be truncated and discarded. The firmware allows and truncates a maximum of 2710 digits or 1850 text characters. The remaining maximum data is submitted to the BCE to be rendered. However, extra checking code is required to truncate excess data while encoding codes that are within the limit. The original Forms and Bar Code Card encodes more than the maximum amount allowed by the AIM specification, but users must never exceed these values. Also, not all bar code readers can decode data more than the maximum allowed in the AIM PDF417 specification. MaxiCode separators and structured appends Note: For more information, see the AIM MaxiCode specification. A valid MaxiCode data separator for MaxiCode data blocks is either of the following: • Group separator-29 decimal (1D hexadecimal) • Comma-44 decimal (2C hexadecimal) MaxiCode typeface call method A structured append is covered in the AIM MaxiCode specification, which allows up to eight MaxiCode symbols to be chained together as one. However, there are no bar code readers that can decode combined bar code series. SuchyMIPS and HP BarDIMM Pro support structured appends so they can parse the structured append, but they do not fully implement it. A structured append consists of four bytes: • A number 1 through 8 that labels each individual MaxiCode in the structured append • A separator character, either a comma or group separator (ASCII 29) • A number 1 through 8 that is the maximum number of MaxiCode symbols in the structured append • Another separator character For example, the only valid MaxiCode that is supported is a single symbol, specified as the following: