LC_ALL can be used to override all other settings.For program input/output the important entry is LC_CTYPE.We cannot explain the locale system here in detail, just a few notes: LC_CTYPE = "de_DE.UTF-8" LC_NUMERIC = "de_DE.UTF-8" LC_TIME = "de_DE.UTF-8" LC_COLLATE = "de_DE.UTF-8" LC_MONETARY = "de_DE.UTF-8" LC_MESSAGES = "de_DE.UTF-8" LC_PAPER = "de_DE.UTF-8" LC_NAME = "de_DE.UTF-8" LC_ADDRESS = "de_DE.UTF-8" LC_TELEPHONE = "de_DE.UTF-8" LC_MEASUREMENT = "de_DE.UTF-8" LC_IDENTIFICATION = "de_DE.UTF-8" LC_ALL = iconv).Įxample: luit using latin-1 for a single program If it does not suit your purpose or is not available for your system refer to general converters that most environments offer (e.g. luit was designed with terminal data streams in mind and can handle most scenarios with escape sequences correctly. If you have to deal with older systems or programs that dont understand UTF-8, we strongly suggest to use a streamline transcoder like luit to translate between the foreign encoding and UTF-8. Xterm.js does not support any legacy encoding and probably never will. xterm.js currently uses onBinary only for legacy mouse reports, that cannot be encoded in UTF-8.Ĭaveat: Watch out for automatic UTF-8 conversions done by some nodejs interfaces with string type, always go with the buffer variant if possible. In nodejs you can consume the payload with the 'binary' encoding, which automatically takes care of the high bits (e.g. data & 0xFF) before processing and file an issue, as it is most likely a problem on the event triggering side. If you find a higher codepoint, strip the high bits (e.g. The payload should never contain a higher codepoint than 255. For easier consumption the payload is a string type, but should be treated as a binary string, where a codepoint directly maps to the 8-bit byte value.
If you need legacy encoding support, see below.Ĭontains raw binary data. For OS interaction this data should be converted to UTF-8 bytes (automatically done by node-pty).
OutputĬontains real string data with any valid Unicode codepoint, thus the payload should be treated as UTF-16/UCS-2. The input decoders are stream aware, thus will compose codepoints from consecutive multibyte chunks. Uint8Array as sequence of UTF-8 byte values.Terminal.write supports these input types with the following encoding:
0 kommentar(er)
