Microsoft Plans to Create Local Language Software
zensufi writes "CNET News has a story stating that Microsoft has announced plans for a program to help governments produce local language versions of key Microsoft applications, giving the software giant a hedge against a growing international threat from open-source software." The piece explains: 'The Local Language Program will provide local and regional governments with "language interface packs" that government and academic developers can use to produce localized versions of the Windows XP operating system and Office 2003 productivity package.'
Unfortunately MS fails to realize that simple translation may not be enough. Take Office v.X on the Mac for example. It's lack of full RTL and Unicode support means some languages can't be supported, even if just the interface is translated. Rubi for Japanese is another language feature that may require access to the source code itself. Not to mention other tasks like modifying their English grammar checker to support new languages...
Merely providing the ability to make a "Language Pack" and translate the strings on the screen does not provide enough access to really support foreign languages. Without full access to the source code, foreign languages will still remain second class citizens
ed
Microsoft should have no problem localizing in Rwanda ;)
The Amiga did this over a decade ago with it's "locale" settings. Anybody could produce a localised translation of application menus etc. In fact there are hundreds of such "locale" settings on aminet.
I read an account in 1999(?) detailing how the government of Iceland wrote to M$ about when they expected to develop packages to run the OS in Icelandic. M$ replied "Well, hmm, never". Not enough by itself, but I just remember that this was the straw that broke the camel's back for me.
Microsoft is far ahead of open source projects in terms of language support in products BUT...
There is usually a version in your local language.
Microsoft Windows China version compleate with anti-Chinese slurs.
One of the first things local governments do with open source is translate the error messages and directions into something the staff can understand.
American companys are legendary for exporting crap. They don't even begin to understand local sensibilitys and insult or piss off everyone.
Microsoft is known for ignoring the sensabilitys of people INSIDE THE UNITED STATES and end up insulting or pissing off anyone who dosen't use Microsofts products and a larg part of the people that do.
American trampling of local culture plus Microsofts apathy twords anything not directly related to Microsoft culture equals an unholy nightmare in the error messages, system prompts, docs and anything else any Windows user has to deal with on a daily basis.
American:
Hit Ctrl+Alt+Del to log in
Vogon:
Punch the guy next to you to urinate on the system
Annother example: "All your base are belonging to us"
It sounds like the bad guy is saying "We captured all your military instalations" or something like that.
Now would YOU want to deal with "All your base" every freaking time you logged in?
And that presumming you didn't bumble into a cultrally significant notion.
Picture a Vogon pushing Control then Alt then Del.. not all at once but in sequence as if Control, Alt and Del were each letters to a word.
(Did I mention Vogons are stupid?)
Purely becouse of the context...
Microsoft is offering to let local governments to do the translations instead of doing it themselfs to address cultrally significant issues in the way things are put.
Open Source projects automatcly do this becouse the translations are handled by locals.
On the other hand....
Yes most Open source projects don't support more than one language for lack of someone in a diffrent locality than the project leader.
I don't actually exist.
Years ago I sold a package called Win/V that allowed you to run native Japanese applications on Windows for Workgroups. This was significant since there was never a Japanese WfW but the Japanese users wanted the networking features.
What made Win/V different is that it didn't just modify the interface to support a different language as the MultiLingual Packs do, but added the underlying code that localized versions of applications need. This way you could run the Japanese version of Excel for example and get all the local features like rubi and Japanese dates but still be running on an English version of the OS. Embassies loved this system as the underlying OS and network would be supported from the home country.
Macs have had this for years with their Language Kits and I don't think Windows has ever matched it. What happens if you try to install Japanese Office 2K on English XP?
If you don't want to repeat the past, stop living in it.