aixterm Command

Purpose

Initializes an Enhanced X-Windows terminal emulator.

Syntax

aixterm [  -ah ] [  -ar ] [  -autopush ] [  -b NumberPixels ] [  -bd Color ] [  -bg Color ] [  -bw NumberPixels ] [  -cc CharRange:Value [ ,... ] ] [  -cr Color ] [  -csd CharShape ] [  -cu ] [  -C ] [  -display Name:Number ] [  -dw ] [  -f0 Font ] [  -f1 Font ] [  -f2 Font ] [  -f3 Font ] [  -f4 Font ] [  -f5 Font ] [  -f6 Font ] [  -f7 Font ] [  -f0 FontSet ] [  -f1 FontSet ] [  -f2 FontSet ] [  -f3 FontSet ] [  -f4 FontSet ] [  -f5 FontSet ] [  -f6 FontSet ] [  -f7 FontSet ] [  -fb Font ] [  -fg Color ] [  -fi FontSet ] [  -fn Font ]  [  -fs Font ] [  -fullcursor ] [  -geometry Geometry ] [  #geometry Geometry ] [  -help ] [  -i ] [  -ib File ] [  -im InputMethod ] [  -j ] [  -keywords ] [  -lang Language ] [  -l ] [  -leftscroll ] [  -lf File ] [  -ls ] [  -mb ] [  -mc Number ] [  -ms Color ] [  -mn ] [  -n IconName ] [  -name Application ] [  -nb Number ] [  -nobidi ] [  -nonulls ] [  -nss NumShape ] [  -orient Orientation ] [  -outline Color ] [  -po Number ] [  -ps ] [  -pt Preedit ] [  -reduced ] [  -rfb Font ] [  -rfi Font ] [  -rfn Font ] [  -rfs Font ] [  -rf0 Font ] [  -rf1 Font ] [  -rf2 Font ] [  -rf3 Font ] [  -rf4 Font ] [  -rf5 Font ] [  -rf6Font ] [  -rf7 Font ] [  -rf0 FontSet ] [  -rf1 FontSet ] [  -rf2 FontSet ] [  -rf3 FontSet ] [  -rf4 FontSet ] [  -rf5 FontSet ] [  -rf6 FontSet ] [  -rf7 FontSet ] [  -rv ] [  -rw ] [  -s ] [  -sb ] [  -sf ] [  -si ] [  -sk ] [  -sl NumberLines ] [  -sn ] [  -st ] [  -suppress ] [  -symmetric ] [  -T Title ] [  -text TextType ] [  -ti ] [  -tm String ] [  -tn TerminalName ] [  -ut ] [  -v ] [  -vb ] [  -W ] [  -xrm String ] [  -132 ] [  -e Command ]

Description

The aixterm command provides a standard terminal type for programs that do not interact directly with Enhanced X-Windows. This command provides an emulation for a VT102 terminal or a high function terminal (HFT). The VT102 mode is activated by the -v flag.

The aixterm command supports the display for up to 16 colors at a time.

The aixterm terminal supports escape sequences that perform terminal functions such as cursor control, moving and deleting lines, and aixterm private functions.

Many of the special aixterm terminal features (like the scroll bar) can be modified under program control through a set of private aixterm command escape sequences. You can also use escape sequences to change the title in the title bar.

There are three different areas in the aixterm window:

• Scroll bar
• Status line
• Terminal window.

By default, only the terminal window is initially displayed.

The terminal window is the area provided for terminal emulation. When you create a window, a pseudo terminal is allocated and a command (usually a shell) is started.

The aixterm command automatically highlights the window border and the text cursor when the mouse cursor enters the window (selected) and unhighlights them when the mouse cursor leaves the window (unselected). If the window is the focus window, the window is highlighted regardless of the location of the mouse cursor. Any window manager, as in the case of the AIXwindows Window Manager (MWM), can cover the aixterm border, and the highlight and border color do not show.

The WINDOWID environment variable is set to the resource ID number of the aixterm window.

When running in an aixterm window, the TERM environment variable should be TERM=aixterm.

The TERM environment variable on your home machine determines what the TERM environment variable should be on the remote machine (unless it is overridden by your .profile).

When you use the rlogin, tn, or rsh commands to login to a different machine, the TERM environment variable should be set to aixterm. If this operation does not occur, you can perform the following two command line operations:

1. TERM=aixterm
2. export TERM

If commands (for example, the vi command) do not recognize the term type aixterm when you login to another system, perform the following one-time operation on the remote system:

1. su
2. cd/tmp
3. mkdir Xxxxx
4. cd Xxxxx
5. ftp LocalSystemName
6. cd /usr/share/lib/terminfo
7. get ibm.ti
8. quit
9. TERMINFO=/tmp/Xxxxx
10. export TERMINFO
11. tic ibm.ti
12. ls
13. ls a
14. mkdir /usr/share/lib/terminfo/a
15. cp a/aixterm* /usr/share/lib/terminfo/a
16. cd /tmp
17. rm -r /tmp/Xxxxx
18. exit
19. On the remote machine, enter the following:
    1. TERM=aixterm
    2. export TERM

Arabic/Hebrew Support

The aixterm command supports bidirectional languages such as Arabic and Hebrew. This command can open a window to be used with Arabic/Hebrew applications. You can create an Arabic/Hebrew window by specifying an Arabic or Hebrew locale (ar_AA, Ar_AA, iw_IL, or Iw_IL) with the -lang flag or by predefining an Arabic or Hebrew locale from SMIT for the system. You can also use the Web-based System Manager wsm system fast path and selecting the Cultural Environment icon.

The Arabic/Hebrew window supports bidirectional text display. Thus, English and Arabic or Hebrew text can be displayed on the same line. There are different aspects in the Arabic/Hebrew window:

• Screen Orientation
• Text mode
• Character shaping
• Numeric representation
• Status line

Screen Orientation

The screen orientation in an Arabic/Hebrew window can be either left-to-right or right-to-left. The default orientation is left-to-right unless otherwise specified with a flag or in the .Xdefaults file. While the window is active, you can reverse the screen orientation using special key combinations. You can reverse the screen orientation according to your needs.

Text Mode

An Arabic/Hebrew window supports two text modes and their corresponding manipulation:

• Implicit
• Visual

In the implicit text mode, characters are stored in same order that they are entered. The text is transformed into its visual form only when it is displayed. In the visual text mode, characters are stored in the same way that they are displayed on the window.

Character Shaping

The Arabic/Hebrew window represents Arabic and Hebrew texts differently, according to its context. Text is represented in one of the following forms:

• Automatic
• Isolated
• Initial
• Middle
• Final

Arabic/Hebrew can also be shaped according to the passthru mode.

Numeric Representation

Numerics can be represented in Arabic numerals, Hindi numerals, or in passthru mode. In implicit text mode, numerals can also be represented according to their contextual form. Thus, Arabic numbers can be displayed in English text or Hindi numbers can be displayed in Arabic text.

Status Line

The Arabic/Hebrew window can display an optional status line that shows the current status of the window. The status line contains the following values:

Use the following key combinations in an Arabic/Hebrew window to change certain settings.

For Implicit Mode only:

For Visual Mode only:

Using the aixterm Command Data-Stream Support

The following is a list of the escape sequences supported by the aixterm command.

Some escape sequences activate and deactivate an alternate screen buffer that is the same size as the display area of the window. This capability allows the contents of the screen to be saved and restored. When the alternate screen is activated, the current screen is saved and replaced with the alternate screen. Saving lines scrolled off of the window is disabled until the original screen is restored.

The following table uses these abbreviations in the right hand column:

Xv

Supported by the aixterm command running in VT100 mode.

Xh

Supported by the aixterm command running in HFT mode.

H

Found in the HFT data stream.

V

Found in the VT100 data stream.

Copy, Paste, and Re-execute Functions

When you create a terminal window, the aixterm command allows you to select text and copy it within the same window or other windows by using copy, paste, and re-execute button functions. These text functions are available in HFT and VT102 emulations. The selected text is highlighted while the button is pressed.

The copy, paste, and re-execute button functions perform as follows:

By cutting and pasting pieces of text without trailing new lines, you can take text from several places in different windows and form a command to the shell. For example, you can take output from a program and insert it into your favorite editor. Since the cut buffer is globally shared among different applications, you should regard it as a file whose contents you know. The terminal emulator and other text programs should treat it as if it were a text file, that is, the text is delimited by new lines.

Menu Usage

The aixterm command has two different menus:

• Options
• Modes

Each menu pops up under the correct combinations of key and button presses. Most menus are divided into two sections that are separated by a horizontal line. The top portion contains various modes that can be altered. A check mark is displayed next to a mode that is currently active. Selecting one of these modes toggles its state. The bottom portion of the menu provides the command entries; selecting one of these performs the indicated function.

The Options menu pops up when the Ctrl key and the left mouse button are pressed simultaneously while the mouse cursor is in a window. The menu contains items that apply to all emulation modes.

The Modes menu sets various modes for each emulation mode. The menu is activated by pressing the Ctrl key and the middle mouse button at the same time, while the mouse cursor is in the window. In the command section of this menu, the soft reset entry resets the scroll regions. This is convenient when a program leaves the scroll regions set incorrectly. The full reset entry clears the screen, resets tabs to every eight columns, and resets the terminal modes (such as wrap and smooth scroll) to their initial states after the aixterm command finishes processing the command-line options. When the Auto Linefeed option is turned on, a carriage return is added when a carriage return, vertical tab, or form feed is received. The shells generally do this for the linefeed, but not for the vertical tab or form feed.

Scroll Bar

The aixterm command supports an optional scroll bar composed of a scroll button that displays at the top of the scroll bar and a scroll region that displays at the bottom. The scroll bar is hidden until you request it to display.

The scroll region displays the position and amount of text currently showing in the window (highlighted) relative to the amount of text actually saved in the scrolling buffer. As more text is saved in the scrolling buffer (up to the maximum), the size of the highlighted area decreases.

The scroll button causes the window to scroll up and down within the saved text. Clicking the right button moves the window position up (the text scrolls downward); clicking the left button moves the window position down (the text scrolls upward). The amount of scrolling is modified by the Shift and Ctrl keys. If neither key is pressed, the window scrolls a single line at a time. Pressing the Shift key causes the text to scroll a full window at a time, minus one line. Pressing the Ctrl key causes the text to be positioned at the extreme top or bottom of the file.

Character Classes

Clicking the left mouse button (the copy function) twice in rapid succession causes all characters of the same class (that is, letters, white space, punctuation, and so on) to be selected. Because people have different preferences for what should be selected (for example, if file names be selected as a whole or only the separate subnames), you can override the default mapping by using the charClass (class CharClass) resource.

The charClass resource is a list of CharRange:Value pairs where the range is either a single number or a low-to-high number in the range of 0 to 127, corresponding to the ASCII code for the character or characters to be set. The value is arbitrary, although the default table uses the character number of the first character occurring in the set.

The default table is as follows:

static int charClass[128] = {

/* NUL  SOH  STX  ETX  EOT  ENQ  ACK  BEL */

   32,   1,   1,   1,   1,   1,   1,   1,

/*  BS   HT   NL   VT   NP   CR   SO   SI */

    1,  32,   1,   1,   1,   1,   1,   1,

/* DLE  DC1  DC2  DC3  DC4  NAK  SYN  ETB */

    1,   1,   1,   1,   1,   1,   1,   1,

/* CAN   EM  SUB  ESC   FS   GS   RS   US */

    1,   1,   1,   1,   1,   1,   1,   1,

/*  SP   !    "    #    $    %    &    ' */

   32,  33,  34,  35,  36,  37,  38,  39,

/*  (    )    *    +    ,    -    .    / */

   40,  41,  42,  43,  44,  45,  46,  47,

/*  0    1    2    3    4    5    6    7 */

   48,  48,  48,  48,  48,  48,  48,  48,

/*  8    9    :    ;    <    =    >    ? */

   48,  48,  58,  59,  60,  61,  62,  63,

/*  @    A    B    C    D    E    F    G */

   64,  48,  48,  48,  48,  48,  48,  48,

/*  H    I    J    K    L    M    N    O */

   48,  48,  48,  48,  48,  48,  48,  48,

/*  P    Q    R    S    T    U    V    W */

   48,  48,  48,  48,  48,  48,  48,  48,

/*  X    Y    Z    [    \    ]    ^    _ */

   48,  48,  48,  91,  92,  93,  94,  48,

/*  `    a    b    c    d    e    f    g */

   96,  48,  48,  48,  48,  48,  48,  48,

/*  h    i    j    k    l    m    n    o */

   48,  48,  48,  48,  48,  48,  48,  48,

/*  p    q    r    s    t    u    v    w */

   48,  48,  48,  48,  48,  48,  48,  48,

/*  x    y    z    {    |    }    ~   DEL */

   48,  48,  48, 123, 124, 125, 126,   1};

For example, the string "33:48,37:48,45-47:48,64:48" indicates that the ! (exclamation mark), % (percent sign), - (dash), . (period), / (slash), and & (ampersand) characters should be treated the same way as characters and numbers. This is very useful for cutting and pasting electronic mailing addresses and UNIX file names.

Key Translations

It is possible to rebind keys (or sequences of keys) to arbitrary strings for input. Changing the translations for events other than key and button events is not expected, and causes unpredictable behavior.

The actions available for key translations are as follows:

For example, a debugging session might benefit from the following bindings:

*aixterm.Translations: #override <Key>F13: keymap(dbx)
*aixterm.dbxKeymap.translations:\
<Key>F14: keymap(None) \n\
<Key>F17: string("next") string(0x0d) \n\
<Key>F18: string("step") string(0x0d) \n\
<Key>F19: string("continue") string(0x0d) \n\
<Key>F20: string("print") insert-selection(PRIMARY)

Key and Button Bindings

The key and button bindings for selecting text, pasting text, and activating the menus are controlled by the translation bindings. In addition to the actions listed in the Key Translations section, the following actions are available:

The default bindings are:

static char defaultTranslations =
"                    <KeyPress>:  insert() \n\ 
~Shift Ctrl   ~Meta  <Btn1Down>:   mode-menu(options) \n\ 
~Shift Ctrl   ~Meta  <Btn2Down>:   mode-menu() \n\ 
~Shift Ctrl   ~Meta  <Btn3Down>:   mode-menu(modes) \n\ 
~Shift ~Ctrl  ~Meta  <Btn1Down>:   select-start() \n\ 
~Shift ~Ctrl  ~Meta  <Btn1Motion>: select-extend() \n\ 
~Shift ~Ctrl  ~Meta  <Btn1Up>:     select-end(PRIMARY)\n\ 
~Shift ~Ctrl  ~Meta  <Btn2Down>:   ignore() \n\ 
~Shift ~Ctrl  ~Meta  <Btn2Up>:     insert-selection(PRIMARY)\n\ 
~Shift ~Ctrl  ~Meta  <Btn3Down>:   start-extend() \n\ 
~Shift ~Ctrl  ~Meta  <Btn3Motion>: select-extend() \n\ 
~Shift ~Ctrl  ~Meta  <Btn3Up>:     select-end(PRIMARY)\n\ 
Shift ~Ctrl   ~Meta  <Btn1Down>:   reexecute() \n\ 
Shift ~Ctrl   ~Meta  <Btn1Motion>: select-extend() \n\ 
Shift ~Ctrl   ~Meta  <Btn1Up>:     select-end(PRIMARY)\n\ 
Shift ~Ctrl   ~Meta  <Btn2Down>:   select-start() \n\ 
Shift ~Ctrl   ~Meta  <Btn2Motion>: select-extend() \n\ 
Shift ~Ctrl   ~Meta  <Btn2Up>:     select-end(PRIMARY)\n\ 
Shift ~Ctrl   ~Meta  <Btn3Down>:   ignore() \n\ 
Shift ~Ctrl   ~Meta  <Btn3Up>:     insert-selection(PRIMARY)\n\ 
Shift Ctrl    ~Meta  <BtnDown>:    size(toggle) \n\ 
Shift Ctrl    ~Meta  <BtnUp>:      ignore() \n\ 
                     <BtnDown>:    bell(0) \n\ 
                     <BtnUp>:      bell(0) \n\ 
";

aixterm Command Internationalization (I18N)

To run an aixterm with a different keyboard layout than the X server's (such as a French keyboard layout on a Swiss German X server), run the following commands:

1. Change the X server to a French keyboard:

   xmodmap /usr/lpp/X11/defaults/xmodmap/Fr_FR/keyboard

2. Set the locale environment variable to Fr_FR using one of the following:
   • For Korn shells: export LANG=Fr_FR
   • For C shells: setenv LANG Fr_FR
   • For Bourne shells: LANG=Fr_FR; export LANG
3. Start an aixterm terminal emulator:

   aixterm &

4. Reset the X server's keyboard file to its original language:

   xmodmap /usr/lpp/X11/defaults/xmodmap/Gr_SW/keyboard

The aixterm command continues to use the keyboard layout that the X server was using when the aixterm started. It ignores KeymapNotify by default.

The aixterm command uses the Input Method to convert the X server's keysyms into either printable characters or nonprintable escape strings such as function keys. The Input Method uses its own keymap files, in /usr/lib/nls/loc, to convert X keysyms into code points for the printable characters, and escape strings for nonprintable characters. There is a keymap file for each language and one keymap file for escape sequences. The escape sequences are in C@outbound.imkeymap; the source is C@outbound.imkeymap.src. The other keymap files begin with the locale name and look like: locale.imkeymap and locale.codeset.imkeymap. For example:

The following dependencies apply:

• You can change the locale by entering the following SMIT fast path: smit mle_sel_menu, or by using the Web-based System Manager wsm system fast path and selecting the Cultural Environment icon. You can also change the locale temporarily by modifying the LANG environment variable.
• You can change the system keyboard definition by selecting the following SMIT menu items: System Environments, Manage Language Environment, and Change the Keyboard Map for the Next System Restart, or by using the Web-based System Manager wsm system fast path and selecting the Cultural Environment icon.
• Codeset depends on the locale (LC_ALL, LANG environment variables).
• Default fonts and font sets depend on the codeset and locale. Using a font that does not match the codeset may produce incorrect output.
• Input Method depends on the locale. The Input Method for the locale should be installed. The Input Method maps Keysyms to a codeset.
• Compose keys (dead keys) depend on the Input Method and X keyboard mapping. An incorrect input method or X keyboard mapping may produce incorrect input.
• Error messages and menu contents depend on the locale and a correct font or fontset. The message catalogs for the locale should be installed. The default messages are English. An incorrect font or fontset can result in garbled menu text and messages.
• Text display depends on the locale and a correct font or fontset. An incorrect font or fontset can result in garbled text. Changing the locale (LC_ALL, LANG environment variables) in an aixterm does not change the codeset that the aixterm displays. If the codeset of the new locale differs from the codeset of aixterm, incorrect output (garbled text) may be displayed.
• The X keyboard mapping depends on the system keyboard definition. Xinit sets the X keyboard mapping to match the system keyboard definition. The mapping is changed with xmodmap. The X keyboard mapping maps key presses to Keysyms.

Availability of Characters in aixterm

ASCII characters 32 (0x20) to 126 (0x7e) are available in most of the codesets and fonts. Characters (bytes) 0 (0x00) to 31 (0x1f) are treated as control sequences and unprintable characters. Other characters 127 (0x7f) to 255 (0xff) vary with codeset and fonts. Using a font that does not match the codeset the aixterm is started in leads to unpredictable results. For example, box characters (line drawing) are available in aixterm vt100 mode with the default vtsingle font. If you use a different font, other characters may be displayed instead. Another example is using a ISO8859-1 font while running in the IBM-850 codeset. Trying to display box characters (line drawing) generates accented characters. Trying to display accented characters generates different accented characters or blanks.

Key Assignments for Bidirectional Languages

In addition to the above key and button bindings, the following key assignments for bidirectional languages are supported by the aixterm command:

The BIDI bindings (for Arabic/Hebrew) are:

~Shift ~Ctrl Mod1   <Key>Return:         scr-rev() \n\
~Shift ~Ctrl Mod2   <Key>Return:         scr-rev() \n\
~Shift ~Ctrl Mod1   <Key>Shift_L: ltr-lang() \n\ 
~Shift ~Ctrl Mod2   <Key>Shift_L: ltr-lang() \n\
~Shift ~Ctrl Mod1   <Key>Shift_R: rtl-lang() \n\
~Shift ~Ctrl Mod2   <Key>Shift_R: rtl-lang() \n\
~Shift ~Ctrl Mod1   <Key>KP_Multiply:    col-mod() \n\ 
~Shift ~Ctrl Mod2   <Key>KP_Multiply:    col-mod() \n\
~Shift ~Ctrl Mod1   <Key>KP_Divide:      auto-push() \n\
~Shift ~Ctrl Mod2   <Key>KP_Divide:      auto-push() \n\
~Shift ~Ctrl ~Meta  <Key>KP_Divide:      chg-push() \n\ 
~Shift ~Ctrl Mod1   <Key>KP_1:           shp-in() \n\ 
~Shift ~Ctrl Mod2   <Key>KP_2:           shp-in() \n\
~Shift ~Ctrl Mod1   <Key>KP_1:           shp-is() \n\
~Shift ~Ctrl Mod1   <Key>KP_2:           shp-is() \n\
~Shift ~Ctrl Mod1   <Key>KP_3:           shp-p() \n\
~Shift ~Ctrl Mod2   <Key>KP_3:           shp-p() \n\
~Shift ~Ctrl Mod1   <Key>KP_4:           shp-asd() \n\
~Shift ~Ctrl Mod2   <Key>KP_4:           shp-asd() \n\
~Shift ~Ctrl Mod1   <Key>KP_7:           shp-m() \n\
~Shift ~Ctrl Mod2   <Key>KP_7:           shp-m() \n\
~Shift ~Ctrl Mod1   <Key>KP_8:           shp-f() \n\
~Shift ~Ctrl Mod2   <Key>KP_8:           shp-f() \n\

You can change these values in the .Xdefaults file. For example, if you want to use Ctrl+Shift to change language layer, you can add the following line in the .Xdefaults file:

Translations:   Ctrl<Key>Shift_R: rtl-lang() \n\
                Ctrl<Key>Shift_L: ltr-lang()   

Flags

A flag takes on the opposite value if the - (minus sign) is changed to a + (plus sign). The following options override those set in the .Xdefaults file:

aixterm -f0 rom11

.Xdefaults Keywords

Use the following keywords to set the defaults for the aixterm command.

Example

The following example can be used to create an aixterm, specifying the size and location of the window, using a font other than the default, and also specifying the foreground color that is used in text. The aixterm command then runs a command in that window.

aixterm -geometry 20x10+0+175 -fn Bld14.500 -fg DarkTurquoise -e 
/tmp/banner_cmd &

The aixterm command is NOT an X Toolkit based application. Because of this, the aixterm command gets resource files as follows:

• System defaults from the first of these it finds:

  $XFILESEARCHPATH %T=app-defaults %N=Xdefaults %L=$LANG
  $XFILESEARCHPATH %T=app-defaults %N=Xdefaults %L=
  /usr/lpp/X11/defaults/$LANG/Xdefaults
  /usr/lpp/X11/defaults/Xdefaults
  /usr/lib/X11/$LANG/app-defaults/Xdefaults
  /usr/lib/X11/app-defaults/Xdefaults
  /usr/lpp/X11/defaults/app-defaults/Xdefaults

• Application system defaults from the first of these it finds:

  $XFILESEARCHPATH %T=app-defaults %N=Aixterm %L=$LANG
  $XFILESEARCHPATH %T=app-defaults %N=Aixterm %L=
  $XFILESEARCHPATH %T=app-defaults %N=aixterm %L=$LANG
  $XFILESEARCHPATH %T=app-defaults %N=aixterm %L=
  /usr/lpp/X11/defaults/$LANG/Aixterm
  /usr/lpp/X11/defaults/Aixterm
  /usr/lib/X11/$LANG/app-defaults/Aixterm
  /usr/lib/X11/app-defaults/Aixterm
  /usr/lib/X11/defaults/app-defaults/Aixterm
  /usr/lpp/X11/defaults/$LANG/aixterm
  /usr/lpp/X11/defaults/aixterm
  /usr/lib/X11/$LANG/app-defaults/aixterm
  /usr/lib/X11/app-defaults/aixterm
  /usr/lib/X11/defaults/app-defaults/aixterm

• User application defaults from the first of these it finds:

  $XUSERFILESEARCHPATH %T=app-defaults %N=Aixterm %L=$LANG
  $XUSERFILESEARCHPATH %T=app-defaults %N=Aixterm %L=
  $XUSERFILESEARCHPATH %T=app-defaults %N=aixterm %L=$LANG
  $XUSERFILESEARCHPATH %T=app-defaults %N=aixterm %L=
  $XAPPLRESDIR/$LANG/Aixterm
  $XAPPLRESDIR/Aixterm
  $XAPPLRESDIR/$LANG/aixterm
  $XAPPLRESDIR/aixterm
  $HOME/$LANG/Aixterm
  $HOME/Aixterm
  $HOME/$LANG/aixterm

• User defaults from the first of these it finds:

  dpy->xdefaults          (A.K.A. "RESOURCE_MANAGER" property)
  $HOME/$LANG/.Xdefaults
  $HOME/.Xdefaults

• Host defaults from the first of these it finds:

  $XENVIRONMENT
  $HOME/$LANG/.Xdefaults-hostname
  $HOME/.Xdefaults-hostname

  Note: XFILESEARCHPATH and XUSERFILESEARCHPATH support is limited to the %T, %N and %L substitution strings. Also, $LANG is actually whatever the result of the setlocale(LC_CTYPE,NULL) call is.