Shawn Steele's thoughts about Windows and .Net Framework globalization APIs
I split my work between Windows and the .Net framework (Silverlight & Visual Studio). For .Net I work on the .Net System.Text and some of the System.Globalization classes. For Windows I'm responsible for many of the NLS APIs.
My primary work is involved with encodings/code pages, sorting, normalization, and IDN. I also mess with locales and cultures.
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included samples are subject to the terms specified at http://www.microsoft.com/ info/cpyright.htm
I hope to put some links to interesting posts about Code Pages/Unicode/Encodings here.
Hope this is helpful. I'll post more links here when I add them
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using RSS
People wonder if we're going to update our best fit code page mappings, or even our code page mappings.
In my post Change to Unicode Encoding for Unicode 5.0 conformance I mentioned that the behavior of illegal
First of all, remember to Use Unicode when practical :) Sometimes older applications don't allow Unicode,
As I've said before, I encourage "Using Unicode" for data. So I've gone to the Unicode conference ( http://www.unicode.org
