• Proxy32 user interface and configuration files are using UNICODE (UTF16LE, MS Windows standard).
• SCRIPT/I-SCRIPT files are automatically converted into UTF-16LE (replaced on the disk by UTF-16LE versions) before they are searched (by search on LauncherTree) or executed.
• Terminal supports UTF8 input/output for communication with remote equipment (full range of UNICODE code points, including 4 byte UTF8 sequences that are translated into UTF-16 surrogate pairs when used in the Windows GUI interface)
• By default, terminal converts all UNICODE user input (Keyboard, IME, Paste, COMMAND, SCRIPT/I-SCRIPT) to ASCII characters before sending it to remote host, but this can be turned off if working with equipment that supports UTF8 input.
• Terminal supports East Asian Width (width of CJK chars) per UNICODE 6.2 spec. while printing on the terminal screen.
• Terminal has a switch to change width of Ambiguous East Asian chars from half to full while printing on the terminal screen.

User input conversion in the Terminal

By default, Proxy32 terminal translates all UNICODE user input (Keyboard, IME, Paste, COMMAND, SCRIPT/I-SCRIPT) into ASCII characters before sending it to remote host. In particular, by default, it is bypassing MS Windows language and keyboard layouts translation. If UTF8 option is enabled ("Enable UNICODE Input from Keyboard, IME, Paste, COMMAND, SCRIPT" in terminal window menu), Proxy32 terminal translates all UNICODE user input (Keyboard, IME, Paste, COMMAND, SCRIPT/I-SCRIPT) into UTF8 characters before sending it to remote host.

This option is thought as extra protection in case remote host cannot handle UTF8 input. Only LINUX/CYGWIN boxes are known to me to be able to handle UTF8 input smoothly. Other equipment may not be able to handle it and, potentially, may even crash when UTF8 input is received. As a rule of thumb, enable this option if working with non-English texts and file names on LINUX/CYGWIN boxes and disable it in all other cases. At the global level this option is located in “Settings/Initial Terminal Settings/WORKAROUNDS/Enable UNICODE Input from Keyboard, IME, Paste, COMMAND, SCRIPT” menu in the LauncherTree window.

Please, keep in mind that PLUGIN/I-PLUGIN provides input to terminal as byte stream and terminal does not translate this information before sending it to the remote host. Therefore, PLUGIN writer is responsible for sending input in the format that remote host can understand.