Novell's
ODF commitment is not quite as strong as it used to be, but Sun Microsystems maintains an interest in the success of this international standard, which could bring it more revenue. Google Pack has just had
the inclusion of StarOffice announced. This will bring a nice boost to ODF adoption. Some say that the decision not to include OpenOffice.org instead of this free version of StarOffice is related to Microsoft's patent agreement with Sun, which
goes back to 2004. The Sun deal excluded OpenOffice.org and resembled the Novell deal.
With ODF-supportive software now widely available, things might change for the better. The following article explains what we -- as users, not companies -- can do
to assist the adoption of OpenDocument format.
While the standardisation war is absolutely crucial, I firmly believe that the only way this battle can be won is by making sure that people use OpenDocument in their everyday life.
[...]
Basically, members of the free software community can and should do more than just watch the fight and rest on their laurels: the more people that fight, the more likely we are to win this battle, which is anything but over. We should all keep in mind that OpenDocument might become, even in the long term, a “fringe format” that nobody actually uses. Microsoft’s monopoly on file formats, if that becomes the case, would create unimaginable damage.
Looking at the other side of the fence, it appears as though the weaknesses of OOXML
are beginning to show.
Apple Inc.'s release of iWork '08 this week is "embarrassing," an analyst said Friday, not for its maker, but for Apple's rival, Microsoft Corp.
We recently became aware of
Sam's thoughts on whatever remains in Microsoft's locki-in arsenal and OOXML warchest.
What if Microsoft surrenders the specifications of its legacy .doc, .xls, .ppt and other formats just in time to make a big impact on the voting process for OOXML at ISO (votes due in early Sept.)?
Is now the
perfect timing for such a stunt? The crucial vote next month matters a lot. It affects a cash cow. In general, just to repeat the old arguments, there are many reasons to escape OOXML and anything it touches (integrates with).
- Microsoft wants control over Web content and documents (the hostage argument)
- Microsoft wants all GNU/Linux users to pay macros and .NET (Mono/Moonlight) 'tax'
- Microsoft wants to embed its lock-ins inside Linux.
This was all said before, but it is worth repeating. Do not accept Moonlight, OOXML, HD, MS-DRM, or XPS (among other next-generation lock-ins).
There appears to be a
well-coordinated plan involving XPS/OOXML/HD/XML
du jour, which Microsoft shoves into standardisation processes in order for Ecma to build tomorrow's lock-ins while
pretending to be open.