Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

The FUD of IDN and Homographs

I was pointed to this article http://www.microsofttranslator.com/BV.aspx?ref=Internal&a=http%3a%2f%2fwww.bortzmeyer.org%2fidn-et-phishing.html about IDN and homographs, which points out that most of the fear around IDN and phishing is unfounded. Seemed

SetLocaleInfo() is horrid, don't use it!

I just ran into a bug with SetLocaleInfo() use, and it pretty much reminded me that SetLocaleInfo() stinks. Michael said it years ago and it's still true. The only thing it's useful for is a "Regional and Language Options" type app, and there's already

IDNA2008 / IDNAbis on Windows 7, Vista, Net, etc.

Some people have asked what they should do to support IDNA2008 on Microsoft platforms. We provide IdnToAscii() and related functions in the Windows SDK. That's available natively on Vista+, and through idndl.dll on earlier platforms. Idndl is shipped

Visual Studio 2010 and .Net v4 Beta released

If you go to http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx there's now a Visual Studio 2010 and .Net v4 beta page. The betas are a good place to learn about new releases and provide feedback. -Shawn
Posted by shawnste | 0 Comments

Missing International Setting Registry Key?

Some Zune users ran into a strange problem http://forums.zune.net/2/3/518796/ShowPost.aspx and it seems like the Nation Value in HKEY_CURRENT_USER\Control Panel\International\Geo isn't there on some Windows XP machines. That seems really wierd to me because

A Cool Hard Drive Fix

Well, I should say all the caveats like "don't try this at home," and "it'll destroy your data," and "this is a stupid thing to do," and "don't try this with data you really need, use a professional data recovery service," but... At home I have a Windows
Posted by shawnste | 3 Comments
Filed under:

Japanese Calendars, How do I Test Support for Additional Eras?

The Japanese Calendar is labeled by the reign of the current emporer. Windows has supported 4 Japanese calendar Eras, however in the future there may be more eras. Realizing this, we've added support in Windows 7, Server 2008R2 & .Net v4 for additional
Posted by shawnste | 4 Comments
Filed under:

Oversimplification of EAI/IMA (International eMail Addresses)

A couple months ago I blogged about EAI Email Address Internationalization/Internationalized Email Addresses (EAI/IMA) and felt like blogging again. China's been very interested in non-ASCII email addresses for some time, and is working hard to adopt

What is Title Case?

Disclaimer: I'm not an English teacher (that's my mom), so I'm sure my description of title casing in English probably has exceptions/variations. Title casing has an interesting history in computer programming. Programmers like to use CamelCase to make

Alternate encoding names recognized by .Net / IE

If you run the sample from http://msdn.microsoft.com/en-us/library/system.text.encoding.getencodings.aspx then you can get a list of what Microsoft .Net thinks each Encoding/Code Page's name is. (WebName is more consistent to what's used in charset).

Unicode, IDN (IDNA), EAI (IMA) and Homograph Security

I wrote about IDN & Security before http://blogs.msdn.com/shawnste/archive/2005/03/03/384692.aspx but thought I'd share some of my more updated views about security of URLs/IDN/Unicode/Email addresses. People haven't really bothered much with DNS

 

A helpful reader pointed out I don't really know Klingon. PS. I just checked out your blog (very nice by the way, lots of stuff I need to read) and I noticed along the top of the page you have  (jItlhInganbe') for "I'm not a Klingon". The translation
Posted by shawnste | 5 Comments
Filed under:

Email Address Internationalization / Internationalized eMail Addresses (EAI/IMA)

With the IDN work for Internationalized Domain Names using characters beyond ASCII, it is only natural to tackle the problem of Internationalized Internet eMail. Some smart people have been working on an IETF working group to figure out how non-ASCII

Writing "fields" of data to an encoded file.

The moral here is "Use Unicode," so you can skip the details below if you want :) A common problem when storing string data in various fields is how to encode it. Obviously you can store the Unicode as Unicode, which is a good choice for an XML file or

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).
More Posts Next page »
 
Page view tracker