Is it really a good idea to use a different encoding than the CLR? Lots of people do stuff with unsafe code etc which would need to be changed.
Also to add a bit of context (history) http://blog.coverity.com/2014/04/09/why-utf-16/#.V5oZpJO7iko is worth a read On Thu, Jul 28, 2016 at 3:47 PM, Edward Ned Harvey (mono) <[email protected]> wrote: >> From: [email protected] [mailto:mono-devel-list- >> [email protected]] On Behalf Of Jon Purdy >> >> > For historical reasons, System.String uses the UCS-2 character encoding, >> that is, UTF-16 without surrogate pairs. >> >> > However, most strings in typical .NET applications consist solely of ASCII >> characters, leading to wasted space: half of the bytes in a string are >> likely to >> be null bytes! > > What's wrong with UTF-8? > _______________________________________________ > Mono-devel-list mailing list > [email protected] > http://lists.dot.net/mailman/listinfo/mono-devel-list -- Studying for the Turing test _______________________________________________ Mono-devel-list mailing list [email protected] http://lists.dot.net/mailman/listinfo/mono-devel-list
