Fri Nov 26 21:48:57 JST 1999 Japanese version is here.

Tcl/Tk 8.0 Japanization patch

Tcl/Tk Japanization patch is an implementaion of Japanese localization of Tcl/Tk 8.0, known as Tcl/Tk 8.0jp.
Current version is 1.7, UNIX & Windows platforms are supported.

Main Japanization features are:

Support iso-2022-jp(jis), shift-jis, euc-jp auto detection and conversion.

Font compounding mechanism, to create a named font like "use Helvetica in ascii range, use Mincho in kanji range".

Supports kanji input, using kinput protocol and XIM protocol on UNIX, IME on Windows.

Supports to handle multi byte kanji string by "kanji", "kstring" commands.

Of course all Tk Widgets can display kanji :), and also supports Japanese "Kinsoku" management.

Latest version's information

The latest patch for Tcl 8.0.5 (tcl8.0.5jp1.7, released 1999 Nov 27, 86KB), and a change log

The latest patch for Tk 8.0.5 (tk8.0.5jp1.7, released 1999 Nov 27, 310KB), and a change log

The latest binary for Windows (Updated 1999 Nov 27, 1.2MB)

On Nov 27 1999, Tcl/Tk8.0.5jp1.7 is released. Here is a patch for the tcl8.0.5jp1.6, and Here is a patch for the tk8.0.5jp1.6.

Changes from tcl8.0.5jp1.6 to tcl8.0.5jp1.7

Basically, these are citations from the change log.

Now tcl80jp.dll and tclsh80jp.exe have proper version/codepage informations (Win).

Tcl couldn't exec 16 bit application at all on Windows 9[58] environment (Win).

Fix NULL pointer freeing in tkUnixFile.c (UNIX).

Changes from tk8.0.5jp1.6 to tk8.0.5jp1.7

Basically, these are citations from the change log.

Now tk80jp.dll and wish80jp.exe have proper version/codepage infomations. (Win)

PostScript output in canvas widget now can generate proper stippled Kanji text. (UNIX/Win)

More than one %A in bind script didn't work properly. (UNIX)

{PreeditPosition StatusArea} conversion mode (AKA "over-the-spot") hadn't work properly from when the "on-the-spot" style were implemented. I enbug'd. (UNIX)

Better support of IM server using TCP transport other than X transport, like Xwnmo. FYI, the X transport was used in Ximp, the TCP transport was used in Xsi. (UNIX)

If XMODIFIERS environmental variable is set to "@im=none", Tk won't use XIM protocol, use kinput protocol instead. (UNIX)

If you want to use "on-the-spot conversion" input method style, You need an IM server that supports XIMPreeditCallbacks|XIMStatusCallbacks style. My recomendation is The latest version of Kinput2.