.NET v.2.0 makes using custom cultures way easier
Last year, I did a tutorial on developing custom cultures for your applications,
"Globalizing ASP.NET Applications with Non-Standard Languages", showing how one could somewhat easily develop a custom type to use for languages either not supported in v.1.0 of the .NET Framework, or basically, not in existence at all.
Shawn Steele from Microsoft just gave me the 411 on some new features in Whidbey to make this process even easier, namely through using the
System.Globalization.CultureAndRegionInfoBuilder class. (He also mentioned that in contrast to the method used by my earlier article, MS doesn't recommend deriving custom types from System.Globalization.CultureInfo anymore).
Shawn's got some cool stuff on it at
http://blogs.msdn.com/shawnste/category/9761.aspx and http://blogs.msdn.com/shawnste/archive/2005/03/08/389944.aspx. Junfeg Zhang's also got something on it at http://blogs.msdn.com/junfeng/archive/2004/08/01/203813.aspx.
Thanks fellas!