The evolving Story of Locale Support, part 13: Divvying up locales, yet again!

by Michael S. Kaplan, published on 2011/12/21 07:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2011/12/21/10249983.aspx


Previous blogs from this series:

Now in the past, I've written The Locales of Windows 7, all divvied up, which included:

I've also written the sequel, The Locales of Windows 7, divvied up further, which included the slihttky more niche:

And in The evolving Story of Locale Support, part 5 (...until the decision was made to not refuse to add it), which listed a bunch of locales added to Windows 8 that at some point might make nice entries to an updated version of Table 3.

I didn't comment about how many of them might be added to a nice updated version of Table 2, because that list is still confidential info. Though if history is a guide then some of the new languqages and some of te exiting ones might fit there.

Also, in The evolving Story of Locale Support, part 2 (raising the roof on keyboards), I Listed a bunch of new keyboards added to Windows 8, some of which have no LCIDs, as I pointed out in that very blog (I described some of my implementation concerns on this matter in The evolving Story of Locale Support, part 11: What language is that keyboard for?).

But there is yet another list -- a missing list.

You see, Table 3 should have, rather than being called

Table 3: locales whose identifiers are not directly associated with any localizations of Windows, even if a related identifier might make for one representing a suitable localization

should have instead been more accurately called

Table 3: locales supported by Windows 7 whose identifiers are not directly associated with any localizations of Windows, even if a related identifier might make for one representing a suitable localization

Because just yesterday the question was asked:

I am wondering if en-HK is a supported culture in Windows 7? From this document, it says it’s supported in Windows XP &
Server 2003, but yet I get a CultureNotFoundException trying to instantiate the culture with “en-HK” or it’s LCID 15369.

Any suggestions? If not, please forward to a more appropriate alias, thanks.

One of the people (Alexander) got that mail forwarded it to me, and he (Alexander) is on the small list of people I have Outlook set to let the mail get to me even though I'm on vacation (as I mentioned in I plan to go somewhere that starts with a "T").

And it is an interesting question, so I thought I'd take it up now!

The problems with that Locale IDs Assigned by Microsoft web page are numerous, and I'll get into that some other day.

But for now I'll give a first crack at yet another table:

Table 7: Locales whose LCD values are reserved but which are not really supported in Windows 8 or earlier

Language Name

Reserved LCID

Burmese

0455

Edo

0466

English - Hong Kong SAR

3c09

English - Malaysia

4409

English - Singapore

4809

French - Cameroon

2c0c

French - Democratic Rep. of Congo

240c

French - Cote d'Ivoire

300c

French - Haiti

3c0c

French - Mali

340c

French - Morocco

380c

French - North Africa

e40c

French - Reunion

200c

French - Senegal

280c

French - West Indies

1c0c

Fulfulde - Nigeria

0467

Guarani - Paraguay

0474

Ibibio - Nigeria

0469

Kanuri - Nigeria

0471

Kashmiri

0860

Kashmiri (Arabic)

0460

Latin

0476

Manipuri

0458

Nepali - India

0861

Oromo

0472

Papiamentu

0479

Rhaeto-Romanic

0417

Romanian - Moldava

0818

Russian - Moldava

0819

Sepedi

046c

Sindhi - India

0459

Sindhi - Pakistan

0859

Sinhalese - Sri Lanka

045b

Slovak

041b

Slovenian

0424

Somali

0477

Sutu

0430

Tamazight (Arabic)

045f

Tibetan - Bhutan

0851

Tsonga

0431

Urdu - India

0820

Venda

0433

Yiddish

043d

HID (Human Interface Device)

04ff

 Note that en-HK is one of the many locales on this list.

Some also recognize Urdu - India,which I discussed in Where's the other Urdu?, a blog where I also talked about the Locale IDs Assigned by Microsoft page and some of its problems.

I'd love to comment about some of the reasons why a locale would end up here on this page, reserved, but in many cases the reasons would be mere suppositions on my part.

I mean I know about my fruitless campaign for an Urdu - India that was champoioned by and ulimately tied to a Microsoft VP who left under unhappy at the lack of direction of many efforts he championed in the unused potential of Microsoft India -- technologies that ultimately were marginalized and now have no owners (an issue I also was unable to influence in the endd since no one had the resources to take the work on). But that's heroic tale of throwing an elbow that didn't connect, a little too much inside baseball, and something that ultimatelty blew my stack on sports metaphors that only some o my readers will get.

Alternately, I know about the campaign of harassment by a professor that led to the Yiddish locale being added to this list, and I could revel my readers with tales like that. But although it came to me from a reputable source, it is still hearsay -- and I'd like to keep blogs admissible. :-)

Kind of hints at future Table 8: Locale lists that are broken in one or more ways. :-)

But for now, that Table 7 list should do. And I got a question of a customer (albeit an internal customer) answered, which id good since i still do serve at the pleasure of the customer....


Timwi on 21 Dec 2011 2:14 PM:

“Moldava”? What the heck is Moldava? :) The country is called Moldova...

Michael S. Kaplan on 21 Dec 2011 4:30 PM:

See that link that I accused of being broken in many senses -- it is their spelling....

cheong00 on 21 Dec 2011 5:50 PM:

IMO, it seems the only difference between zh-HK and en-HK would be DateTime format difference (I currently cannot think of the others. Even in zh-HK, people has been set the currency format to HK$#,##0.00 ). Is there a point for implementing a seperate English based locale for Hong Kong?

There may be, just weak. So I guess this is why it haven't been implemented as of Windows 8.

Michael S. Kaplan on 21 Dec 2011 6:25 PM:

I suspect the lack of a proven need for the locale is the main reason it was not added, actually.


referenced by

2012/10/26 The evolving Story of Locale Support, part 28: We finally fixed that 'Install New Languages' thing!

2012/10/02 The evolving Story of Locale Support, part 27: No, the T and the H aren't silent...

2012/08/21 The Locales of Windows 8, not yet divvied up...

2012/08/20 The evolving Story of Locale Support, part 26: Hey Windows 8, there's someone on the phone for you.

2012/07/11 The evolving Story of Locale Support, part 25: Something old, something new, something repurposed, and something...

2012/06/07 The evolving Story of Locale Support, part 24: I Adar you! Hell, I Double Adar you! (Windows 8 ed.)

2012/06/05 The evolving Story of Locale Support, part 23: Tamazight? Outta sight!

2012/04/12 The evolving Story of Locale Support, part 22: Digit Substitution 2.0

2012/03/08 The evolving Story of Locale Support, part 21: The Windows 8 Hijripalooza extraordinaire!

2012/03/02 The evolving Story of Locale Support, part 20: Yes, it's Bangla. Not Bengali!

2012/02/21 The evolving Story of Locale Support, part 19: In honor of International Mother Language Day...

2012/02/15 The evolving Story of Locale Support, part 18: Two scripts that share ten digits can be trouble

2012/02/02 The evolving Story of Locale Support, part 17: Today I feel like translating you more than before

2012/01/24 The evolving Story of Locale Support, part 16: We can't scale to a Xishuangbanna Dai locale, but…

2012/01/17 The evolving Story of Locale Support, part 15: Fixing our listings up in Windows 8!

2011/12/22 The evolving Story of Locale Support, part 14: Tifinagh, Tamazight, and Berber? Oh my!

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