03.16.08
Novell/Microsoft Translator: Fail
Earlier today we published a pointer to an article that explains OOXML interoperability as an impossibility. As practical proof of this, consider the results of development work that has probably gone on for over a year.
His results reveal that conversion needs more attention from developers, esp. now that The Netherlands standardize on ODF – with more public agencies to come. The German Foreign Office migrated to Linux and Open Source solutions. The test results demonstrate that PR stunts won’t convince customers that compare the solutions available. The results also indicate that the OOXML conversion will be a non-trivial exercise for competitors. A single international standard could help to reduce the pain.
Why even discuss the unfeasibility of OOXML’s interoperability capabilities in theory when actual real-life “splats” such as the above make good demonstrations? There are more examples of this. From this month alone:
- Microsoft API Pledge Worse Than Useless, Real Standards Needed
- Broken Promises: Microsoft Interoperability Already Broken (No GNU/Linux, No ODF)
- The Latest Hits at Microsoft’s Broken OOXML Platform/App/Format
OOXML is hardly interoperable among and between different versions of Microsoft Office (and never will be). There is no chance of ever achieving decent interoperability between different applications if Microsoft’s OOXML enters the equation. Need it even be added that such interoperability is not free? █
