Barcode Types (Fonts) and Patterns

The following industry-standard barcode types are supported:

• Code 128 (barcode128) - Code 128 is used for alphanumeric or numeric-only barcodes and uses all 128 ASCII characters; can be generated with a dynamic, static, or embedded PDF REQ document.
• Code 39 (barcode39) - Also referred to as 3 of 9 or 3.9. Code 39 uses 43 characters including uppercase letters (A through Z), numeric digits (0 through 9) and a number of special characters (-, ., $, /, +, %, and space); can be generated with a dynamic, static, or embedded PDF REQ document.
  • Code 39 Extended - Code 39 Extended is an extended version of Code 39 that supports the ASCII character set. So with Code 39 Extended you can also code the 26 lower letters (a-z) and the special characters you have on your keyboard.
    Note: Currently, only Code 39 Extended is compatible with the RTF document format.
• Inter25 (barcodeInter25) - Also referred to as 2 of 5; can be generated with a dynamic, static, or embedded PDF REQ document.
  Note: BarcodeInter25 requires the barcode to contain an even number of characters and static text characters; a 0 (zero) will be added to the beginning if an odd number of characters is provided. Note also that a barcodeInter25 only supports the use of numeric characters (i.e. "digits"). The use of non-numeric characters will result in an exception.
• 2D Symbolism (barcode2D) - This option produces a barcode based on the PDF 417 definition; can be generated with a dynamic, static, or embedded PDF REQ document.
  Note: Any pattern text passed using barcode2d does not appear as text on the resulting documents; however, pattern text is present when scanning the barcode.
• QR Barcode - This option produces a two-dimensional matrix barcode and can be generated with a dynamic, static, or embedded PDF REQ document.
  Note: The QR barcode is .5 x .5 inches in size when generated on documents and depending on the barcode alignment, the central scanning point is equidistant from the surrounding document margins regardless of the barcode size. Any pattern text passed using barcodeQR does not appear as text on the resulting documents; however, pattern text is present when scanning the barcode.

The mechanism to apply specific values to a barcode on a per-document-request basis is to include a Pattern parameter on Barcode object in the request. This allows a barcode to be constructed with one or more optional components;

• %page% - individual page number of the document
• %totalpages% - the total number of pages for the document
• %docsequence% - the doc sequence number
• %docsequencetotal% - the total doc sequence number
• %docname% - the instance display name of the document
• %date% - the current system date in MM/DD/YYYY format
• %BRCD . . .% - the custom barcode pattern containing optional characters

The order of parts in the pattern string does not matter; whatever order is presented in the string defines the order of presentation. Text can be added anywhere is the string to establish a unique name or to set delimiters between any of the components. In this example, the barcode is defined to generate with the total numbers of pages, the instance display name of the document, and the system date with a [ _ ] added as the de facto delimiter for each value.

<exp:Barcode>
 <exp:Type>barcode128</exp:Type>
 <exp:Pattern>Page_%page%_of_%totalpages%_%date%_Doc_%docsequence%_of_%docsequencetotal%</exp:Pattern>
</exp:Barcode>

The example renders a barcode that looks like this: