GEOID -- The LCIDs maligned little brother....

re: GEOID -- The LCIDs maligned little brother....

Jonathan Wilson — Fri, 04 Feb 2005 13:58:00 GMT

I imagine that managing this database must be a headache.
Especially when you consider that if you get geographic or geopolitical information wrong, it can cause big problems. (for example, is there any way to list what country the region of kashmir is in without pissing someone off?)

re: GEOID -- The LCIDs maligned little brother....

Michael Kaplan — Fri, 04 Feb 2005 15:59:00 GMT

Well, any time some issue is updated, it obviously must be updated....

You may also have successfully hit on one os the reasons why MapPoint does not cover all locations in the world? :-)

re: GEOID -- The LCIDs maligned little brother....

Ivan Petrov — Fri, 04 Feb 2005 21:44:00 GMT

(Ivan, I have moved your comment to http://blogs.msdn.com/michkap/articles/363007.aspx#367392 without prejudice since it was horribly offtopic for here)

re: GEOID -- The LCIDs maligned little brother....

Ruben — Fri, 04 Feb 2005 22:01:00 GMT

Would you care to explain a little further what the heck the use is for RegionInfo.GeoId without any of the SYSGEOTYPE information? Who needs a GeoId when the only way to do something with it, is by P/Invoking to Win32?

But then again, what is the use for a TimeZone class, when the only time zone supported is the current time zone?

re: GEOID -- The LCIDs maligned little brother....

Michael Kaplan — Fri, 04 Feb 2005 22:12:00 GMT

Ruben -- one is for custom cultures (which eventually become custom locales), and the other is the along the lines of "maybe next version"....

Both of which will be interesting topics for another day!)

re: GEOID -- The LCIDs maligned little brother....

Ruben (176) — Fri, 04 Feb 2005 22:56:00 GMT

Well, I don't quite see the custom cultures argument, unless it's some internal necessity in Windows to always assign a GeoId to a locale. But then again, if it's just an integer without context, why not give it the value 0. Just as meaningful as 221, which btw seems to be the GeoId for Sweden, according to the .NET SDK sample on GeoId. Who knew.

Anyway, great blog! I just love topics where no-one will ever be right and it's all one jolly mess of compromises.

Time zones and locations and keyboards, oh my!

Sorting It All Out — Sat, 28 May 2005 07:07:10 GMT

Yesterday, Manip post a rant about the fact that the three settings in the title of my post today are...

Client side locale settings on the server?

Sorting It All Out — Mon, 27 Jun 2005 02:33:34 GMT

Recently overheard in the microsoft.public.dotnet.internationalization newsgroup:

Hi,
I'm developing...

Location in the Regional and Languages options control panel

Sriram Krishnan — Tue, 11 Apr 2006 23:21:31 GMT

One of the free perks of working for Microsoft - when you want to know why a feature in a Microsoft product...

What the hell is up with Timor-Leste?

Sorting It All Out — Sat, 19 Aug 2006 10:27:32 GMT

Regular reader Mark Brooks asked in the Suggestion Box:

What's up with Timor-Leste? How did it...

On holiday? Outlook might try to tell you where....

Sorting It All Out — Tue, 26 Dec 2006 11:37:48 GMT

In Open it all up, get out of the way, and then what happens? , I talked about the challenges that my

If you play with your gadget, there are all kinds of problems you can run into

Sorting It All Out — Thu, 13 Dec 2007 18:20:51 GMT

I am not talking about going blind or hair on your palms, either. I'm talking about internationalization