Linked by Thom Holwerda on Sun 2nd Sep 2007 18:40 UTC
GNU, GPL, Open Source Eric S. Raymond writes on his blog: "There's been a lot of debate in the community about how OSI should properly handle Microsoft's planned submission of some of its licenses for OSD certification. That debate has been been going on within OSI, too. OSI's official position, from the beginning, which I helped formulate and have expressed to any number of reporters and analysts, is that OSI will treat any licenses submitted to Microsoft strictly on their merits, without fear or favor. That remains OSI's position. But I find that my resolve is being sorely tested."
Thread beginning with comment 268047
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: The article in short
by lemur2 on Mon 3rd Sep 2007 00:03 UTC in reply to "RE[3]: The article in short"
lemur2
Member since:
2007-02-17

By the way, the fact that Gnumeric, Koffice, Abiword, Lotus, GoogleDocs and more are all able to add support for ODF should tell you a lot about how hard it is for any office suite to support it.

What's also striking about these code bases adding support for ODF is that they have very different origins, are written in different languages and yet they are all making great strides in reaching full support for ODF.


Well, ODF is after all designed from the ground up to be platform-independent and OS-independent.

It shouldn't take Microsoft barely any effort at all to support ODF fully and natively in MS Office. Microsoft engineers (ie not MS managers and not MS PR people) have apparently been quoted off the record (in discussions with Massachusetts officials) as assesing that the task of adding full native support for ODF in MS Office would take about two weeks of effort.

And you have the gall to tell me that Microsoft wants to compete on features.


Precisely. Where is Microsoft's effort to compete on the "native support for ODF" feature? We (the public, the end-users) have been waiting for quite a while now for that feature. It doesn't make sense that Microsoft can't compete on that much-desired feature ... so the only conclusion to reach is that Microsoft has made a political (not technical) decision to forbid full support of ODF by MS Office.

It would seem that the feature Microsoft is keenest to support in its products are the plentiful "lock-in" features, the "requires a Windows platform" features and the "screw the customer" features. One finds these features at their greatest concentration in MS Office.

Reply Parent Bookmark Score: 5