Thank you for your response! I followed your advice to ask on the " tcl-mac" list, and was told that the problem is known, and a patch exists: The patch has not yet been integrated into the TkAcqua main branch because it slows text processing down a lot. Someone is working on this, and it may be folded into the main branch soon.

For description of the patch see "[ 638966 ] Font rendering on MacOSX with ATSU":

http://sourceforge.net/tracker/index.php?func=detail&aid=638966&group_id=12997&atid=312997


On 17-nov-04, at 23:13, Read Roberts wrote:

Thanks for confirming that it is not just my system!

I'm pretty sure that it the problem is in Tk rather than Python/Tkinter , as I can do Entry_widget.cget('txt') and get the right string back, and can even cut and paste from the Entry widget to other apps and still get the original Unicode back ( well, UTF-8, but it is still correct).

Looks like I will have to go spelunking in TK to find the cause - anyone have suggestions about where to start?

First ask on the mailing list for Mac Tcl/Tk developers, <[EMAIL PROTECTED]>. It may be a known problem. And they're friendly to Python/Tkinter users over there, too:-)
--
Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma Goldman

_______________________________________________ Pythonmac-SIG maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/pythonmac-sig

Reply via email to