Slashdot Mirror
Microsoft Office 2007 to Support ODF - But Not OOXML
Andy Updegrove writes "About two hours ago, Microsoft announced that it will update Office 2007 to natively support ODF 1.1, but not to implement its own OOXML format. Not until Office 14 is released (no date given so far for that) will anyone be able to buy an OOXML ISO-compliant version. Why will Microsoft do this after so many years of refusal? Perhaps because the only way it can deliver a product to government customers that meets an ISO/IEC document format standard is by finally taking the plunge, and supporting 'that other format.' Still, many questions remain, such as when this upgrade will actually be released, how good a job it will do, and whether the API Microsoft has said it will make available to permit developers to supply 'save to ODF' default plugins will be supported by a patent non-assertion promise allowing implementations under the GPL (the upgrade supplied by Microsoft will not allow ODF as the default setting)."
They may be selling it like pancakes, but I have also seen an upsurge in dissatisfaction.
1) Why do I have to learn a new interface?
2) Why is user X not able to open my files. Why can't we open our shared files?
3) Why is our file corrupted.
This issue has become so great that department managers have been asking me if we can go to OpenOffice.
Current plan is to minimize purchases of systems with Office 2007 and switch to OO next year, after the new version with file sharing comes out.
He who said 1,000,000 monkeys on 1,000,000 typewriters would eventually type the great novel, never saw an AOL chat room
I think what matters most is that MS has committed itself to providing ODF compliance, even if that is a bit limited way, by the end of the first quarter of 2009.
This means that businesses who have been delaying the normal computer upgrade cycle (sometimes for years) now have a clear pathway: they can immediately migrate to OpenOffice under existing WinXP licenses on new hardware, or they can jump directly to an enterprise Linux with OpenOffice. Either way, they can move forward knowing that before they have finished the rollout, the documents they are producing will be compliant with the Microsoft universe.
The timing of this is great for the USA economy. It is much less costly to do a major rollout in a slack period, and we can count on slack for the rest of 2008. It will be easier to hire the needed tech support people, and if the rollout involves moving to Linux, it can be done with a lot less expense in hardware than the cost forecasts of even last year. The time and cost for retraining staff can be more easily absorbed during the competitive lull. Then when the economy gets back on track in 2009, these companies will be very well positioned for fast and strong growth.
I applaud Microsoft for biting the bullet and coming out with this news now. Perhaps now USA IT departments can get out of these doldrum eddies and start making headway again.
But then, look at IE. It took some serious competition, in the form of Firefox, but IE finally did shape up and start adding features (tabs) and reasonable standards compliance.
All we really need, then, is an ACID test for ODF, in which we can show that OpenOffice, KOffice, Google Docs, and even isolated projects like AbiWord and Gnumeric do better than Office, thus shaming Microsoft into doing it right. That assumes they don't get it right the first time, although that does seem unlikely.
Don't thank God, thank a doctor!