On Wed, 19 Jan 2011 12:16:59 +0000 Alexander Lamaison <awl03@doc.ic.ac.uk> wrote:
On Wed, 19 Jan 2011 11:33:02 +0100, Matus Chochlik wrote: [..]
All the wstrings, wxString, Qstrings, utf8strings, etc. will be abandoned. All the APIs using ANSI or UCS-2 will be slowly phased out with the help of convenience classes like ansi_str_t and ucs2_t that will be made obsolete and finally dropped (after the transition).
This is simply not going to happen. How could MS even go about doing this in Windows? It would make very single piece of Windows software incompatible with the next version!
That has never stopped them before -- see Windows 2.0 -> 3.0, Windows 3.x -> Windows 95 (only partial compatibility), various versions of WinCE/Windows Mobile/whatever-marketingspeak-name-they're-using-this-year... ;-) But you're right, they'll probably stick with UTF-16, despite its problems. -- Chad Nelson Oak Circle Software, Inc. * * *