ongoing · Life Is Complicated - 0 views
-
Fortunately for Microsoft, the DaVinci plugin is coming, which will enable Microsoft office applications to comply with ISO 26300. We all understand the financial issues that prompted the push to make OOXML a standard (see Tim's comment above and http://lnxwalt.wordpress.com/2007/01/21/whose-finances-are-on-the-line/ for more on this) and ensure continued vendor lock-in. However, OOXML is not the answer.
-
ODF can handle everything and anything Microsoft Office can throw at it. Including the legacy billions of binary documents, years of MSOffice bound business processes, and even tricky low level reaching add-ons represented by assistive technologies.
-
Yes! It's Da Vinci time. I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run? Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci. California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.
I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept. If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF. We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications. - ...1 more comment...
-
Yes! It's Da Vinci time. I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run? Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci. California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.
I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept. If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF. We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications. -
Yes! It's Da Vinci time. I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run? Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci. California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.
I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept. If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF. We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications. -
Hi guys,
There is an interesting discussion triggered by Tim Bray's "ongoing · Life Is Complicated" blog piece. Our good friend Mike Champion has some interesting comments defending ISO/IEC approval of MS Ecma 376 based on many arguments. But this one seems to be the bottom line;
<mike> "there is not an official standard for one that (in the opinion of the people who actually dug deeply into the question, and I have not) represents all the features supported in the MS Office binary formats and can be efficiently loaded and processed without major redesign of MS Office.
..... So, if you want a clean XML format that represents mainstream office document use cases, use ODF. If you want a usable XML foormat that handles existing Word documents with full fidelity and optimal performance in MS Office, use OOXML. If you think this fidelity/performance argument is all FUD, try it with your documents in Open Office / ODF and MS Office 2007 / OOXML and tell the world what you learn." </mike>
Mike's not alone in this. This seems to be the company line for Microsoft's justification that ISO/IEC should have two conflicting file formats each pomising to do the same thing, becaus eonly one of those formats can handle the bilions of binary documents conversion to XML with an acceptable fidelity.
This is not true, and we can prove it. And if we're right that you can convert the billions of binaries to ODF without loss of fidelity, then there was no "technology" argument for Microsoft not implementing ODF natively and becoming active in the OASIS ODF TC process to improve application interoperability.
<diigo_