 a subset of ISO-2022 where a part of ISO-2022 control codes and escape sequences are not supported. Many popular encodings belong to this category such as ISO-8859-*, EUC-*, ISO-2022-KR, TIS-620, TCVN5712, and so on.
Some of popular encodings such as Shift_JIS, Big5, GBK, GB18030, Johab, and so on belongs to this category.
ISO-2022-JP, ISO-2022-JP-2, ISO-2022-JP-3, EUC-TW, and so on. All of them are ISO-2022-compliant.
*1 Characters from unsupported character sets (i.e., characters which cannot be expressed in the mlterm encoding) may appear in the selection (received copy-and-paste string). If you want to receive characters which are equivalent to characters which are supported in the current mlterm encoding (i.e., characters which share the same codepoint in Unicode), you can use -U (or --viaucs) option. Otherwise, these characters are pasted into mlterm using ISO-2022 escape sequence (when mlterm encoding is category b). Note such ISO-2022 escape sequences are illegal in the current mlterm encoding and the application software will need special feature to treat them properly, though it is displayed well in mlterm. When mlterm encoding is category c, such characters are simply ignored (when -U option is not enabled).
*3 Characters from unsupported character sets will be pasted into mlterm using ISO-2022 escape sequence.
mlterm loads configuration files of "main", "font", "vfont", "tfont", "aafont", "vaafont", "taafont", "color", "key", "termcap", and "xim" on start up. "menu" configuration file is loaded by the configurable menu displayer (mlterm-menu). See the section of CONFIGURABLE MENU for detail.
Configuration files for one user are to be located in "~/.mlterm/" directory, while location for configuration files for all users depends on the compilation option. Possible locations are "/etc/", "/etc/X11/", "/usr/X11R6/lib/X11/mlterm/", and so on.
Main configuration items which can be overridden by command line options.
Configurations for ordinary X fonts.
Configurations for ordinary X fonts of variable column width.
Configurations for ordinary X fonts of vertical writing.
Configurations for Xft or cairo fonts.
Designate concrete RGB values for color names.
Key definitions for special features of mlterm.
Define preset locales for X Input Methods which are shown in the GUI configurator. Of course you can input XIM names and locales for the GUI configurator which are not listed in this configuration file.
Define menu items which is displayed by configurable menu displayer.
The contents of these configuration files (other than menu) consist of lines of "key=value" format. Lines beginning with "#" are ignored.
This file contains main configuration items which can be overridden by command line options. The main configuration file "main" has the following keys. Parentheses show the corresponding command-line options. See the explanation on these command-line options for detail.
Application name. auto_restart=bool (--restart) Restart mlterm with all opened ptys except ssh if SIGSEGV, SIGBUS, SIGFPE or SIGILL is received. If you want to get core image, specify "false".
Specify number of extra dots between letters. (ignored if you specify --V option.) If you use multiple fonts whose widths are different, adjust this option.
Specify number of extra dots between lines. If you use multiple fonts whose heights are different, adjust this option.
If the received selection (i.e., copy-and-paste strings) or strings received from XIM is not UTF8_STRING type, convert it into Unicode and then to the current mlterm encoding, in order to identify equivalent characters (i.e., characters which share the same codepoint in Unicode) from various character sets. See SELECTION section below for detail.
Specify actual screen height.
Specify actual screen width.
Automatically detect appropriate character encoding from the encodings specified by auto_detect_encodings option.
The font configuration files "font", "vfont", "tfont", "aafont", "vaafont", and "taafont" have the following keys.
Specify fonts for corresponding character sets. The format is different between "font", "vfont" "tfont" files and "aafont", "vaafont" "taafont" files.
In "font", "vfont", "tfont" files, "font" is specified in "NAME:PERCENT;SIZE,NAME:PERCENT;SIZE,NAME:PERCENT;..." format where "SIZE" is font size in pixel, and "NAME" is XLFD or alias names of X fonts. If the first "NAME" contains "%d", it is replaced by an appropriate font size number. ":PERCENT" is multiplied by font size and decides character width of a font. If ":PERCENT" is omitted, max font width is used for it.
In "aafont", "vaafont", "taafont" files, "font" is specified in "FAMILY WEIGHT SLANT SIZE-ENCODING:PERCENT;SIZE,FAMILY WEIGHT SLANT SIZE-ENCODING:PERCENT;SIZE,FAMILY WEIGHT SLANT SIZE-ENCODING:PERCENT;..." format. The first pair of FAMILY WEIGHT SLANT SIZE and ENCODING specifies the default font and the others with SIZE are for specific sizes. ":PERCENT" is multiplied by font size and decides character width of a font. If ":PERCENT" is omitted, 'W' width is used for it.
Assign a concrete color for the name COLORNAME. Default colors used by mlterm are black, red, green, yellow, blue, magenta, cyan, and white. and can be overridden here.
For hilighted colors, a name with "hl_" prefix will be automatically searched. i.e. for bold read character, "hl_red" is searched instead of "red".
The format of RGB is either "RRRR-GGGG-BBBB" (where RRRR, GGGG, and BBBB are hexadecimal value from 0 to ffff), "#RRGGBB", "#RRGGBBAA", "rgb:RR/GG/BB" or "rgba:RR/GG/BB/AA"(where RR, GG, and BB are hexadecimal value from 00 to ff).
These settings are used to create list of XIMs by the GUI configurator. Though a XIM which is not listed in this file can't be selected from the list, it can be selected by specifying its name directly.
Here, the format for KEY is "(MASK+)KEY", where MASK is one of Control, Shift, Mod1, Mod2, Mod3, Mod4, Mod5, Mod and Alt. You can specify multiple "MASK+"s. You can search spellings of KEY by using xev(1) command or searching keysym macros from /usr/X11R6/include/X11/keysymdefs.h (or the equivalent file in your X11 include directory) and omit the prefix XK_. Double quotation marks are not needed. You can specify Button1, Button2, Button3, Button4 or Button5 as KEY.
FEATURE is one of IM_HOTKEY, EXT_KBD, OPEN_SCREEN, NEW_PTY, OPEN_PTY, NEXT_PTY, PREV_PTY, VSPLIT_SCREEN, HSPLIT_SCREEN, CLOSE_SCREEN, NEXT_SCREEN, PREV_SCREEN, HEXPAND_SCREEN, VEXPAND_SCREEN, PAGE_UP, PAGE_DOWN, SCROLL_UP, SCROLL_DOWN, INSERT_SELECTION, "STRING", or "proto:STRING".
Open new pty in horizontally splitted screen (default Shift+F1).
Open new pty in vertically splitted screen (default Shift+F2).
Scroll down one page. (default Shift+Next).
Start backscroll mode and scroll up by one line (default Shift+Up). Note this key is enabled only when -q/--extkey option is used.
Scroll down one line (default Shift+Down). Note this key is enabled only when -q/--extkey option is used.
The specified string is issued when the KEY key is pressed. Double quotation marks are required around the STRING. Note that you cannot control the status of mlterm by sending terminal control codes such as "\x1b]5379;encoding=utf8\x0a" because the code sequence will be caught by your shell (or something running on it). To deliver control sequences to mlterm directly, use "proto:STRING" instead.
The specified string is assumed to mlterm's original control sequence. A list of sequences should be found in doc/en/PROTOCOL. For example, "proto:encoding=utf8" means changing the current character encoding to UTF-8