On Tue, May 08, 2012 at 01:01:07AM -0500, Dick Hollenbeck wrote: > With latest wx, wxString is a container holding a std::string holding > characters encoded > as UTF8 bytes on linux and OSX. Windows is unknown.
UTF8? not wide chars? Strange, the C++ approach is usually using wchar_t, not MBCS... there *is* a configure option for using UTF8 in 2.9, maybe that's active in your build. This would actually break every indexed access to the string (unless they abstracted it with huge performance penalties, having to start from the beginning each time). I see 6GB ram *laptops* around. I think these days string processing (i.e. not only copying strings from a place to another) in core is more convenient with wchars... -- Lorenzo Marcantonio Logos Srl _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
