The Whey doesn't get a locale, either

by Michael S. Kaplan, published on 2009/05/26 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2009/05/26/9641049.aspx


As a by the way, this blog does NOT represent anything beyond my own personal thoughts based on the way I think things are going. You could even blame it on my Tegretol dosage, to be perfectly honest (if the pain were not so intense I'd have skipped this med for sure). I am not even on the team that decides these things any more and I wasn't in charge of the strategy when I was then. Anyone who quotes me with prefacing words like "According to Microsoft..." is a complete and utter moron.

It starts with a nursery rhyme, as it turns out a very popular one from what I am told:

Little Miss Muffet
Sat on a tuffet,
Eating her curds and whey;
Along came a spider,
Who sat down beside her
And frightened Miss Muffet away.

You might wonder where I am going from here.

Well, first there is the mail I got (product and personal info removed because it just seemed prudent):

Dear Michael ..

We have been contacted by a group of Kurdish people who would like to translate our product to Kurdish. However the problem we are facing is that we cannot find (checked winnt.h) the language ids (e.g. LANG_KURDISH) associated with the Kurdish language and sub language/culture.

I have been reading the following paper It is Time to Add Kurdish Culture to VS .NET Globalization
Since you have been referenced and I think to remember that you are involved with globalization at Microsoft I thought you are the right person to contact :-)

Have the language ids for Kurdish already been defined? If not would it be possible to do so?

As always thank you for your time and efforts.
Best Regards,

Ah, so the title and the nursery rhyme is a bad pun (curds vs. Kurds) skirting a geopolitically sensitive issue!

The answer is that there is no LANG_KURDISH defined. Although the paper starts off on very solid ground it ignores the geopolitical issues completely, to wit:

Plus I have no idea who the authors talked to; although they quoted my book several times they never contacted me (by the address provided in the book or any other way) and I don't believe they contacted anyone with knowledge/understanding of the issue, or they would have gotten a much more accurate (though for them not so happy) of an answer.

Remember that nothing gets added to .NET; it is first added to Windows and then later to .NET.

So assuming that there were going to see (for example, off the top of my head) some or all of the following new locales added:

without (in many cases) the support and assistance of the governments who decide to let Microsoft ship software in their countries, and with the unhappiness of severaql of those countries as a part of the process, it is easy to imagine software banned in some of those places.

Microsoft can't set policy here, or be used as proof of a policy.

Thus we have our answer: the locale id values have not been defined, and they cannot be given the present environment.

In the end, whether we are talking about Kurdish, or Kashmiri, or any of a number of such languages, Sometimes, tech companies cannot take sides. If you do things with custom locales and custom keyboards, then the operating system will support the efforts, but these things can't so easily be put in the box, built in. And thus they can't be so easily put into the .Net Framework,

On the other hand, this is yet another reasons that LCIDs suck, and any software -- Microsoft or any other company -- that depends on LCIDs needs to get off of them. For everyone's sake. Note that it is the software's dependence on LCIDs that led to the question being asked in the first place!

 

This post brought to you by ڵ (U+06b5, a.k.a. ARABIC LETTER LAM WITH SMALL V)


John Cowan on 26 May 2009 4:46 PM:

FWIW, CLDR (the Unicode Common Locale Data Repository) currently supports the following locales: generic ku-IR, ku-IQ, ku-SY, and ku-TR, plus script-specific ku-Arab-IR, ku-Arab-IQ, ku-Arab-SY, and ku-Latn-TR.  Of course, if people added more data they could get more locales.

Sigh.

Michael S. Kaplan on 27 May 2009 1:26 AM:

Hey John,

Of course this kind of underscores the problem with simply adding CLDR support, doesn't it? :-)

Random832 on 5 Jun 2009 5:05 PM:

What about just adding a locale for some generic country (US? Invariant Country?) so they can at least get the language?

Michael S. Kaplan on 8 Jun 2009 5:21 PM:

That would not be a good idea for the sake of people who do live in a region (it is also impossible for invariant and inflammatory  for US).

Andy on 22 Jun 2009 3:25 PM:

Not very nice to make fun of a suppressed and persecuted people. Bad pun? Adding insult to injury, more like.

Michael S. Kaplan on 23 Jun 2009 3:31 AM:

Not making fun of anybody, just pointing out emotional flaws in an attempt at a technical justification for an issue that serious repercussions.

The pun is perhaps bad, but most are (as are most of my blog titles!).


referenced by

2011/11/08 The evolving Story of Locale Support, part 5 (...until the decision was made to not refuse to add it)

2010/10/01 Kurdish with an Arabic Accent?

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