Microsoft's Open XML Project A Short-Term Fix
TechPro writes "In an interview with eWeek the managing director of the ODF Alliance (Marino Marcich) was pretty dismissive of Microsoft's Open XML Translator project. While the move was a recognition of the ODF Format's acceptance by government's around the world, the installable software plug-ins that would be created under the project were really 'only a bridge, a stopgap measure that will probably not be acceptable to government's around the world over the long term. Plug-ins simply don't give the benefits of open file formats and standards,' he said."
Quoting the blog entry:
python>>> q="'";s='q="%c";s=%c%s%c;print s%%(q,q,s,q)';print s%(q,q,s,q)
They are being obtuse by ignoring the spirit of the request to support open standards. Microsoft is attempting to win the battle by frustrating users. Proprietary formats have kept them in business for many years -- why change now? However, I remember when they supported dozens of file formats .
Didn't MS do something similar with Java? Basically have their own "interpretation" of it which is almost, but not quite, compatible. How difficult would it be to make MS' version just off from everyone else's?
If brevity is the soul of wit, then how does one explain Twitter?
Huh? Many Open Source projects or 3rd party companies offer paid technical support for the project. For example, both Sun and a variety of consultants provide paid support for OpenOffice, including its support for ODF.
In short, OO.o natively supports ODF and has technical support, MS Office has an ODF plugin in development, but MS won't offer tech support for it.
python>>> q="'";s='q="%c";s=%c%s%c;print s%%(q,q,s,q)';print s%(q,q,s,q)
I don't understand the problem. If it's a plug-in, and it reads and writes to the ODF standard, where is the problem?
The only thing I can think of is if people worry about a Microsoft "upgrade" breaking this plug-in. And then having to wait for the patch to the plug-in.
Excuse me, but, fuck "translating". This isn't about "translating". This is about being able to read ODF files and save your work to the ODF format.
"Translating" only comes into play when you're talking about:
a. Converting all your previous work to a new format.
b. When some people you are communicating with are restricted to the
c. And Microsoft's "Open" XML format will only be available in their NEXT release so it won't affect anyone who is still using their current or a previous release.
Am I missing something, somewhere?
Microsoft's claims seem to center around an organization upgrading to the next release of MS Office and then migrating to the ODF format.
While I see most situations as an organization migrating to the ODF format from an existing installation of MS Office 2000 or previous.
how long till they embrace and extend? Microsoft Open Document Format ODF with extensions, you can open ODF documents, but once you do microsoft starts "updating them" with MS only extensions, making MS documents all but unreadable in other word processors, and once an ODF file is opened in MS office it is modified so no longer conforms to ODF. They would surely claim, hey we support ODF see, everyone else is just not smart enough to offer you the extra stuff we put in, aren't we the greatest? 1. take someone elses great idea 2. break ...mmmmm extend it so it only works with MS windows
3. claim everyone else is broken
4. profit!
A Smith & Wesson beats four aces -- Murphy's Law of Poker
There really needs to be a reference renderer for ODF. Something independent from OpenOffice, with examples of all of the grammar and semantics in the spec.
The notion that any MS project of this nature is a short term fix cannot help but to be dead on target. As a point of discussion, look at the release timeline for the next releases of Internet Explorer, and even Windows itself.
Microsoft takes considerable heat from many sources that it's development process is dragged out far beyond need or reason. Look at the long development cycle with consideration of anti-trust verdicts, agreements, etc. and you begin to see some logic.
Microsoft is under some legal obligation to de-bundle or make removable certain components of their preferred distro. These obligations have an expiration date in the not very distant future. That expiration date is also not rediculously far beyond the historic release cycle for MS product upgrades.
Given the choice of re-engineering my product so a specific component MS wants to become ubiquitous may be removed, or delaying release a few months and using the time to tie it in so tightly that the notion of removal becomes irrelevant, guess what Microsoft will choose to do.
With delayed release they allow themselves to present that they are in compliance with all orders in effect at time of release, without having to de-couple anything. As a result, your filesystem browser is also your internet browser, is also your front end for all GUI desktop apps... Nevermind that this is in complete opposition to the expectation that the kernel is the interface between hardware and all other software, and that the command shell, filesystem browser, web browser, GUI windowing system, etc. all fall into the category of 'all other software.'
My office has been taken over by iPod people.