Is WxWidgets for me?

[Graeme Gill]

Vadim Zeitlin wrote:
>  If you use UTF-8 internally you may find it easier to work with the new
> API in the trunk where, first, wxString uses UTF-8 representation
> internally too (which avoids the unnecessary conversions if you already
> work with UTF-8) and, second, the API is "char *" friendly. The only
> problem is that svn trunk is, of course, work in progress -- but if you
> don't plan to release your application immediately it might still be a
> better choice.

I notice at the bottom of this page
<http://wiki.wxwidgets.org/Development:_UTF-8_Support>,
there is an open question about a UTF-8 build under MSWindows.

I would presume this is because the win32 API are setup to
handle Unicode as 16 bit wide chars, so supporting UTF-8 implies
converting all the string arguments to/from the API calls within
WxWidgets.

 From the perspective of someone using WxWidgets cross platform,
and interfacing to a non-WxWidgets back end, then being
able to use UTF-8 uniformly within WxWidgets on all
platforms would be far cleaner than having to add special
code for the MSWindows version (ie. it would make it more platform
transparent to be able to assume UTF-8 everywhere).

regards,

Graeme Gill.