Tomer Gabel's annoying spot on the 'net RSS 2.0
# Thursday, December 14, 2006

I just reinstalled my laptop (a long and annoying story which I shall tell some other time), and this time opted for the Intel PROSet/Wireless drivers along with the PROSet/Wireless software suite (the one that replaces the crappy Windows wireless network management applet). It installed fine, the wireless card seemed to work fine but when I tried to start up the Intel application I was horrified.

It was in Hebrew.

Now, I realize that language preferences are a very personal issue, which is exactly why this pisses me off so much: why have ATi, nVidia and Intel all decided that my language of preference is Hebrew? The fact that my Windows is configured for Hebrew support in non-Unicode applications is no bloody excuse - it's that way because a lot legacy (and even new!) Hebrew applications require this setting to work properly. But my Windows is completely in English. Had I wanted localized UIs, I would've installed a localized version of Windows.

In Intel's defense, the translation was very comprehensive and even the RTL issues were sorted out; usually, however, software that supports localized menus have a language option where you can change the default language. The PROSet/Wireless software suite does not, and this time I was pissy enough to do something about it. Solution? Either download and import this registry hack, or do it manually:

  1. Start up your favourite registry editor;
  2. Go to HKLM\Software\Intel\Wireless;
  3. Change the value of InstalledLangId from whatever it is to 0x409 (or 1033 if you're decimal) -- that's the LangId for English;
  4. Change the value of InstalledLangShortString to "ENG";
  5. Kill the iFramewrk.exe process and restart it (or restart your machine if you're lazy)

All done. I really wish applications would stop deciding for me the language I want to work with.

Thursday, December 14, 2006 12:00:20 PM (Jerusalem Standard Time, UTC+02:00)  #    Comments [3] -
Software
Thursday, December 14, 2006 1:50:28 PM (Jerusalem Standard Time, UTC+02:00)
I guess this is simply a bug. Their software uses the wrong locale property to pick a UI language. There _is_ a right property to use and I don't agree that every program should come with a language-selection utility. When you have a Windows MUI package installed, you'd see an additional item in the Regional Options allowing you to select a UI language.
Ilya
Thursday, December 14, 2006 2:28:13 PM (Jerusalem Standard Time, UTC+02:00)
And if you're working on, say, a Japanese-localized computer - what then? Software that you've installed would be completely indecipherable to you.

At any rate, this "bug" as you call it is so popular in localized software that I think "malfeature" is a more appropriate term.
Saturday, December 30, 2006 12:33:13 AM (Jerusalem Standard Time, UTC+02:00)
Thank you for your post. Intel was stupid with reading those settings or at least having a courtesy of asking for preference. I had the same problem, only in Russian and mostly question marks. The directions worked great and computer restart was needed!

Great job.

Dave
OpenID
Please login with either your OpenID above, or your details below.
Name
E-mail
Home page

Comment (Some html is allowed: a@href@title, b, blockquote@cite, em, i, strike, strong, sub, super, u) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

Live Comment Preview
Me!
Send mail to the author(s) Be afraid.
Archive
<September 2010>
SunMonTueWedThuFriSat
2930311234
567891011
12131415161718
19202122232425
262728293012
3456789
All Content © 2010, Tomer Gabel
Based on the Business theme for dasBlog created by Christoph De Baene (delarou)