by Michael S. Kaplan, published on 2008/04/15 00:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/04/15/8396470.aspx
Content of Michael Kaplan's personal blog not approved by Microsoft (see disclaimer)!
Note that this post is entirely offtopic and if that kind of thing bothers you then you re invited to get out right now....
It was back in December of 2006 that I first posted For the [locale] explorer in you...., a blog about the sample that Francois Liger had updated on GotDotNet, Culture Explorer 2.0.
As it turns out, the timing of the update was very unfortunate.
Because GotDotNet is no more -- it has been shut down, and as that page mentions:
Secondly, if you are one of those generous people who had recently uploaded a sample – or multiple samples – to the GotDotNet site, your contribution may be amongst the samples on the MSDN Code Gallery site. We have migrated popular samples (dating back to the beginning of 2007) to the MSDN Code Gallery site.
So if people like me and others who had been nagging Francois to update the sample had been a bit lazier or less annoying, they might have migrated the sample themselves? :-)
Of course there are flaws in this theory, since
Anyway, recently someone named Michael commented on this fact:
Is Culture Explorer 2.0 still available anywhere? GotDotNet is gone now, and I can't find the app in the MSDN Code Gallery, CodePlex or anywhere else. Nothing new comes up in searches for the app, or for the author either. Sorry to ask here, but I can't find anything anywhere else, so I thought I'd at least ask.
thanks,
michael
Michael is telling no lies here, and I verified with Francois that he hadn't migrated it under some other name or anything weird like that.
But he will have the chance to look into it now, at least.
I do know that the red tape you have to go through to put stuff on these other sites is a bit more effort than GotDotNet was, which makes all of this a bit more of a worry. But I'll get my nag on and see if I can help expedite things. It is a nice sample, after all. :-)
This post brought to you by ᠱ (U+1831, a.k.a. MONGOLIAN LETTER SHA)
Stuart Dunkeld on 15 Apr 2008 6:07 AM:
You can download it from
-- Stuart
Andrew West on 15 Apr 2008 12:16 PM:
Completely off-topic, but I notice that you embed the sponsoring character (U+1831, MONGOLIAN LETTER SHA) in an html font tag specifying "Mongolian Baiti" as the font face. It drives me crazy that IE7 (like IE6 before it) lists Mongolian as a "language script" that you can configure the font for, but it will not populate the font lists with any fonts regardless of how many fonts you have on the system that support Mongolian (including Mongolian Baiti), so it is impossible to actually configure what Mongolian font to use! The good news is that it does display Mongolian using Mongolian Baiti without explicitly specifying the font in the html, but the bad news is that I can't get it to use a Mongolian font other Mongolian Baiti without messing with the html. I just wish someone would fix IE ... or is this one of those Kafkaesque examples like Uyghur where Microsoft can't fix something, however broken, in case it breaks user expectations?
Michael S. Kaplan on 15 Apr 2008 12:43 PM:
There are reasons (not good reason, but reasons!) why this behavior exists, and they may find their way into a blog at some point (if I remember or if it is in the suggestion box)....
referenced by