{Insert a pun about the word Serbian here, I can't think of one}

by Michael S. Kaplan, published on 2010/08/09 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2010/08/09/10047417.aspx

The other day in I put up a table covering all of the Serbian, Bosnian, and Croatian locales on Windows:

Now this list is complete according to many of the sites on MSDN, including

• Locale IDs Assigned by Microsoft on GoGlobal (which includes things that aren't even in Windows yet but are simply reserved because someone wanted them for their own purposes), and
• Language Identifier Constants and Strings (which is a part of the Windows NLS documentation).

I did note the whole Serbia/Montenegro issue and pointed to some other blogs, but seeing no info or update on plans here my assumption was that there was none....

So anyway, I figured it ought to be pretty solid. In theory.

But then if you look at Regional and Language Options in Windows 7:

There are clearly at least four missing from this 'full" list:

• Serbian (Latin, Serbia)
• Serbian (Cyrillic, Serbia)
• Serbian (Latin, Montenegro)
• Serbian (Cyrillic, Montenegro)

Probably a good idea since the word FORMER is on the ones for Serbia and Montenegro....

By the way I hate the new name structure since I don't think the alphabetical order that comes out of the names is necessarily more intuitive!

But anyway, what are the constants for these four new locales?

Oops.

Lucky for us that someone wrote a document about Microsoft .NET Framework 4: What is New in Globalization, which tells the rest of the story.

I'll get into that document more another day, for now I'll just stay in this one part of the world!

So here are the additional table items:

 And as I noted in the Bosnian blog:

Note that there is still no unique ISO code for Montenegrin (Montenegro), so that the situation Kieran described back in What's in a name? Part two back in 2006 is still not clarified.

The issues I mentioned in Ask 'em if their language is Montenegrin; their answer may surprise you are not all that further along either.

So there is the problem that there was time to write a new .Net white paper but not time to update core lists that contain the information that both native and managed developers might want.

The only other place that has the updated locales is the protocol site (here) though since it lists some different values, somebody may want to update that since that means the Protocol docs are wrong!

Their take on Serbian:

Like I said, someone may want to fix the discrepancies here!

Anyway, I guess I should thanks for Microsoft .NET Framework 4: What is New in Globalization, or else nobody would ever be able to get information on the latest story here.

Though I'd rather the other docs weren't inaccurate, if I had my choice here....

Oh wait. I do. Since my group has some responsibilities around GoGlobal, I can do a little insisting on better information for documentation they provide like Locale IDs Assigned by Microsoft. I can also suggest they clean up their own docs like Language Identifier Constants and Strings, but that is really more up to them, I guess. :-)

Now there are a few remaining issues to talk about, though that will have to wait for another day. Stay tuned....

Carl on 10 Aug 2010 3:14 AM:

Maurits [MSFT] on 24 Aug 2010 1:36 PM:

referenced by

go to newer or older post, or back to index or month or day