[wx-dev] UTF-8 for internal string processing

[Vadim Zeitlin]

On Tue, 01 Apr 2008 19:50:49 +0100 Julian Smart <julian at anthemion.co.uk> wrote:

JS> This does really concern me too.

 Sorry, what does? I'd really appreciate any concrete examples. In wx
itself we did change some code to use iterators (e.g. wxTextBuffer) but it
was needed in surprisingly few places.

JS> I hope that it will be possible to compile wxWidgets and one's app in a 
JS> compatibility mode that uses the same representation as before.

 Yes (especially if somebody cares to maintain it, even if it only means
installing a buildbot slave running a build with --disable-utf8).

JS> However this rather negates the goal of one-build-fits-all

 Yes.

JS> and would mean internal wxWidgets code (and any libraries) would still
JS> have to be written using wxT().

 No, absolutely not, this is just wrong. You don't have to use wxT()
whether or not wxString uses UTF-8 internally or not, it will just result
in a run-time (instead of compile-time) conversion but as you don't embed
megabyte-long strings in the code this is really never a problem.

 Regards,
VZ