Linked by Eugenia Loli on Thu 24th Aug 2006 16:33 UTC
Features, Office Massachusetts will begin using OpenDocument as the default document format later this year as planned, but it will be sticking with Microsoft Office in the near term, the state's top tech executive said.
Permalink for comment 155906
To read all comments associated with this story, please click here.
MollyC
Member since:
2006-07-04

OpenXML is an open standard. As such, one can guarantee the fidelity of documents converted between OpenXML and ODF (as much as can be, anyway, since ODF doesnt' support all of MS's features). In the case of using the MS sponsored plugins, OpenXML is merely a temporary intermediate format. Someone starts Word, opens an ODF file, it's converted on the fly to a temporary OpenXML file, Word opens that file, and converts the data to its own internal structures. The reverse happens when saving to ODF.

How does the "good" ODF plugin work when reading an ODF file from Word? Does it convert the file to .doc then feed that .doc file to Word? What's the difference (besides the fact that the ODF to DOC conversion is based on OO.o's DOC support, which is faulty for complex files)?

Oh, and your main complaint when you mistakenly said that Office 2007 was required was that users would have to *pay* for Office 2007, so using MS's ODF plugin wasn't free as in beer. Now you're chaning your story to say that you're concerned about lockin (which, as I've show above, makes no sense).

And you keep spreading the myth that OpenXML is a Windows-only format. It's not. MacBU is working on adding OpenXML to Mac Office as we speak, so it works on Macs. Apple is one of the sponsors of OpenXML, so that practically guarantees that it works on Macs. Novell's Gnumeric spreadsheet already supports OpenXML, so OpenXML works on Linux.

And before you start talking about ActiveX controls and whatnot, please try to explain away the fact that the Windows version of OO.o supports OLE, a windows only technology, and therefore OO.o can produce ODF files containing windows-only stuff (that being, OLE objects). What happens when such a file is opened on another platform? The app must deal with the stuff it doesn't understand or support (i.e. the OLE objects) by ignoring it, keeping it around as a blob, or whatever. It's the same with OpenXML. If an OpenXML file contains ActiveX controls, OLE objects (which are pretty much the same thing in that they're both embedded COM objects), or other Windows-only stuff (if there are any other Windows only stuff that can be saved; I don't know of any), and an app on another platform must open the document, then the app must deal with those things in the same way and ODF app would have to deal with OLE objects stored by the Windows version of OO.o.

Edited 2006-08-25 15:57

Reply Parent Score: 3