Datamax-O'Neil Class Series Programmer’s Manual - Manual (Page 235)

Class Series Programmer’s Manual 221
Appendix H
Single and Double Byte Character Font Mapping
Label format records with font code 9 in the b field of the Format Record header can specify any of the
following bit-mapped or scalable fonts with the associated specification in the font size/selection (eee
height) field, as shown in the tables on the following pages.
Example: 1911u4000100010A0215134<CR>
The example above will produce a printed string consisting of the two Kanji characters referenced by the
two HEX ASCII pairs A0, 21, and 51, 34, on appropriately equipped printers.
Example: 1911U4001000100P012P012<0x38><0x77><0x00>
The above example will produce a printed string consisting of the one 12 point Kanji character referenced
by the byte pair with hex values 38 and 77 on appropriately equipped printers.
 Note: Double byte hex representation character strings terminate with two null bytes and a <CR>, i.e., 0x 00
00 0D
. The Hex-ASCII representation is terminated with <CR>.
The alphanumeric portion (nn) of the scalable font specifiers, Snn, Unn, unn, numbering system is a base
62 numbering system, 0, 1, 2…8, 9, A, B, C...X, Y, Z, a, b, c...x, y, z. For scalable fonts the S designation
signifies single byte characters and U designates double byte. The lower case U counterpart signifies that
print data in the label format record is in a hex-ASCII format. Fonts that have been downloaded with
designators of the form nn, where nn are alphanumeric, as seen in the font size specifier (eee height)
column below, may be referenced in label format records by their upper or lower case specifiers as
available. However, fonts created for double-byte access cannot be accessed using Snn as the font
designator, and vice versa, single-byte fonts cannot be accessed using Unn or unn.
 Note: Downloading scalable fonts require specifying the font ID, a two character alphanumeric. The S, or U, u
used in referencing the font within label format records is not used in the download specification.
Attempting to utilize a scalable font with an inappropriate byte-size designation (e.g. S on double byte or
U, u on single byte) will have unpredictable results.