Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Custom Cultures / Locales / CultureInfo   (RSS)

How Come My "ț" (or Another Character) Doesn't Work in Code Page XXX?

First of all, as I always suggest, Use Unicode when practical :) Then you don't run into these kinds of problems. The "thing" to remember about code pages in general is that they were an early way to get characters to display in a readable way on CRT

MSDN Code Gallery Custom Locales

MSDN has this new nifty Code Gallery place for samples and the like, so I stuck my custom locale examples there at http://code.msdn.microsoft.com/CustomLocales I added a few more since posting them to my blog here.

http://www.languagegeek.com/

http://www.languagegeek.com/ says it is dedicated to the promotion of Native North American languages. A coworker ran into this site while she was trying to learn more about the Lakota language (and she made a Lakota custom locale too! :) I don't know

Cantonese and Manderin language tagging.

The IETF "Language Tag Registry Update" working group has noted that lots of data is tagged as "zh-Hant", regardless of whether or not it is pronounced as Cantonese or Manderin. For video and audio however, this doesn't allow a fine enough distinction,

zh-Hans, zh-Hant and the "old" zh-CHS, zh-CHT

With Windows Vista and Microsoft .Net 2.0 (MS07-040 security patch) and 3.0+, we've started to use the IETF standard "zh-Hans", and "zh-Hant" names for Chinese simplified and traditional. In windows the zh-CHS/zh-CHT names were never used because the

How do you make your regional and language options apply to new user accounts?

In general its a good idea to allow users to choose appropriate settings, but being able to adjust the default user account settings to provide users with an appropriate default locale is often helpful. Also one cannot easily change the system account's

What's a genitive month name anyway?

I’m not a linguistic expert, so I’ll probably get this a bit wrong, but basically a genitive month name is used when there’s a number next to the month name. This doesn’t happen in English, but I think of it sort of like instead of saying “1 April 2008”,

"Windows Vista Command Line Configuration of International Settings" is on-line on MSDN

Generally its a good idea to let the users figure out their international settings, but sometimes they need to be managed in a command-line manner. Windows Vista Command Line Configuration of International Settings at http://www.microsoft.com/globaldev/vista/vista_tools/vista_command_line_international_configuration.mspx

Locale Builder Beta 2 is Available

The long awaited Microsoft Locale Builder Beta 2 is now available for immediate download at http://www.microsoft.com/downloads/details.aspx?FamilyID=e4588c5e-8f21-45cc-b862-38df8d9bd528&displaylang=en So now you too can (again) make a Klingon or Hawaiian

Security patch MS07-040 for .Net 2.0 breaks some culture names for .Net 2.0 on Windows XP/2003/2000

[12 July 2007] Updated with culture names on list of effected cultures The .Net patch of July 10th, ms07-049 http://www.microsoft.com/technet/security/Bulletin/ms07-040.mspx , changes culture names to use the new names on Windows XP/2003/2000 as well

Vista international configuration document on-line

As I've said before, its often good to honor the user's international settings, which they can set using the intl.cpl (Regional and Language Options) control panel. Sometimes it is interesting to be able to configure these settings programmatically. Some

Updated custom culture sample workaround for the .Net 2.0 Culture Name Change

I updated the sample for Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales . I added the aliased cultures to the parent chain of the old culture by creating a replacement of the new culture and changing the parent to the

How to tell if the collation version changed.

I added this to the msdn wiki for collation, but I'll blog about it here too. Occasionally we change the sorting behavior because new code points are added to Unicode, or we find out betterer data or made a mistake (never!) or whatever. Unfortunately

DateTime.Parse() and DateTime.TryParse() fail in some cases

DateTime.Parse and DateTime.TryParse fail in .Net 2.0 if the user locale date override has a space in it. Ie: if its something like "M d yyyy". .Net is getting tripped up over the space (we're working on a fix for SP1/Orcas). A workaround is to pass the

Configuring International Settings from the command line

Administrators like to set international settings from the command line. (Ie: Regional and Language Options, aka intl.cpl options). It is possible to do this in Windows Vista through an xml configuration file. A document is being created for MSDN, but
More Posts Next page »
 
Page view tracker