+***---***---***---***---***---***---***---***---***---***---***---
+ UNICODE!
+
+ wxWindows and wxPython can be compiled with unicode support
+ enabled or disabled. Previous to wxPython 2.3.3 non-unicode mode
+ was always used. Starting with 2.3.3 either mode is supported,
+ but only if it is also available in wxWindow on the platform.
+ Currently wxWindows only supports unicode on MS Windows platforms,
+ but with the recent release of GTK+ 2.0 it is only a matter of
+ time until it can be done on wxGTK (Linux and other unixes) as
+ well.
+
+ When unicode is enabled, then all functions and methods in
+ wxPython that return a wxString from the C++ function will return
+ a Python unicode object, and parameters to C++ functions/methods
+ that expect a wxString can accept either a Python string or
+ unicode object. If a string object is passed then it will be
+ decoded into unicode using the converter pointed to by
+ wxConvCurrent, which will use the default system encoding. If you
+ need to use a string in some other encoding then you should
+ convert it to unicode using the Python codecs first and then pass
+ the unicode to the wxPython method.
+***---***---***---***---***---***---***---***---***---***---***---