On 6/25/12 6:08 AM, Prashant Deshmukh wrote:
> This is problem with just one of those strings. for this just installing
> unicode version doesn't seem feasible.
> does this don't have any simple solution.
Switching to the unicode build may not be the simplest solution, but it
is the smartest. There will not be any more separate ansi builds of
wxPython starting with 2.9.x, and it is likely that there will not be
any more 2.8.x releases either. So switching to unicode now will make
moving on to the next release much easier.
If you really must stick with the ansi build for some reason then you
can solve this particular problem by telling wxPython to use a different
encoding when it converts to/from string/unicode for the wx APIs, using
something like wx.SetDefaultPyEncoding('utf-8')
BTW, how did the � get in to the wx.Choice string?
--
Robin Dunn
Software Craftsman
http://wxPython.org