TransAct Epic 3000, Руководство программиста

Страница: 219 / 271

T480 Programmer’s Guide T480 Extended Printer Control
100-14362 Rev A Page 219
(0xFEFF) for the correct byte order to be initialized. Sending the BOM in big-endian
would be as follows:
0xFE 0xFF
UTF-16LE uses the little-endian method of sending the two bytes. This method sends
the low byte first and then the high byte. It is not required to send the byte order mark
(0xFEFF) for the correct byte order to be initialized. Sending the BOM in big-endian
would be as follows:
0xFF 0xFE
UTF-8
UTF-8 uses a Multiple Byte Character Sequence (MBCS) to identify the desired Unicode
character. This encoding method is less straightforward but preserves some of the 8-bit
character of ASCII encoding.. This method uses unique bit sequences at the MSBs of a
byte to determine its location and meaning within the MBCS encoding. See the table
below for more information. If UTF-8 is selected all data sent to the printer must be
encoded. All command parameters over 127 must be encoded in UTF-8.
UTF-8TXT uses a Multiple Byte Character Sequence (MBCS) to identify the desired
Unicode character. This encoding method is identical to UTF-8 except commands and
command parameters over 127 are not UTF-8 encoded. They must be sent unmodified
as 8-bit values.
UTF-8TXT is probably the easiest mode to use. It allows normal 8 bit
commands and graphics while still supporting the full Unicode character
encoding range. Typically EPIC 3000 Printers are shipped set to this
mode
.
Scalar Value 1
st
Byte 2nd Byte 3rd Byte 4th Byte
0000000 00000000 0xxxxxxx 0xxxxxxx
0000000 00000yyy yyxxxxxx 110yyyyy 10xxxxxx
0000000 zzzzyyyy yyxxxxxx 1110zzzz 10yyyyyy 10xxxxxx
00uuuuu zzzzyyyy yyxxxxxx 11110uuu 10uuzzzz 10yyyyyy 10xxxxxx
NOTE: Where values from 0x001FFFFF may be encoded, only values up
to 0x0010FFFF are valid in Unicode 5.0
Unicode UTF8 Encoding Example
3 Byte output Example
Hex Character Code: FA11
FA 11
- Original Hex Code(s)
11111010 000100001
- Converted to Binary