Different programming environments enforce distinct escape syntaxes for representing non-ASCII characters. This tool formats text across all major language conventions:
Given this JavaScript configuration snippet containing an emoji and accented character:
const label = "Café 🚀";
Formatting across language modes produces:
ES6 (\u{...}): const label = "Caf\u{e9} \u{1f680}";
JSON / Java (\uXXXX): const label = "Caf\u00e9 \ud83d\ude80";
Python (\x \u \U): const label = "Caf\xe9 \U0001f680";
CSS (\XXXX ): const label = "Caf\e9 \1f680 ";
UTF-8 bytes (\xXX): const label = "Caf\xc3\xa9 \xf0\x9f\x9a\x80";
Notice that in JSON/Java mode, the rocket emoji decomposes into two UTF-16 surrogate pairs (\ud83d\ude80), while ES6 and Python use clean single-token representations. Python writes characters below U+0100 as \xe9, the way its own ascii() does. Every CSS escape ends with a terminating space, so the real space after é shows up as two spaces. The UTF-8 byte mode writes the bytes of each character, which is what C strings and shell printf expect.