It sounds like a limitation in PyGTK which might be a bug (because of
its non-symmetric nature across different API calls). However rather
than waiting for any potential bug fixes, try a closer look at the
gettext module. There are multiple different, yet semantically
similar, functions which can be installed as _. One of those returns
str strings instead of unicode strings.
I'm aware of the different versions of the gettext() functions, but I
prefer sticking with unicode.
I suppose I'll file a bug report, even if the severity of the problem is
low, since it can be easily worked around.
BTW, my project is an open source mapper for roleplaying games, using
Cairo and GTK+ through Python:
http://sourceforge.net/projects/hectormapper/
I must say using PyGTK has been very fun.
Thank you,
Alfonso Tarantini
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
