Text objects – HP SAP Smart Forms and Zeberea Print User Manual
Page 43
Driving Zebra Printers from Smart Forms
13760L
Page 42
Text Objects
Smart Forms supports Zebra preloaded printer-resident scaleable fonts. It also supports
TrueType font downloading and TrueType fonts stored in Zebra printer Flash memory.
We strongly recommend that you use printer-resident fonts for simplicity and maximum
printer throughput.
Western European—IBM CodePage 850
You will normally design your forms/labels for Zebra printers using the SAP “HELVE”
font. This font maps to Zebra’s printer-resident “CG Triumvirate bold condensed” (IBM
Codepage 850) when using device type ZlbzebsX.pri (X=2,3 or 6).
International Printing (EMEA Only)—Unicode™
SAP “HELVE”,”HELVECYR” (Cyrillic) and “HELVE_I7” (Greek) can also be used for
international printing using Zebra’s ZlbzebsX.pri (X=2,3 or 6) device type. This Unicode
UTF-8 device type maps to Zebra’s printer-resident Swiss 721 font. This is preloaded on
all printers shipped in EMEA. This font is available for download FOC for other
countries if required. This will allow you to print local languages using Unicode (UTF-8)
even on non-Unicode SAP systems.
Global International Printing including APAC—Unicode
SAP end users wishing to print Asian characters on Zebra printers must use the SAP font
ANDALE_J, ANDALE_K, ANDALE_S or ANDALE_T with the Zebra Device Type
ZlbzebuX.pri (X=2,3 or 6) and the corresponding optional matching font card available
from Zebra. Refer to the section on device types at the beginning of this document for
more information. This will allow you to print local languages using Unicode (UTF-8)
even on non-Unicode SAP systems.
Text Reversing
Text reversing is supported via Solid Boxes. Refer to “Tips and Tricks: Lines and Boxes”
(page 43) and also “Tips and Tricks: Printer Settings” (page 48) for detailed information.
TrueType Fonts
Smart Forms allows users to upload TrueType fonts and then use these fonts for the
form/label design (See OSS Note 201307). TrueType fonts are uploaded using
transaction SE73; see below: