luit

luit is a utility program used to translate the character set of a computer program so that its output can be displayed correctly on a terminal emulator that uses a different character set.[3] Whereas iconv converts the character set of strings or text files at rest, luit converts the input and output of programs running interactively.

luit
luit rendering ISO 8859-1 accented characters on a UTF-8 terminal emulator.
Original author(s)Juliusz Chroboczek
Initial release2001 (2001)
Stable release
2.0 / May 8, 2016 (2016-05-08)[1][2]
Repository
Operating systemUnix and Unix-like
TypeUtility software
LicenseMIT/X Consortium License
Websiteinvisible-island.net/luit/

Overview

The main purpose of luit is to allow "legacy" applications that use character sets other than UTF-8 to work with contemporary terminal emulators.

luit may be required today when connecting to a "legacy" host that only supports an older encoding, such as ISO 8859-1. For example, instead of running "ssh legacy-machine", a user may have to run "LC_ALL=fr_FR luit ssh legacy-machine" to properly render French accented characters on a UTF-8 terminal.[3]

luit is also used to properly render the output of applications that use ISO 2022 character set switching. ISO 2022 is an older standard[4] that allowed an application to "switch" between different fonts, e.g., to mix line-drawing characters with text or to display text in multiple languages and character sets. UTF-8 itself does not support switching fonts; the encoding is stateless and gives each unique character (including line-drawing characters) its own numerical encoding. It can be used to translate between these two encodings.

Examples of programs that require translation to run correctly on a UTF-8 terminal include earlier versions of emacs/MULE,[5] and programs that use ISO 2022 shift sequences in ANSI escape codes that switch to an alternate character set in order to draw line-drawing characters.

luit is invoked automatically by xterm when necessary to translate program output into UTF-8,[6] for programs running on a local computer. When connecting remotely to another computer, the user must run luit directly.

luit interprets application output according to the locale's character set with ISO 2022 shifts and ECMA-48 escape sequences. If an application is speaking a different language than the locale's character set (one that may have matched the terminal emulator's expectations in the absence of luit), luit can misinterpret the application's output and produce corrupted output to the terminal.[7]

History

luit was written in 2001 by Juliusz Chroboczek,[5] when major Linux distributions began migrating to the Unicode character set from "legacy" encodings such as ISO 8859-1.[4] It has since become a widely installed base utility, present on more than half of all Linux computer systems by some estimates.[8][9] It is also part of IBM's AIX.[10]

Implementations

There are two versions of luit: one maintained by Thomas Dickey[6] as part of xterm, and another by Freedesktop.org.[11] Linux distributions generally ship the latter version[12] as part of their X11 utilities package. However, while migrating to GitLab, the latter fork was discontinued because it was unmaintained.[13]

gollark: kbps or KB/s?
gollark: Ignore umnikos as they are bee.
gollark: ... no.
gollark: Incorrect; you are to produce and consume the cracker.
gollark: CONSUME the cracker.

See also

References
  1. Coopersmith, Alan, "Luit 1.1.1 release announcement" (March 22, 2012)
  2. http://invisible-island.net/luit/luit.log.html
  3. "luit manual page"
  4. "UTF-8 and Unicode FAQ for Unix/Linux"
  5. "luit author website"
  6. "luit home page"
  7. "luit notes"
  8. "x11-utils Debian popularity contest results"
  9. "Ubuntu popularity contest results"
  10. AIX 7.1 manual
  11. "Xorg luit home page"
  12. "Freedesktop mailing list discussion, 'luit forked?', April 2009
  13. Adam Jackson (August 7, 2018). "[PATCH app/luit] Retire this fork of luit". xorg-devel@lists.x.org (Mailing list).
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.