Welcome to MSDN Blogs Sign in | Join | Help

May 2009 - Posts

Locale Builder and Two Letter ISO name and Three Letter Windows Language Name

When you use the Microsoft Locale Builder tool to build a custom locale, it asks for a lot of fields. Two may not be obvious: The Two Letter ISO Language name is permitted to be 3 letters for locales that don't have a 2 letter code (eg: haw for Hawaiian).

Cheating to UNinstall Custom Cultures / Locales

In Cheating To Install Custom Cultures , I mentioned how to add the custom cultures without using CultureAndRegionInfoBuilder.Register(). Should you have any problems with a custom culture / locale and want to uninstall it but are having difficulty with

A Pet Peeve of Mine

One of my pet peeves is software that is too restrictive about installing. The #1 compatibility thing I find is applications that refuse to install on a newer OS for no good reason. Generally if you can get them to install OK then they run OK. I feel
Posted by shawnste | 1 Comments

Don't use MB_COMPOSITE, MB_PRECOMPOSED or WC_COMPOSITECHECK

This pretty much demonstrates another reason to Use Unicode, but if you do need to use some non-Unicode encoding until you can convert to Unicode, please don't use these flags. MultiByteToWideChar() and WideCharToMultiByte() provide some interesting sounding
 
Page view tracker