In either VTxxx or Tektronix mode, there are escape sequences to change the.

There are TrueType fonts with good coverage (better, anyway). The VT220 emulation does not support soft fonts, it is otherwise complete. For instance, on my OSX machine, 'Mono' is shown in xfd as Bitstream Vera Sans Mono-12:style=Roman, which (see Font Squirrel) has that sort of limited coverage.

likewise, if your shell sets different locations for the resource files than the system, that can make a difference.īut likely the difference lies in the font choice.

xterm by default only supports the PRIMARY buffer. Unlike set-vt-font(), this does not affect the escape- and select. xterm can tell the querying program what. It does not change if you alter resource settings, e.g., the boldColors resource. depending on how it is compiled, typically 16. For example, for xterm (X-class Xterm) and the Terminus font, you might add to /.Xresources. X resources: use a font specification with character set and econding fields set to -iso10646-1.

your system locale may not use UTF-8 encoding if your shell sets the locale in its initialization script, you can see differences a selection in xterm you may notice that the selection does not get sent to the. Normally it is 'XTerm', but can be set to another class such as 'UXTerm' to override selected. Ctrl RightClick (context menu) and UTF-8 encoding.

Without the -fa option, xterm defaults to bitmap-fonts, which may come with reasonably good Unicode coverage (depending on what you want).

Most of the TrueType fonts are not unicode fonts, but rather ISO-8859-1 with a handful of characters outside that set. And the comment about starting it from the command-line says xterm -u8

Uxterm does not change font