Welcome to MSDN Blogs Sign in | Join | Help

June 2007 - Posts

I see my favorite Ansi function has the behavior I want.

Occasionally I am asked about the A version of a W function. Ie: GetLocaleInfoA does something that appears more convenient to some user than GetLocaleInfoW. The implied thought is that maybe they should just use the A version. For the most part our A

Almost dismasted

As you may have guessed from the photo, I like to sail. I have an F-25 trimaran "Gazelle" that was built by the previous owner from wood. I've sailed from Puget sound to Desolation sound in her, and near Vancouver we outran a commercial fishing vessel
Posted by shawnste | 1 Comments
Filed under:

Why can't we strip the diacritics?

We have some "best-fit" behavior which we generally consider to be "bad". Any loss of data is generally a bad thing, so we recommend storing data in Unicode (so you don't lose anything). Assuming you can't use Unicode, why is it so bad to just make everything

Encoder/Decoder Encoding fallbacks fail after 2GB of data has been converted

We have an unfortunate bug in .Net v2.0+ that causes encoding or decoding of more than 2GB of data to fail. That's a lot of data, but it still shouldn't do that. This is a problem with our built in fallbacks. Ironically, if you encounter bad bytes then

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
 
Page view tracker