🧾 Description
Script that can solve some of our issues when confronted with this particular situation, the customer has both a device that does not support UTF-8 encoding, and the need to scan Labels with German Umlauts created with UTF-8 encoding.
If a customer has a device that only support ASCII characters a problem will arise when scanning a label with Umlauts encoded using UTF-8, even if another formatting was used, precedent to this, explained in article KA-01334. That is because UTF-8 uses two (2) ASCII characters to encode the Umlaut instead of one (1), while the other script was converting only one (1) ASCII character. That script has its usefulness when scanning labels with Umlauts but encoded with ASCII.
Here below the translation Table:
\xC3\xBC -> \xFC (ü)
\xC3\xB6 -> \xF6 (ö)
\xC3\xA4 -> \xE4 (ä)
\xC3\x9F -> \xDF (ß)
\xC3\x9C -> \xDC (Ü)
\xC3\x96 -> \xD6 (Ö)
\xC3\x84 -> \xC4 (Ä)
\xC3\xB6 -> \xF6 (ö)
\xC3\xA4 -> \xE4 (ä)
\xC3\x9F -> \xDF (ß)
\xC3\x9C -> \xDC (Ü)
\xC3\x96 -> \xD6 (Ö)
\xC3\x84 -> \xC4 (Ä)
Devices tested with this configuration successfullyare PowerScan 9500/9501/9531 and QuickScan 2400.
🛠️ Resolution Steps
Converting UTF-8 encoded Umlauts in ASCII readable characters. Configuration document is in Attachments section.