Re: [wxhaskell-devel] wxString handling broken when using wx 2.9

[Eric Y. K. <eri...@gm...>]

On Wed, Sep 21, 2011 at 17:44:58 +0200, David Virebayre wrote:
> I have no good answer to those questions. But, if I didn't read too
> fast, I think wxwidgets uses UTF-16, which is also what is used in
> Text.

There is a GSoC project to switch Text to to UTF-8 for what it's worth

> I've made a little program and used Text to process Textual data which
> I want to display in a GUI, so converting to String puts lots of
> unwanted T.unpack here and there.

OK so that's potentially an argument about convenience

> Since wxHaskell or wxWidgets probably has to convert that back to
> UTF-16 at some point...
> 
> I'm probably thinking way ahead of time with this idea.

Being a sort of naive computers-dont-really-exist-only-code-does
sort, I'd tend to say this is an implementation detail we shouldn't
think too too hard about.  Just make it work first.

-- 
Eric Kow <http://erickow.com>