Note that wordview script haven't changed since 0.91.7. So test with recents upstream version would reproduce the results.
Really I've encountered simular problems in the lot of other tcl/tk programs (such as tkabber, alicq, proprietary programs I develop to earn my living). Problem can be more accurately described as: Sometimes Tk picks up a wrong font which causes BadValue error on X server when attempting to display some characters. It might be if font is marked as Unicode but doesn't contain required character. Upon this exception application is terminated without any attempt to recover, I've posted this problem into Tk upstream bugzilla, but currently SF is down for maintainance, so I cannot provide exact URL to the report. Recently I've encountered very simular error in Gtk based program (vmware). So, it might be low-level xlib problem. Unfortunately, problem is quite hard to reproduce. As work-around it might be suggested to specify Wordview.Text.Font resource in the X resource database to use some unicode truetype font. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
