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.'
What antimonopolistic evil behaviour!
Actually customizing their products to different markets. UN FRICKIN BELIEVABLE.
Now throw yer tantrum kids.
I don't need no instructions to know how to rock!!!!
Please, like it or not, MS is already light years ahead of OSS in terms of localization and supporting foreign languages. We've got a lot of catching up to do before we're even in the ballpark!
The NorCal local language pack will add the words hella and and shit in as many places as it can.
"Ah man, now I get it. The help files are hella easy to understand 'n shit. So if you wanna shut down, click the start button, and select Shut Down And Shit"
Meanwhile, the Southern Californian Localization will feature such items as "Shut Down - It's Just Called Shut Down"
Heh.. that sounds liek them wantign the OSS kind of workforce without payign the price...
...the schmoe who has to translate all the stupid shit Clippy says into other languages.
Where can I get my hands on these development tools so that I can start on a ROT13 version of Office?
Vg nccrnef lbh ner gelvat gb glcr n yrggre. Jbhyq lbh yvxr zr gb uryc?
If my answers frighten you, stop asking scary questions.
I don't know exactly what this "hedge" is. Open-source software has been translated by locals for a long time already. It seems that something even more important to these locals would be the price and reliability of their machines. GNU/Linux might be the better system for them to run, given limited resources.
I have two eyes, I have two feet.
Countries like China have local regions which don't speak either Mandarin or Cantonese, yet these are most likely the only 2 Chinese languages that Microsoft localizes their products for.
Vonal Declosion
How Do you say General Protection Fault in swahili?
EEEEeeeeeeeeeee!!!!
ThunderBird. Nuff said.
So Microsoft is giving us the priviledge of letting us translate their products for them. For some reason I don't think this will work well commercial product. You paid for it, why should you work more? Obviously for open source, it's diffrent.
For $400 a pop you would have thought they could have done this themselves.
Help fight continental drift.
The MUI (Multi-Language User Interface) Pack has beena available for the US-English version of Windows for years.
Localized versions of Windows have been available for years as well.
Now they DARE to Localize Applications?! THOSE BASTARDS!!!
...Also, I didn't know Buggalo could fly.
Give them some credit where it is due. Microsoft has always pushed multi language support at every level long before OSS was a serious contender. All their OS API's support unicode, multi language versions of their OS's and many applications have been around a long time.
I wonder if somewhere down the line MS will turn around and lock up users into only opening files made under a certain language something a-la DVD "scheme" (yea dual use term that word scheme). So user Wong in China creates files in China to send to his brother Ming in America. Will user Wong also have to buy an addon somewhere in the future?
MoFscker
Microsoft didn't even want to support Icelandic,
in spite of the government wanting to fund the
whole project.
Now, with Linux supporting all sorts of weird
stuff like Welsh and a zillion Indian languages,
Microsoft is losing out in places. All those
little annoying-to-support markets add up.
So, what license is to be used for these translations, written by third parties? Will Microsoft try and demand ownership, or at least commandeer a right to unlimited use of the translation?
If it is legally possible, it would be a really interesting experiment to write a translation and release it under the GPL, then sit back and watch the reaction.
This sounds to me like they're just outsourcing the task of translating their software to different languages to other small countries that wouldn't make it financially worth it for microsoft to do it.
Microsoft has announced plans for a program to help governments produce local language versions of key Microsoft applications
Shouldn't that be the other way around? Why should governments be doing Microsoft's work? If Microsoft wants to sell in upper Mongolia, it ought to make the effort to localize its own damn software for that market.
If you ask me, this is just one more example of Microsoft's incredible hubris.
I'm in China and I've never seen a non-pirate version of any piece of software, including on computers of reputable companies. Not only is there no respect for copyright, there is no understanding of the concept. The increase in profit will not be that great because everyone will use the new localised software... but in pirate copies with no money going to MS... but I guess that's ok if you rate it by convenience to humanity.
There is nothing monopolistic about making your product available to as many people/organizations/governments that you can.
Where I come from... we call this competition! You know, where different organizations tailor their products to a given market and duke it out to see who succeeds.
Help Brendan pay off his student loans
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
Dialectizer Wizard
Please choose a language...
( ) Elmer Fudd
( ) Redneck
( ) Jive
( ) Cockey
( ) Sweedish Chef (my favorite)
( ) Moron
( ) Pig Latin
( ) Hacker
(BTW, this is from The Dialectizer site - Microsoft currently blocks them - no sense of humor)
Funny that it took so long for MS to realize they'd been had... I remember a friend of mine translating KDE documentation in french about 4 years ago... Not to mention the fact that asian fonts have been almost constantly present under linux, as far as I can remember. Besides, China already has Dragon Linux, and they wouldn't switch back to windows for anything else than a nuclear war threat... and even then it'd be a tough challenge! So guess what: that's not going to make a difference in the long run. MS has lost the initiative, and they're trying to make believe they still have it... I hope we can prove they're behind the Opensource community, and have been ever since linux came to being!
---- I am certain of only one thing : I know nothing else.
So one wonders what kind of antiquated practices MS is using that requires a 'special' program to allow localization. Could it be that perhaps MS is not competing against OSS, but is continuing it's fight against best software engineering practices. [And I know that many at MS know how to write code. I have their books. OTOH, we see many cases where corporate and monopoly market interests contraindicate best practices.]
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
When Alpha was struggling, MS helped kill it by porting only part of its portfolio, and making difficult for other people to port theirs.
Now, MS WXP and MS Office... what about countless other apps? And is it as easy for ISVs to translate theirs? Then, can they ship a binary with multilanguage built in as in POSIX systems?
And even if people could translate all that mass of software, will they do proprietary software vendors' work? Perhaps for MS Office and WXP, but I doubt for anything else.
In the end, we still have an edge here. MS actually progressed just a little.
Leandro Guimarães Faria Corcete DUTRA
DA, DBA, SysAdmin, Data Modeller
GNU Project, Debian GNU/Lin
Yes, very witty PARENT ... however, it really goes to show how Open Source has really rocked the industry (especially Microsoft),
I think this will be the first of a whole series of changes, which should be good for everyone who doesn't depend of closed IP.
pantalla azul de la muerte!
e.
Build Your Own PVR/HTPC news, reviews, &
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.
Their language packs wouldn't be complete without these languages/alphabets:
- Ebonics
- Pig latin
- Esperanto
- Elvish
- Klingon
- Linear B
I guarantee you Microsoft won't support any of these. But the open source community is certainly not above it, and will surely be the only recourse for anyone needing to localize software in those languages. And I'm sure there's more I haven't named here.
why does localization in .NET suck so hard? compared to how Java handles internationalization (not perfect by the way), the support in .NET feels weak. In fact the project I'm on now has completely foregone internationalization because it isn't sufficient. Instead, there's development teams in other countries, who localize it for other languages. Often, they end up rewriting most of the application. Internationalization is hard and isn't simple, but having a good framework isn't just supporting Unicode. Supporting Unicode is the minimum requirement.
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.
...when the market speaks, even BeelzeBill listens.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
So this is a lot like the Qt Linguist, right? Only Qt Linguist is here already, open source, and good for any Qt/KDE application.
Once again, Microsoft at the forefront...
The BSOD. It's universal.
PO files in Debian for each language
http://www.debian.org/international/l10n/po/
How many new buffer overflows will all these previously fixed-length strings introduce? A zillion?
What a strange bird is the pelican, his beak can hold more than his belly can.
[ ] I AGREE.
[ ]I DO NOT AGREE.
Wh47 d1d j00 541, 31337 15n't t3h r0xor5 ne m0r3???
What about languages that don't have direct translations for key words like "security hole", "patch", "bug", "unstable" and "hotfix"?
While we argue and sue each other over dinosaur mascots...
While we debate Open Source versus Free Software versus GPL versus LGPL...
Microsoft is adding more features to their products...
What percentage of the desktop does MS own now? 90%? 95%?
Wonder why? I don't.
We could always stop majoring on the minors and make better software... but's that just me.
Agile Artisans
Yay! now we can get the:
pantalla azul de la muerte
(Blue Screen of Death - Spanish from the fish)
For a while now, they've actually been producing local-language software, in a desultory and half-assed way, specifically in response to (usually much better) local-language free software. See, for ex., http://www.kyfieithu.co.uk/item.php?lg=en&item_id= 79 for Welsh, Nynorsk (the *other* Norwegian), and Catalan.
Actually you're confusing the spoken language with the written language.
Most computer program uses the written language rather than the spoken language. After all, how often do you ran a program that had a southern accent...
But there are two versions of written Chinese-- they're called traditional and simplified. The latter was created in the middle of last century.
Unlike spoken Chinese, you don't have the numerous dialects to deal with. So it is a reasonable thing for Microsoft and RedHat to target just these two versions of written Chinese.
-cmh
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.
But here we have a company with over $60 billion in the bank, pulling in more than $1 billion per month in pure profits, raking in unheard of profit margins on their products, and they are asking local and regional governments to provide them with gratis localization services.
Shameful.
-- My choice of computing platform is a symbol of my individuality and belief in personal freedom.
The Local Language Program will provide local and regional governments with "language interface packs" ...
....
Oh, so it's only "governments" that rate, hmm?
No help for the Esperanto community, I guess.
Though it wouldn't surprise me to find Microsoft courting the Klingon-speaking community
-kgj
-kgj
Is this MS saying "We're sick of all your complaints about incorrect rtranslations, so we're going to let you do your own translations, so we don't have to pay these translators any more."
MSS: Microsoft Support, how can I help you?
Non-US User: Hi, there are three buttons on this dialogue box I'm getting which translate to "Next", "Yes" and "Ok". How do I know which one to press?
MSS: I'm sorry, we don't support foreign language issues. Please call your local technical support and talk to your translation team.
Politas
Microsoft is doing this to compete with Linux. Since there aren't any decent grammar checkers for Linux, they are not going to worry about it.
I've been following the Welsh translations of KDE (odd hobby, I know), and they've been discussing these "Language Interface Packs". Apparently, installing them converts Windows into that language, yes. But that doesn't mean that one user can use Welsh (or French or German) and another individual use English (or German or French). So, you're locked into ONE LANGUAGE PER WORKSTATION. Other projects (like KDE) allow users to switch languages back and forth.
There's an article (in English) on their website.
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.
m$ really knows how to sell simple (and already established) solutions as innovative, simple because their products did neglect such needs till now. the l18n issue is soooo damn old, and everyone knows that it takes such a little effort to implement (it's mostly about externalizing strings from your source and managin' formatting objects in a centre place, like dates). it's nothing what i couldn't do with my eclpise in 5 minutes. but the average business person will still think that m$ did invent the whole thing. (which they didn't, btw)
Here's what I've heard on the street, and I could be highly inaccurate, but here it is anyway:
Some weeks ago, CNet came out with an article on localization, using Rwanda as an example.
Within a day or two, Microsoft had reps in that country, and offered the government all the MS software it wanted at $2 (US equiv) a CD. Also, resellers would get a sweet deal, to either increase profits there, or lower the cost of computers.
So, news of providing hooks to make locally localized versions seems natural. Microsoft isn't stupid, and it isn't sleeping either. These are decidedly tactical moves.
You can look at it this way, also: Competition between Linux and MSoft is resulting in a boon to poor countries: much cheaper software.
Sounds to me like they are just trying to outsource some work. Nothing comes from MS with no strings attached :)
Can I still hate Microsoft, regardless?
With all their billions in the bank, why can't they just pay for the translations? I can't believe that a government would spend resources doing translation work for Microsoft.
Of course, M$ is going to try to get away with not having to pay for it. But I doubt governments (and of course just those of relatively low-population countries) will want to assist funding for them, seeing as how they have such a huge war chest.
I feel confident that gov's will prefer to fund translation on Linux, and M$ will be forced to pay for the their own translation anyway, if they want to get into the market.
Cheers, Michael From sunny Toronto
DichDaq pa' taH tlhIngan?
Yeah, yeah, yeah. The story is a dupe, the topic is boring, the facts weren't checked. WE GET IT!!
With a pair of Chinese and Japanese software companies developing a version of Linux for the Asian market I'm sure that M$ can already see their potential market shrinking. I'm also pretty sure that many at M$ are worried about the desktop deal that Sun has struck with China. So M$ tries to counter these moves with a language pack? I'm sure that M$ is going to have to try a lot harder than that!
Free Firefox news reader.
Sarcasmometer? Oh, that's a useful invention...
Where? Perhapse you'd like to post links to the "first bunch" of crying-foul posts? And keep a close eye out for claims of monopolistic or anit-competative behavior. After all, that's what the "insightful" post claimed would be the complaint (I think).
What I've seen are quips about translating clippy and the infamous BSOD. I've seen claims that this "advancement" is a reaction to Linux's current abilities. And I've seen the question of whether this kind of community effort / pro-bono work should be done for commercial software with premium fees.
So here's the counter-issue for you. The "problem" being highlighted here doesn't exist. It was a knee-jerk reaction to criticism often generated by a company who, frankly, deserves criticism.
Now - I will agree there are complaints I disagree with. Heck - there are compliments I disagree with. But please. Do us all a favor. Attack the issue at hand. Avoid sounding like the zealots you decry.
Even when you use small words.
> Can I still hate Microsoft, regardless?
Yes, in more languages than ever before.
Sheesh, evil *and* a jerk. -- Jade
Umm, you have to either ship a seperate language DLL for that, or you have to ship a new exe (depending on whether the string tables were in it or the dll). A localized version.
No, you don't. Win16 resources supported multiple string tables within the binary, one for each supported code page. One binary can support multiple localizations, with the Control Panel configuration specifying the default code-page for the application. The app could use the API to format dates and times. Many of the important localization tools debuted in Windows 3.1.
You're right about the dialog sizes. Dialog metrics have always been a problem, even for plain old ASCII apps.
In Win16, nothing was Unicode - they used code pages (an IBM standard I think), which did support multi-byte characters.
You also have to worry about "unsupported" characters in some language versions when you're using anything that's not unicode (CString anyone?).
CString has supported Unicode and other multi-byte sets since MFC 3.0 - when NT 3.1 was released. When was that - 1994?
I feel Microsoft finally got their act together for locale support with NT - an OS that was natively Unicode, and then with Office 2000, which properly supports Unicode. As for the defense of Win16 -- I was just rebutting the assertion that string tables are something new for Windows. They're not.
It sounds incredible to me that Microsoft actually tries to get governments to translate their software for them free, while Open Source localization groups are desperate with getting governments to participate or provide even little funding.
Perhaps we would need to organize better?
For some time, I've been trying to find out if there exists a collective effort for localizing open source software, which covers both all softwares and all locales.
Currently, we seem to have two types of localization efforts: software-specific and national efforts. For example, the major OSS softwares, such as KDE, Gnome, and OpenOffice have organized translation efforts. Then there are some national efforts. For example, in Finland, we have organized a joint national effort as a working group, which gathers the different Finnish localization teams together and aims to provide them publicity, recruiting, funding, other resources, and generally a channel for cooperation. We currently have KDE, Gnome, OpenOffice, Debian, and some other translation teams working together on common issues such as quality, vocabulary, and tools. I have noticed that there exists also some other national or language-specific efforts, such as for Arabic and South-African languages. However, I haven't found any cooperation effort between these national efforts, where we could participate.
So, what I'm looking for is a universal effort that covers both all the different localization projects for different softwares, and for the different languages (or nationalities). There exists some more-or-less generic efforts, such as the Translation Project, but those which I've seen cover only a limited set of software products (TP covers some 100 but it's still rather limited).
If you know about such an universal cover effort, please tell me.
Otherwise, perhaps the time is ripe for starting to plan for such an effort. I'm not talking about any massive organization, just a loose, light-weight organization that would serve as a center for information sharing and cooperation. Well, basicly a well-structured web portal would suffice.
I begun to wonder about this last fall, when I started designing a portal-based information system for the Finnish national localization effort and did preliminary organization analysis. I noticed that many of the tools we would need would also be useful for others. Well, of course it may be difficult to unify such tools between different efforts, as different efforts have their own preferences, but it would be nice to get to know what other efforts need and what they could contribute.
Our Finnish national effort is still slowly forming, but we are quite active in certain areas such as quality assurance. We have had one joint workshop event so far and have planned to have one twice a year (next one is scheduled for May). Last year, we produced a 26 page report about the status of different Finnish localization projects. We have also tried to make contacts with translation departments of universities. Our effort for getting funding is still in infancy.
We would very much like to share "patterns" of organizing national and software-specific efforts and serving the actual translation teams.
So, is there anyone interested in world domination?
Now throw yer tantrum kids.
Tantrum? I'm delighted. In order to protect their monopoly on all fronts they are spreading their resources thinner and thinner in order to combat the various threats from competitors, open Source and open standards (for instance Linux, Open Office/Star Office, Java, XML, Mobile platforms) This means loss of focus, low quality, delayed releases. And hopefully their downfall.
Being bitter is drinking poison and hoping someone else will die
Having said that, it's certainly a start. I think we will see Microsoft, and other proprietary software vendors, forced to provide localisation in the future, to compete with Open-Source software which enables this.
perl -e 'fork||print for split//,"hahahaha"'
What with them having argued so strenously (in USia and EUia) that these are "an integral part of the OS". Let's see how that assertion pans out in practice.
If you were blocking sigs, you wouldn't have to read this.
We used the local language support fact to persuade our government to use Open Source. Now, Microsoft feel the heat and tried to pursue the same path as ours!
Shame to them! They are really a cheap imitator. ;)
Me - Fedora, Mandrake, Nano and Abiword translator
The current localization efforts are so lame. I want my language skins. Please...
Jacek Artymiak
freelance consultant and writer
master of many a page
What antimonopolistic evil behaviour!
Actually customizing their products to different markets. UN FRICKIN BELIEVABLE.
Now throw yer tantrum kids.
Actually it is likely a smokescreen. Microsoft has long touted their localization efforts while in reality avoiding numerous locales even when they have lots of customers in those locales. In the case of Hebrew, they declared there would never be Hebrew language versions of their software even though the Israeli government offered to pay for the development and ultimately even to supply the developers if that is what it took. Microsoft said NO.
Now they are claiming they will work with local governments in localizing MS Software? I will believe it when I see it.
After all these years there is still no English version of Windows or Office.
Office has an English dictionary option but the application itself is in American (U.S. English). This is the nearest a Microsoft application comes to English.
60 million speakers of English in the UK and no local translation! We still have to put up with "favorites" and "color", while even the few Welsh speakers get their own version!
Crazy!
The Register On Windows, Nynorsk, Sami and Catalan: ... First ask yourself if they teach Catalunyan in school, see if the government in Madrid approves of a Catalunyan version of the software (or would it be common-sense just to keep ALL offices Castillian and not create issues between versions), and then see if M$ would make money out of it. Basque is another thing altogether... :| (as well as Galician, Andaluzian etc...)"
Paul Taylor writes "So why Nynorsk, and not Catalan? Little chance of the Catalans getting their own language in Office... it's not a matter of economics, it's a matter of politics. Nynorsk is an "evolution" of Norwegian as far as I know, and M$ can hide behind the "Bright Shield of Progress" and getting some merit from the overall hack community. Catalunyan is really a political matter. Solved only with Madrid's approval
Oscar del Pozo Triscon, Softcatala writes I've read your poignantly funny (article about Microsoft Office in Nynorsk. I couldn't help laughing out loud while reading the last paragraph, a sort of call to arms to us Catalans. Well, I'm happy to report you that we have been fighting to have a powerful, honestly-priced Office suite in our language, and we have succeeded indeed. Softcatala, a not-for-profit organisation that localises free software into Catalan and advocates its use (and to which I obviously belong), localised OpenOffice 1.0 to Catalan a few months ago in cooperation with Sun Microsystems, and recently distributed 70,000 CDs with it through a Catalan newspaper. As a result, the Education Department of the Catalan Government is looking very closely to OpenOffice to replace Microsoft Office in all schools throughout the country. So, surprise, surprise, despite all previous arguments and PR rubbish, Microsoft have promised the Catalan Government a localised version of Microsoft Office this year. Of course, we all know how strongly committed Microsoft Corporation is when it comes to minority languages. So we will keep releasing Catalan versions of free software, just to prevent their very strong moral fibre to be tested by the absence of competition. By the way, we'll be glad to give technical assistance to other organisations looking to translate OpenOffice or other free software to a "non-profitable language". OpenOffice.org catalan version
Miquel Strubell writes Dear Drew, Within 24 hours of your article "Windows comes to Nynorsk" being posted on the Internet, it received coverage in Catalonia. Thank you for raising the issue once again. Microsoft translated 1.0 versions of Windows 95 and 98, which they then failed to update. These versions were not introduced into their catalogue and were extremely hard to find in the PC corner shop. They also signed a third agreement with the Catalan government, this time without an exorbitant invoice attached to it, to produce a Catalan version of Windows XP. What they didn't say was that the vesion translated would be the network format, so it turns out out that the home user has been cheated! Nynorsk has achieved a version of Office, an area where Microsoft have entrenched themselves in refusing to produce a Catalan version. Good for Nynorsk speakers! More and more Catalans are turning to alternatives such as open code products, which www.softcatala.org distribute free of charge.
BBC:Boycott threat
In both instances, Microsoft pointed to the large cost of translating computer programs.
But the Norwegians had an ace up their sleeve.
The main organisation working for the Nynorsk language got most of Norway's high schools to threaten to boycott all Microsoft software if they didn't come up with a New Norwegian version of Office.
Many more users of minority languages will no doubt be inspired to fight a renewed battle for their
-= If you fight Dragons long enough, you will become a Dragon =-
"In the case of Hebrew, they declared there would never be Hebrew language versions of their software even though the Israeli government offered to pay for the development and ultimately even to supply the developers if that is what it took. Microsoft said NO."
In some of the better software products, you can just take the messages file and translate it yourself, without any need to request that the vendor enables that feature for you.
"Free Software", I think they call it. Hey, you even get freedom of language thrown in...
There is nothing monopolistic about making your product available to as many people/organizations/governments that you can.
Even if you do it at a net loss to your company?
You could call that "generating goodwill" and I'm sure there will be people calling it just that. Company shareholders will tolerate some goodwill as long as they can be convinced it translates into the bottom line at some point. OTOH, I could take a fair hit of ill-will as a company as long as I was making billions of dollars per year in profits, so goodwill is only so valuable.
But having been through the school of TANSTAAFL I would be suspicious of a profit-making entity just giving something away. They don't do it without a well thought-out profit-minded reason.
"Provided by the management for your protection."
...I'm just wondering when they're going to openly admit that to themselves and the public.
For years I've been wondering why Microsoft doesn't join the corporate fray of OSS, on the way mixing it with their branding and doing a branding variant of the 'embrace and extend' thing they're into. After all, nobody gave a damn about licensing until MS started ranting about the GPL being anti-american and at the same time screwing up their licensing as to piss everybody off.
Anyway, I've narrowed in on some optinal answers to this question:
1) MS is to big, slow and stupid and the chiefs are to Windows-focused that they don't see the light.
--I don't think this is the real truth. It fits into a typical MS rant and would fit to a megacorporation the size of MS, but considering that they actually are a software company, and a quite succesfull one I think this answer is to simple.
2) MS couldn't care less. Even if they only hopp on in 2 years from now when they've milked the last proprietary cow, they'll just throw in a few billion, by the one or other Linux company, mix in a little DirectX and Exchange for Linux and squish RH, SuSE and Madrake along the way.
--This seems more likely. But then again, if that's their plan, they would have started this much earlier. And I dont think they could gain foothold any more, neither now or 2 years from now.
3) The MS revenue stream relys so much on markting hype and exclusive Windows branding that MS has no other choice than to take up the fight, even if they're going to lose in the end anyway. They'd rather shoot themselves than admit that OSS has them by the balls and start an ordered retreat out of the proprietary software market in the long run. Taking every money they can get on the way and pushing forth into embedded and home entertainment systems.
--I would think this to be the best answer. Yet even this way it's a dead end for MS as a monopoly. No way in hell can they stand up to a Sony & Matsushita tag team who've just decided to use Linux as their prime embeded system for home entertainment - because it's cheaper and has less lock-in.
Either way you put it, MS as the master-blaster-of-all-things-Computer is done with. They'll either manage to get the curve into a major service and embeded vendor and strengthen their strong branding in that area or they're going to end up like Commodore or something simular.
My 2 Eurocents.
We suffer more in our imagination than in reality. - Seneca