Detection Of UTF-16 Encoding In Streaming XML Data Without A Byte-Order Mark And Related Printers, Systems, Methods, And Computer Program Products

• US 20120170079A1
• Filed: 03/15/2012
• Published: 07/05/2012
• Est. Priority Date: 11/14/2007
• Status: Active Grant

• Current Assignee: Zebra Technologies Corporation
• Original Assignee: ZIH Corp. (Zebra Technologies Corporation)
• Inventors: Susi, Ferdinand C. III, Wettstein, Jessica S.
• Granted Patent: US 9,720,885 B2
• Time in Patent Office: Days
• US Class Current: 358/3.13
• CPC Class Codes: G06F 3/1297 Printer code translation, conversion, emulation, compression; Configuration of printer parameters
• CPC Class Codes: G06F 40/126 Character encoding
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets

Abstract

Provided are printers and other electronic devices, systems, methods, and computer program products that automatically detect and determine UTF-16 encoding schemes and endiannesss thereof in an incoming XML data steam for XML declarations without a UTF-16 byte-order mark (BOM) or encoding declaration. This allows for the automatic and unambiguous accurate detection of UTF-16 encoded XML data within a mixed encoding environment, such as from multiple sources using more than one encoding scheme, even when XML data does not start with a BOM or encoding declaration.

Claims

1. A method, comprising automatically determining a UTF-16 encoding scheme in an incoming data stream without a byte-order mark.

2. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving structure markup language data in the incoming data stream; and

processing the incoming data stream according to the automatically determined UTF-16 encoding scheme.

3. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving structure markup language data in the incoming data stream; and

storing a current encoding status of the incoming data stream as the automatically determined UTF-16 encoding scheme.

4. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving XML data in the incoming data stream at a print server;

inserting a byte-order mark into the incoming data stream identifying the automatically determined UTF-16 encoding scheme of the incoming data stream to create an enhanced incoming data stream; and

transmitting the enhanced incoming XML data stream to a printer.

5. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving the incoming data stream;

storing a current encoding status of the incoming data stream;

monitoring the incoming data stream for the presence of a 0x3C byte;

when a 0x3C byte is identified, determining if a byte following the 0x3C byte is a null 0x00 byte; and

if the byte following the 0x3C byte is a null 0x00 byte and if the current encoding status is not UTF-16LE, then;

determining if a byte before the 0x3C byte is a null 0x00 byte;

if the byte before the 0x3C byte is a null 0x00 byte, then begin processing the incoming data stream as UTF-16BE and storing the current encoding status of the incoming data stream as UTF-16BE; and

if the byte before the 0x3C byte is not a null 0x00 byte, then begin processing the incoming data stream as UTF-16LE and storing the current encoding status of the incoming data stream as UTF-16LE.

6. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving the incoming data stream;

storing a current encoding status of the incoming data stream;

monitoring the incoming data stream for the presence of a 0x3C byte;

when a 0x3C byte is identified, determining if a byte following the 0x3C byte is a null 0x00 byte; and

if the byte following the 0x3C byte is a null 0x00 byte and if the current encoding status is not UTF-16LE, then;

determining if a byte before the 0x3C byte is a null 0x00 byte; and

if the byte before the 0x3C byte is a null 0x00 byte, then begin processing the incoming data stream as UTF-16BE and storing the current encoding status of the incoming data stream as UTF-16BE.

7. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving the incoming data stream;

storing a current encoding status of the incoming data stream;

monitoring the incoming data stream for the presence of a 0x3C byte;

when a 0x3C byte is identified, determining if a byte following the 0x3C byte is a null 0x00 byte; and

if the byte following the 0x3C byte is a null 0x00 byte and if the current encoding status is not UTF-16LE, then;

determining if a byte before the 0x3C byte is a null 0x00 byte; and

if the byte before the 0x3C byte is not a null 0x00 byte, then begin processing the incoming data stream as UTF-16LE and storing the current encoding status of the incoming data stream as UTF-16LE.

8. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving the incoming data stream;

storing a current encoding status of the incoming data stream;

monitoring the incoming data stream for the presence of a 0x3C byte;

when a 0x3C byte is identified, determining if a byte following the 0x3C byte is a null 0x00 byte; and

if the byte following the 0x3C byte is a null 0x00 byte and if the current encoding status is UTF-16LE, then;

determining if the two bytes before the 0x3C byte are null 0x00 bytes;

if the two bytes before the 0x3C byte are null 0x00 bytes, then begin processing the incoming data stream as UTF-16BE and storing the current encoding status of the incoming data stream as UTF-16BE; and

if the two bytes before the 0x3C byte are not null 0x00 bytes, then begin processing the incoming data stream as UTF-16LE and storing the current encoding status of the incoming data stream as UTF-16LE.

9. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving the incoming data stream;

storing a current encoding status of the incoming data stream;

monitoring the incoming data stream for the presence of a 0x3C byte;

when a 0x3C byte is identified, determining if a byte following the 0x3C byte is a null 0x00 byte; and

if the byte following the 0x3C byte is a null 0x00 byte and if the current encoding status is UTF-16LE, then;

determining if the two bytes before the 0x3C byte are null 0x00 bytes; and

if the two bytes before the 0x3C byte are null 0x00 bytes, then begin processing the incoming data stream as UTF-16BE and storing the current encoding status of the incoming data stream as UTF-16BE.

10. The method of claim 1, wherein automatically determining a UTF-16 encoding scheme, comprises:

receiving the incoming data stream;

storing a current encoding status of the incoming data stream;

monitoring the incoming data stream for the presence of a 0x3C byte;

when a 0x3C byte is identified, determining if a byte following the 0x3C byte is a null 0x00 byte; and

if the byte following the 0x3C byte is a null 0x00 byte and if the current encoding status is UTF-16LE, then;

determining if the two bytes before the 0x3C byte are null 0x00 bytes; and

if the two bytes before the 0x3C byte are not null 0x00 bytes, then begin processing the incoming data stream as UTF-16LE and storing the current encoding status of the incoming data stream as UTF-16LE.

11. The method of claim 1, wherein the incoming data stream comprises XML data.

12. A electronic device, comprising a processor configured for receiving structure markup language data without a byte-order mark in an incoming data stream and automatically determining a UTF-16 encoding scheme of the structure markup language data without a byte-order mark.

13. The electronic device of claim 12, wherein the structure markup language data is XML data.

14. The electronic device of claim 12, wherein the electronic device comprises a printer.

15. The electronic device of claim 12, wherein the electronic device comprises a print server.

16. The electronic device of claim 12, wherein the electronic device comprises a software print driver.

17. The electronic device of claim 12, wherein the electronic device comprises a bar code scanner.

18. The electronic device of claim 12, wherein the electronic device comprises an RFID reader/writer.

19. A printing system, comprising:

a first electronic device;

a print server communicatively connected to the first electronic device and configured to receive data from the first electronic device in an incoming data stream received by the print server, wherein the printer comprises an XML processor configured to;

process the incoming data stream to automatically determine a UTF-16 encoding scheme in the incoming data stream without a byte-order mark,

insert a byte-order mark into the incoming data stream identifying the automatically determined UTF-16 encoding scheme of the incoming data stream to create an enhanced incoming data stream, and

transmit the enhanced incoming data stream; and

a printer communicatively connected to the print server and configured to receive the enhanced incoming data stream.