Problems with textcrtl and WriteText, AppendText

Hi,
under Linux (Suse9.1, KDE), with Python 2.3.3, wxPython 2.5.2.8 (non-Unicode)
the following code does only insert the C with cedille when written as such in the source code. It does not insert it when written as WriteText('\xc3'), which it used to do in former versions. Same with other non-Ascii characters. Is it a bug or did I overlook some recent change requiring different coding?
Thanks
Christoph

#start code example
import wx

class Dialog(wx.Dialog):
   def __init__(self, parent):
        wx.Dialog.__init__(self, parent, -1, 'Test TextCtrl',)
        tc = wx.TextCtrl(self, -1, size=(200, 100), style=wx.TE_MULTILINE )
        self.Centre(wx.BOTH)
        tc.AppendText('\xc3')
        tc.AppendText("Ç")

if __name__ == '__main__':
    app = wx.PySimpleApp()
    dlg = Dialog(None)
    dlg.ShowModal()
    dlg.Destroy()
    app.MainLoop()
# end code example

Christoph Herzog wrote:

Hi,
under Linux (Suse9.1, KDE), with Python 2.3.3, wxPython 2.5.2.8 (non-Unicode)

GTK1 or GTK2 version?

the following code does only insert the C with cedille when written as such in the source code. It does not insert it when written as WriteText('\xc3'), which it used to do in former versions. Same with other non-Ascii characters. Is it a bug or did I overlook some recent change requiring different coding?

It works for me with the GTK1 version. I don't have a non-unicode GTK2 version to try.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

Christoph Herzog wrote:

Hi,
under Linux (Suse9.1, KDE), with Python 2.3.3, wxPython 2.5.2.8 (non-Unicode)

GTK1 or GTK2 version?

GTK1. I tried both, the binary RPM, you supplied and the source RPM, no difference. Same with wxPython 2.5.2.7, so I suppose, its a Suse-specific problem :frowning:

···

the following code does only insert the C with cedille when written as such in the source code. It does not insert it when written as WriteText('\xc3'), which it used to do in former versions. Same with other non-Ascii characters. Is it a bug or did I overlook some recent change requiring different coding?

It works for me with the GTK1 version. I don't have a non-unicode GTK2 version to try.