NAME

kterm − terminal emulator for X

SYNOPSIS

kterm [-toolkitoption ...] [-option ...]

DESCRIPTION

The kterm program is a Kanji terminal emulator for the X Window System.  It provides DEC VT102 and Tektronix 4014 compatible terminals for programs that can’t use the window system directly.  It comes from xterm in the core programs of the distribution of the X Window System.  The most of the functions are the same as original xterm’s, however, it has capabilities of displaying Kanji strings and handling of the status line, if compiled with -DKANJI or -DSTATUSLINE compile time options. 

OPTIONS

The kterm terminal emulator accepts all of the standard xterm command line options along with the additional options listed below (if the option begins with a ‘+’ instead of a ‘−’, the option is restored to its default value):

−fk kanji-font
This option specifies a Kanji font to be used when displaying Kanji text. This font must be the same height and width as the ascii font. The default is “a14.”

−fkb kanji-font
This option specifies a Kanji bold font to be used when displaying bold text. This font must be the same height and width as the kanji font. If no Kanji bold font is specified, it will be used as the normal font and the bold font will be produced by overstriking this font. The default is not specified.

This option specifies a Kana font, which may be used as GR in 8bit environment.  This font is used if “ESC ( I” is appeared in JIS Kanji mode, SS2 (0x8e) is appeared in EUC Kanji mode, and not used so frequntly in normal Japanese text.  The default is “kana14.”

b kana-font
This option specifies a Kana bold font.

−km  kanji-mode
This option specifies the Kanji code from the pty output. If kanji-mode is “jis”, then it assumes the output is coded by JIS code, i.e., each Kanji string is proceeded by ESC-$-B or ESC-$-@ and each ascii string is proceeded by ESC-(-B or ESC-(-J. This mode does not require 8 bit passing tty modele because 7 bit encoding with appropriate escape sequences is used. If kanji-mode is “euc”, then it assumes the output is coded by EUC. If kanji-mode is “sjis”, then it assumes the output is coded by Shift-JIS code (which is the same as MicroSoft Kanji code). The default mode is “jis.”

−sn By default, the status line is in reverse-video (relative to the rest of the window).  This option causes the status line to be in normal video (the status line is still enclosed in a box). 

−st This option causes the status line to be displayed on startup. 

X DEFAULTS

The program understands all of the core xterm resource names and classes as well as:

kanjiFont (class KanjiFont)
Specifies the name of the kanji font.  The default is “a14.”

kanjiboldFont (class KanjiFont)
Specifies the name of the bold font.  The default is not specified.

kanaFont (class KanaFont)
Specifies the name of the kana font.  The default is “kana14.”

kanaboldFont (class KanaFont)
Specifies the name of the bold font.  The default is not specified.

kanjiMode (class KanjiMode)
Specifies the Kanji code of pty output. The default is “jis.”

statusLine (class StatusLine)
Causes the status line to be displayed on startup.

statusNormal (class StatusNormal)
Specifies whether or not the last column bug in cursor should be worked around. The default is “false.”

EMULATIONS

The VT102 emulation is fairly complete, but does not support the blinking character attribute nor the double-wide and double-size character sets.  Termcap(5) entries that work with xterm include “kterm”, “xterm”, “vt102”, “vt100” and “ansi”, and xterm automatically searches the termcap file in this order for these entries and then sets the “TERM” and the “TERMCAP” environment variables. 

POINTER USAGE

Kterm converts the specified text by the cut operation into JIS code regardless of the Kanji mode and then saves it to the Xserver.  This convention allows us to cut and paste between different kterm’s with differecnt Kanji mode. 

SEE ALSO

xterm(1), resize(1), X(1), pty(4), tty(4)
“Xterm Control Sequences”

BUGS

Xterm will hang forever if you try to paste too much text at one time. It is both producer and consumer for the pty and can deadlock. 

Variable-width fonts are not handled reasonably. 

This program still needs to be rewritten.  It should be split into very modular sections, with the various emulators being completely separate widgets that don’t know about each other.  Ideally, you’d like to be able to pick and choose emulator widgets and stick them into a single control widget. 

The focus is considered lost if some other client (e.g., the window manager) grabs the pointer; it is difficult to do better without an addition to the protocol. 

There needs to be a dialog box to allow entry of log file name and the COPY file name. 

Many of the options are not resettable after xterm starts. 

All programs should be written to use X directly; then we could eliminate this program. 

Current kterm does not support the designate sequence of KANJI as “ESC $ ( B” but “ESC $ B” which is still valid sequence in ISO 2022 (even if it seems to be historical reason :-)

COPYRIGHT

Copyright 1988, XXI working group in Japan Unix Society Japan. 
See X(1) for a full statement of rights and permissions. 

AUTHORS

Far too many people, including: Katsuya Sano (Tokyo Inst. of Tech.), Michael Irie (Sony Corp.), Akira Kato (Tokyo Inst. of Tech.), Michiharu Ariza (Software Research Associates), Makoto Ishisone (Software Research Associates)

September 29, 2021