NAME

kterm − terminal emulator for X

SYNOPSIS

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

DESCRIPTION

kterm 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 is derived from the xterm (Release 4) terminal emulator found in the core distribution of the X Window System.  kterm provides the basic functions of xterm plus the ability to displays Kanji strings. 

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 “k14”.

−fkb kanji-bold-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, the normal Kanji font will be used as the Kanji bold font, and the bold font will be produced by overstriking this font. The default is not specified.

−fr kana-font
This option specifies a Kana font, which may be used as GR in 8bit environment. This font is used if “ESC ( I” appears in JIS Kanji mode or SS2 (0x8e) appears in EUC Kanji mode.  It is not frequently used in normal Japanese text. The default is “kana14”.

−frb kana-bold-font
This option specifies a Kana bold font.  This font must be the same height and width as the kanji font. If no Kana bold font is specified, the normal Kana font will be used as the Kana bold font, and the bold font will be produced by overstriking this font.  The default is not specified.

−km kanji-mode
This option specifies the interpretation of Kanji codes from the pty output. If kanji-mode is “jis”, then it assumes the input/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 module because 7 bit encoding with appropriate escape sequences is used. If kanji-mode is “euc”, then it assumes the input/output is coded by EUC. If kanji-mode is “sjis”, then it assumes the input/output is coded by Shift-JIS code (which is the same as MicroSoft Kanji code). The default mode is “jis”.

STARDENT EXTENSIONS

Since this port of kterm is on the R4 version of xterm, the R4 xterm font menu feature has been modified for use on kterm.  The font menu allows up to five (5) fonts to be defined via resources.  In addition, a font from the current selection can be used and stored as a sixth entry in the font menu.  Modifications made to kterm allows four (4) additional fonts to be defined (via resources) for each of the font menu entries.  These resources define the kana font, kana bold font, kanji font and kanji bold font for that menu entry.  Note that the the size of the kana/kanji fonts must be the same as that of the regular font for that menu entry.  A font selected via the selection mechanism is only valid for the main font, not for the kana/kanji fonts.  Refer to the application defaults file /usr/lib/X11/app-defaults/KTerm for additional details. 

X DEFAULTS

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

kanjiFont, kanjiFont1..kanjiFont4 (class KanjiFont)
Specifies the name of the kanji font.  The default is “k14.”

kanjiBoldFont, kanjiBoldFont1..kanjiBoldFont4 (class KanjiFont)
Specifies the name of the bold font.  The default is not specified.

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

kanaBoldFont, kanaBoldFont1..kanaBoldFont4 (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.”

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”.  xterm automatically searches the termcap file in this order for these entries and then sets the “TERM” and the “TERMCAP” environment variables. 

SEE ALSO

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

BUGS

Kterm assumes that the width of Kanji characters is twice that of ASCII characters. Of course variable-width fonts are not handled like xterm. 

This version of kterm uses “ESC $ B” to designate the Kanji character set in tty output when JIS mode is selected.  There is no way to specify “ESC $ ( B” instead. 

Because of a historical reason in Japan, the sequence to designate Swedish character set “ESC ( H” is treated as that of Japanese roman character set. 

There is no distinction between ASCII and Japanese roman character sets, though the latter includes the “Yen” character, interrupted bar and upper score. 

Currently available xterm and previously released kterm can not paste a Kanji text from this kterm because we are not allowed to store the selected Kanji text into the cut buffer or selection with STRING type, as defined in the ICCCM,

COPYRIGHT

Copyright 1988 and 1989, 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, Inc.), Makoto Ishisone (Software Research Associates, Inc.), Hiroto Kagotani (Tokyo Inst. of Tech.) Send bugs to kagotani@cs.titech.ac.jp, please.

March 13, 1992