Microsoft to release ODF document converter
,----[ Quote ]
| Critics of Microsoft's OOXML have complained that it overlaps
| with the functionality already in ODF and that there should be
| only one standard. Others have complained that the
| specifications--at more than 6,000 pages--are too difficult
| to implement in products.
`----
http://news.zdnet.com/2100-3513_22-6155585.html
Microsoft's press release has, as usual, included "intellectual property" in
it.
Also, have a look here to see some hidden truths:
http://boycottnovell.com/2007/02/02/microsoft-openxmlodf-translator-10/#comment-309
It's one of the developers of a plugin.
,----[ Quote ]
| "1) It's not full round-trip, there is a public warning by no else
| than the CleverAge guy on his blog. Any government mandated full
| round-trip scenario is thus DOA.
| 2) if you take the status documents (CSV files) for the one way or
| other way conversions, you'll see as much as half of the items with
| no status, or with partial status only, i.e. not complete.
| 3) that list in the point above deliberately ignores important
| features of documents such as password-protection.
| 4) it uses C# because the XML is so bad that it cannot rely on
| XSLT transforms alone. This proves the point of anyone questioning
| the value of the XML markup versus binary formats.
| 5) It uses C# and .NET 2.0 meaning that you are required to use
| Microsoft own proprietary stack just to run the code. In other
| words, this force feeds Microsoft .NET into corporations, whether
| they want it or not."
`----
|
|
