>tclkit-win32-sh
% set name �������
�������
% string toupper $name
������┴
% exit
>tclsh
% set name �������
�������
% string toupper $name
�������
%
[email protected]

There have been a number of encoding issues with tclkit, some of them caused
by a serious startup issue in Tcl itself (needing encodings before the system has
initialized itself far enough to be able to load those from the database embedded
in the Tclkit executable).
I wish I knew how to resolve this problem :(
You might be able to force a proper interpretation of encodings by calling "encoding
system ..." as part of your startup, i.e. in your Tcl scripts.
-jcw