Linked by Thom Holwerda on Sat 3rd Feb 2007 16:40 UTC, submitted by jayson.knight
Features, Office A Microsoft-sponsored open-source project is expected on Friday to release a translator that will convert file formats between Microsoft Office and rival standard OpenDocument, or ODF. Microsoft started the project at SourceForge last year, relying on three partners to develop the code that lets a user open and save word processor documents in two different formats.
Permalink for comment 209027
To read all comments associated with this story, please click here.
RE[3]: question
by hal2k1 on Sun 4th Feb 2007 12:31 UTC in reply to "RE[2]: question "
Member since:

//No it cannot. If you check the page at , you'll see that there are "disjoint" features not shared by OpenDocumentFormat and OpenXml. So it's technically impossible to write a 100% converter. //

Well, all the more reason not to use OOXML then isn't it? It is especially stupid to use OOXML as an intermediate stage in a process that is trying to produce ODF as the final output, isn't it? Why are you even attempting to do what is technically impossible?

Why not just use the same process as Microsoft use to produce OOXML (which is: internal memory data <-> OOXML) to make ODF instead (like this- plugin: internal memory data <-> ODF) as the daVinci plugin does it, rather than the "technically impossible" (CleverAge convertor: internal memory data <-> OOXML <-> ODF) that the CleverAge converter uses.

As you point out, what the CleverAge plugin is trying to do is technically impossible to do 100%. It is not however impossible to do a 100% conversion like Microsoft does it for OOXML ... and like daVinci does it for ODF.

However, please note your observation is not what I actually said.

What I actually said was "It can save old legacy-format MS Office files in ODF format with 100% fidelity."

This in fact the daVinci plugin can do. What is more, the capability has been demonstrated.

In this context, 100% fidelity means that a legacy-format MS Office is saved as ODF by the plugin. The ODF saved file is then read back in by the plugin, and saved back as a legacy-format file. The files survives the "round-trip" 100% intact.

OOXML cannot do that. The CleverAge plugin cannot do that.

The daVinci plugin can do that.

As far as the fidelity of the file when it is in the ODF format - some data is saved as "metadata". Other ODF applications will have some difficulty reading the metadata ... but that is because Microsoft has obscured the old legacy formats and utterly refuses to reveal their full structure.

Nevertheless, the conversions done by the daVinci plugin are better than those done by, and considerably better than those done by the CleverAge convertor, which is the topic of this thread.

Edited 2007-02-04 12:36

Reply Parent Score: 4