Tkoutline and non-ascii characters
Not logged in

2006-04-15 Helmut - Want tu use Chinese Characters and tried to start tkoutline-i18n-0.93.exe, but get the msg couldn't open setup.tcl, then if I supply an empty one init.tcl. What am I doing wrong? Thank you very much Helmut

Brian Theado - I'm having trouble duplicating the problem so I'm not sure what is going on. Is there more to the message "couldn't open setup.tcl"? If you can provide more details that would be helpful. Also, does the normal tkoutline download work for you?

2006-03-01 Brian Theado - Fixing problems with international characters in tkoutline 0.93

If you want to be able to enter international characters into tkoutline, then some missing encoding files need to be added. I added the encoding files and made a download available at

Then, there is a second problem with the international characters being lost when saving and then reloading from disk. One way to fix that is to place the following line in your startup script:

 encoding system utf-8

You can get to your startup script by going to Edit->Edit Startup Script.


About non-ascii characters problem. This is not only tkoutline problem, but tclkit problem too. Standard tclsh and wish consoles detect my "encoding system" as cp1251. And no problems. But tclkit and tkoutline consoles detect my "encoding system" as cp1252. And can not set another encoding: "unknown encoding cp1251".

Brian, can you distribute tkoutline not only as starpack and starkit but as wish script too?

const mech.

ps. Now I download source code from tkoutline-0.93.tar.gz There are no problem with non-ascii characters. But there is the problem for edited file saving:

 unknown option "a node": should be "::outlinewidget::tree1 walk root ?-type {bfs|dfs}? ?-order      {pre|post|in|both}? -command cmd"
 unknown option "a node": should be "::outlinewidget::tree1 walk root ?-type {bfs|dfs}? ?-order {pre|post|in|both}? -command cmd"
     while executing
 "::struct::tree::_walk ::outlinewidget::tree1 root -order both {a node} {
         switch $a {
            enter {
                lappend list [bad-link: $tree g..."
    ("uplevel" body line 1)
    invoked from within
 "uplevel 1 [linsert $args 0 ::struct::tree::$sub $name]$tree g..."
    ("uplevel" body line 1)
    invoked from within
 "uplevel 1 [linsert $args 0 ::struct::tree::$sub $name"
    (procedure "::struct::tree::TreeProc" line 19)
    invoked from within
 "tree1 walk root -order both {a node} {
        switch $a {
            enter {
                lappend list $tree getall $node {}

Brian Theado - Thanks. The input problem is a problem with lack of encoding files and then ther e is also a problem with saving non-ascii. Thanks for the tar.gz error report--I'll have to look into that.

14Feb2006 Just downloaded the latest version of TKoutline today (Feb. 14), and it looks gereat!

One minor problem/question, though: I can't get it to display characters in Hebrew (although if I copy Hebrew text from another application into TKOutline, the Hebrew letters are displayed) -

Brian Theado - What exactly are you doing when you can't get it to display the characters in Hebrew? How do you get the Hebrew text into the other application?

01Mar2006 - Brian Theado - I got information from Lieb via email and here is a summary on how to duplicate the problem:

Add hebrew input ability to windows XP

Languages Tab, and in the Supplemental language support section check the box that says "install files for complex script and right-to-left languages".

Enable hebrew input

Languages Tab, and under Text services and Input Languages, click Details.

choose the key combination/language bar settings for inputting Hebrew.

Try entering hebrew into tkoutline


The link above details a bug from a user and it contains some reponses from me about preserving non-ascii characters when saving an outline. I am new to Unicode and encodings. If anyone else has a clue to add, then please help in the discussion.