The headline reads, "Microsoft Bows to Pressure to Interoperate with ODF."
It's not even news, actually, according to Andrew Updegrove, a partner with Boston law firm Gesmer Updegrove, and the editor of ConsortiumInfo.org.
"Microsoft's announcement on plug-ins is being treated in the press as 'new news,'" Updegrove said. "Ray Ozzie actually let slip mention of the project last October, and an open-source converter project was started by the same French company last September 26."
"Still, as recently as May 19, Microsoft did not disclose the project when it replied to a [Massachusetts] request for information on plug-ins. Why go public now? Presumably due to the series of pro-ODF announcements made in Europe," he added.
In fact, "The plug-in announcement is but the latest in a series of Microsoft concessions in reaction to the rising popularity of ODF. It will be interesting to see where the string of concessions eventually ends, as this latest fallback to a new defensive position leaves Microsoft far more vulnerable than it seemed only a few short months ago," Updegrove said.
However, much as I respect Updegrove, I don't see it that way.
Regarding the timing, I think that it had much more to do with Office 2007's latest delay. Microsoft had to try to drum up some positive buzz for Office 2007, and this was all ready to go.
But let's take a closer look at this ODF support of Microsoft's, shall we?
First, consider what Microsoft will actually be offering. It's a set of third-party, add-on utilities that will enable Office users — first only Office 2007 users, but later users of other Microsoft Office programs as well — to read and write in ODF.
It is not a set of programs, open-source BSD license or not, that anyone else will be able to use. The Translator will only work with Microsoft's own proprietary programs. You can't use it, as it is, as an independent bridge between Microsoft's formats and ODF.
There are two key phrases here. The first is "third-party."
Jason Matusow, Microsoft's director of standards affairs, came right out and said Microsoft was not contributing code or providing architectural guidance for Open XML Translator.
In other words, if it does a crummy job of translating to and from, don't look to Microsoft to clean up your slightly mangled documents. Microsoft will, however, be supplying technical support.
Why, oh why, do I think that Translator's technical-support line will often be telling users that the fault for a botched document transfer lies at ODF's door? And somehow I think Microsoft's technical support's usual suggested "fix" will be to just use Microsoft's own Open XML instead. "It's so much better," they'll say to annoyed users.
The next part of the Microsoft Translator trap is the phrase "add-on."
Instead of simply building ODF in like any other format, Microsoft is going to require users to download and install the program themselves.
Any time there's an extra step that you don't have to take, most users won't bother to take it. I know it and Microsoft knows it.
Microsoft isn't bowing to any real pressure. It's making a move to help itself continue to sell Office to offices that require open standards but won't drink the "Open XML is an open standard" Kool-Aid.
Updegrove interprets the situation differently.
"Microsoft's latest concession clearly makes it easier for governments and other users to feel safe in making the switch from Office to ODF-supporting software, since Microsoft itself will be collaborating to make document exchanges smooth and effortless," Updegrove said.
"Critics of the Massachusetts (and Danish, French and Belgian) initiative will now know that not only will Massachusetts government workers and the keepers of public records be able to easily exchange documents, but those with disabilities may simply continue to use Office as their peers convert to ODF software, later changing over themselves when accessibility tools for ODF software become available."
I can't see that at all. To me, for the reasons I cite above, this is just more Microsoft smoke and mirrors.
This isn't the first, or likely even the one hundred and first, time that Microsoft has played this open-standard support trick. It did it with "supporting" the Kerberos network authentication protocol.
More recently, Microsoft has been playing the exact same game with Adobe Systems and support for its PDF format in Office 2007.
By doing the minimum to make Office 2007 technically compliant with government and corporate open-document-standard requirements, Microsoft isn't bowing to anything except its greed for continuing its desktop office monopoly.
What could Microsoft do if it were really interested in supporting open standards? Easy: Bake ODF import and export support into Office 2007.
This? This Translator support is just another trap to keep users locked into Microsoft Office.
eWEEK.com Senior Editor Steven J. Vaughan-Nichols has been using and writing about operating systems since the late '80s and thinks he may just have learned something about them along the way. He can be reached at email@example.com.
Check out eWEEK.com's Linux & Open Source Center for the latest open-source news, reviews and analysis.
Copyright © 2006 Ziff Davis Media Inc. All Rights Reserved. Reproduction in whole or in part in any form or medium without express written permission of Ziff Davis Media Inc. is prohibited.