Summary: Microsoft’s forking of ODF (MSODF) still a serious issue that gets no rest
THE ODF Alliance is unhappy with Microsoft's MSODF and many others have expressed similar disgust. The word is spreading right now that Microsoft’s so-called ‘support’ of ODF causes more harm than good and here is the ODF Alliance quoted:
ODF Alliance managing director Marino Marcich said in a press statement this week that “support for ODF represents an important and ongoing test of Microsoft’s commitment to real-world interoperability. Unfortunately, serious shortcomings have been identified in Microsoft’s support for ODF. Putting potentially millions of ODF files into circulation that are non-interoperable and incompatible with the ODF support provided by other vendors is a recipe for fragmentation.”
The European Open Source observatory has just written about the subject too.
ODF implemented by one company is not the same as implemented by the other seven products.
There’s rumble in the web during the last days. And the reason is something to celebrate, but regrettably only for the first look. Microsoft published Service Pack 2 for their Microsoft Office 2007 product and for the first time in history they decided to officially support saving and opening in Open Document Standard (ODF).
We mustn’t let them get away with this. They should realize, that interoperability is not made by them alone, but by interacting with others, by working together and by sharing experiences. Maybe it’s time for an independent organization to test the usefulness of office documents?
Charles, who is involved in the OpenOffice.org project, summarises some writings:
# I could point to other blogs, but this one comes from Jeremy Allison, author of Samba, now working for the great Satan Google. It’s actually quite interesting because what Jeremy is saying is that all this dispute seems to be based on the impression that Microsoft did the minimum to have ODF work inside MS Office. My take on this is we should first stop getting ballistic at each other, especially inside the ODF TC. What is needed in the interest of ODF and the users, is to have a careful examination not on the ODF conformance in MS Office, but on why, based on experience, the interoperability is severely hampered when using ODF with MS Office. Based on this analysis we should be able to go forward. But don’t let this fool you: this has, I’m afraid, nothing to do with the development of ODF 1.2.
# As an interesting reminder, here’s what the European Commission was saying about Microsoft’s announcement on the support of ODF inside MS Office last year.
Well, if we’re talking about interoperability it has been done. Or tried. We could call it overunderdoing. Here’s the algorithm:
1. pick one interoperability concern
2. solve it up to 85% (percentage may vary)
3. wisely choose the 15% to leave out so interoperability can be said to work but with constant annoyances
4. make a loud announcement to the press
5. profit: everyone will read the announcement but only a small fraction of such readers will notice the missing bits; despite the claimable advances over the previous situation it still won’t be practical to make any use of the announced interoperability
Here is what Microsoft might try next (when the damage it has caused is done):
Is OOXML the better standard?
No, it is not in my opinion. But I think that is what Microsoft now tries to make us public authorities think. I know about the facts behind the scenes. I know that this company declines real support for ODF by doing something strange, not aiming at real interoperability, but at a Microsoft implementation of ODF, not compatible with others. So they, as worldwide market leader, can proof the insufficiency of ODF. And they have the solution for us. Use OOXML instead. It implements every function Microsoft Office does. And the next step is, that other interested implementations should improve their products to implement everything OOXML does. Really simple, isn’t it?
More about it was published in the German press and Rob Weir says: ‘UNESCO/Sun agreement “will promote the use of open source technologies, including OpenOffice.org and OpenDocument Format (ODF) standard”.’ He is referring to this joint development.
In the mean time, whilst scheming to destroy ODF, Microsoft doing the same thing to Web standards. From the news:
WordPress users may want to avoid Microsoft’s new Internet Explorer 8
That was enough for us to uninstall. Looks like IE8 may very well be what some people are already calling, the last nail in the coffin.
See the picture which shows erroneous page rendering in IE8. Someone should hold Microsoft accountable for this. Enough is enough. It’s deliberate. █
“In one piece of mail people were suggesting that Office had to work equally well with all browsers and that we shouldn’t force Office users to use our browser. This Is wrong and I wanted to correct this.
“Another suggestion In this mail was that we can’t make our own unilateral extensions to HTML I was going to say this was wrong and correct this also.”