Use Barcode Fonts in Reports
Publisher includes several fonts that output barcodes.
Font files included with Publisher:
- LibreBarcode128-Regular.TTF - Supports code128a, code128b, and code128c algorithms. Also supports code128auto to automatically switch between the three code128 algorithms.
- LibreBarcode39-Regular.TTF - Supports code39 and code39mod43 algorithms.
- LibreBarcodeEAN13Text-Regular.TTF - Supports upca and upce algorithms.
When you use one of these prepackaged fonts, Publisher executes the preprocessing on the data prior to applying the barcode font to the data in the output document. For example, to calculate checksum values or start and end bits for the data before formatting them.
At design time, you don't need to apply the barcode font to the field in Microsoft Word. Instead, you can map the font that you apply to the field using Publisher's font mapping. At runtime, Publisher applies the barcode font to any field using the base font you specified in the font mapping. Be sure to choose a font that isn't used elsewhere in the template.
If you want to use the font directly in Microsoft Word, then add the appropriate .TTF file to the C:\WINDOWS\Fonts
directory. To use the Template Builder Preview function, map the font in the Template Builder configuration file.
To use the barcode fonts in the report output:
Note the following:
-
Microsoft Word may not render the barcode fonts properly even when they're installed on your client. To work around this issue, apply a different font to the field and map the font as described above.
-
The upca algorithm accepts only UPC-A message string and encodes into UPC-A barcode.
-
A string of 12 characters is treated as UPC-A message with a check digit, 11 is without a check digit.
-
The upce algorithm accepts only UPC-E message strings and encodes into UPC-E barcode.
-
A string of 8 characters is treated as a UPC-E message with both a front and end guard bar; a string of 6 characters is without guard bars.