- wxWidgets 3.0 wxString internally uses UCS-2 (basically 2-byte per
- character wchar_t) under Windows and UTF-8 under Unix, Linux and
- OS X to store its content. Much work has been done to make existing
- code using ANSI string literals work as before. If you need to have a
- wxString that uses wchar_t on Unix and Linux, too, you can specify
- this on the command line with the @c configure @c --disable-utf8 switch.
- As a consequence of this change, iterating over a wxString by index
- can become inefficient in UTF8 mode and iterators should be used instead:
+ Since wxWidgets 3.0 wxString internally uses UCS-2 (basically 2-byte per
+ character wchar_t and nearly the same as UTF-16) under Windows and
+ UTF-8 under Unix, Linux and OS X to store its content.
+ Much work has been done to make existing code using ANSI string literals
+ work as before. If you need to have a wxString that uses wchar_t on Unix
+ and Linux, too, you can specify this on the command line with the
+ @c configure @c --disable-utf8 switch.
+
+ Since iterating over a wxString by index can become inefficient in UTF-8
+ mode and iterators should be used instead of index based access: