Friday, July 11, 2008 12:01 AM
Michael S. Kaplan
What kind of English were you looking for? We only seem to have one in stock....
A question came up the other day that some regular readers might find vaguely familiar:
We have been using the CultureInfo.CurrentUICulture to get the default UI language of the client OS. It works for locales like en-US (which is the default) and for other language locales like de-DE, es-ES, fr-FR, it-IT, ja-JP, ko-KR, pb-BR, ru-RU, zh-CN etc., but NOT getting the locales which are other flavours of English like en-AU etc., instead returning en-US in those cases.
The language locales are picked based on client operating system for the language or if not from the regional settings languages etc.,.
For example, if we set the locale en-AU everywhere in regional settings and in also in MS Office, its still picking up only en-US.
We are trying to get the locale from our Add-in in MS Office using the .NET 1.1.
Please throw some light on how we can get the locales which are other flavours of English.
Ah,. the hazard of being UICulture-based running on Microsoft products!
So maybe you remember one of the following blogs from the past:
and more.
The problem is the same -- despite the commonly known and understood fact that these various dialects are not all 100% mutually intelligible, companies like Microsoft, in an effort to save money, tries to enforce a single language version of many different products.
The exceptions to this are few and far between, e.g.:
- Chinese
- Portuguese
- Norwegian (where we actually skipped a Nynorsk LIP, as I described here)
And despite all the lip service (pun intended) that people pay to the need to support "local experiences", despite complaints from former MSFTies like Mike Williams or not-yet-quite-former MSFTies like me, despite the work of cartoons like Darby Conley's Get Fuzzy with the multitude of cats who visit from non-US English speaking places like Manchester that many can't understand and even more random references, no one thinks the problem is bad enough to bother with.
No one wants to "get" the problem here though.
When I think about the nightmares associated with time zones and all the brave efforts to fix longstanding problems that only were able to get traction when they directly impacted people at the executive level in Redmond, I wish some similar solution were possible here -- like localize all of Microsoft's products into UK English or even better Australian English and have these versions on the computers of every executive, technical fellow, and Distinguished Engineer at Microsoft.
How many days would they have to use products while they struggle to understand the words before it would become a mandate to care about local experiences in all of the other places that English, Spanish, French, German, Italian, Chinese, etc. are spoken besides the few places we localize to....
But to be honest I don't see how it could be accomplished. And since no one gets made an executive by finding ways to have stuff cost more money, the problem perpetuates itself.
This blog brought to you by z (U+007a, aka LATIN SMALL LETTER Z)