Comment 14 for bug 275020

Yes, "encoding names" command shows the same encodings for tclsh8.5 and for tclkit8.5
There is some posts in Internet about different model of working with encodings in tclsh and tclkit - for example http://groups.google.ru/group/comp.lang.tcl/browse_thread/thread/ba74f4fef7bdb12a/6f51fde1a6f63766?q=tclkit+tclsh&rnum=2#6f51fde1a6f63766

Could it be because of it?
Anyway, if 0.96.8 for Windows works fine, this must be not code problem, but tclkit problem...