Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

[News] Microsoft Breaks the Law by Breaking Interoperability, Sun Offers Plugin

Hash: SHA1

M$ not playing fair to OpenOffice

,----[ Quote ]
| We did troubleshooting of so many things to make the switch smoother for our 
| users, but, regardless of that, our enemy, was somewhat invincible, and 
| nothing seems to overcome such an obstacle, but don't get me wrong, this 
| enemy is cheating, and this is giving it the edge required to defeat us.   


Better ODF support in Microsoft Office via Sun's ODF Plugin

,----[ Quote ]
| I normally don't post my ODF Plugin news and information on GullFOSS, but so 
| many people complain (everywhere, including in OOo mailing lists) about the 
| bad ODF support in Microsoft Office 2007 SP2, that I thought it might be a 
| good idea to post some information about the ODF Plugin here...   



MS forking ODF? They would love to.

,----[ Quote ]
| By the looks of it, I cannot but feel that MS has found a way to fork the ODF
| 1.1 to suite their world view of having their product as the only one out
| there. I have to agree with IBM's Rob Weir in this post.


ODF interoperability event - Royal Library, The Hague - June 15/16 2009


A follow-up on Excel 2007 SP2's ODF support

,----[ Quote ]
| In other words, all of those Interoperability Directors and Interoperability
| Architects at Microsoft seem to have (hopefully temporarily) switched into
| Minimal Conformance Directors and Minimal Conformance Architects, and are
| gazing at their navels. I hope they did not suffer a reduction in salary
| commensurate with the reduction in their claimed responsibilities.
| [...]
| In any case, this comes down to why do you implement a standard. What are
| your goals? If your goal is be interoperable, then you perform
| interoperability testing and make those adjustments to your product necessary
| to make it be both conformant and interoperable. But if your goal is to
| simply fulfill a checkbox requirement without actually providing any tangible
| customer benefit, then you will do as little as needed. However, if your goal
| is to destroy a standard, then you will create a non-conformant,
| non-interoperable implementation, automatically download it to millions of
| users and sow confusion in the marketplace by flooding it with millions of
| incompatible documents. It all depends on your goals. Voluntary standards do
| not force, or prevent, one approach or another.
| To wrap this up, I stand on the table of interoperability results in the
| previous post. SP2 has reduced the level of interoperability among ODF
| spreadsheets, by failing to produce conforming ODF documents, and failing to
| take note of the spreadsheet formula conventions that had been adopted by all
| of the other vendors and which are working their way through OASIS as a
| standard.


Microsoft now attempts to sabotage ODF

,----[ Quote ]
| - Ask the ODF Alliance to publish a press release recommending not using
| the "Save as ODF" facility included MS Office SP2, due to the bad quality of
| the produced ODF files.
| [...]
| - Start a petition asking Microsoft to make MS Office SP2 unavailable until
| the design flaws in the product have been corrected.
| We must make it clear to Microsoft that their attitude is not acceptable, and
| force them to behave in a better way.


Engage, embrace, extinguish

,----[ Quote ]
| Today we have OpenOffice.org 3.1 gets released. In the meantime, the
| proprietary product from Redmond claims to be able to wirte ODF format, but
| fails. Pity. Money corrupts, but MS Tax Dollars corrupts absolutely.


Microsoft now attempt to fragment ODF

,----[ Quote ]
| One of the first articles published about SP2 and for which I call the
| attention of everyone is from Rob Weir, chair of the OASIS ODF TC (group that
| develops the ODF, to which I belong). It is simply scary to see what Office
| 2007 does with existing ODF spreadsheets.
| The technical details are all on Rob’s blog, but in summary, when opening an
| ODF spreadsheet (.ods file) using Office 2007, it simply removes all existing
| formulas without telling anything to the user, leaving only the values in
| cells (results of formulas evaluation, previously stored in the document). If
| a user wants to test the ODF support in Office, and without giving due
| attention, save an existing spreadsheet, will overwrite the document removing
| all the formulas (as if you were writing a table). I saw absurdities in life,
| but nothing compared to this.


OpenDocument Format: The Standard for Office Documents


A Few Facts As Antidote Against Microsoft's anti-ODF FUD Campaign

,----[ Quote ]
| The best antidote against FUD is facts. FUD only works when people don't know
| any better. So, given some recent anti-ODF FUD in the air, I thought it would
| be useful to provide some facts.
| First, I'd like to show you who voted Yes to approve OpenDocument v1.1 as an
| OASIS Standard in January of 2007. ODF v1.2 is already being adopted by some
| now, of course, as development has continued, but Microsoft chose to stick
| with v1.1, so let's do the same. I think you'll find the list dispositive as
| to who is sincere in this picture. Next time you read some criticism of ODF,
| then, you can just take a look at the list and ask yourself what it tells
| you. And if you are a technical person, here's ODF v1.1, so you can compare
| any claims of deficiencies. Here's Groklaw's chronicle of the OOXML/ODF saga,
| where you can find many resources, including a chronology of events from 2005
| to the present.


Microsoft vs. ODF: arrogance on display

,----[ Quote ]
| Note to Microsoft: This is not how standards work. Frankly, if you don’t
| intend to support ODF properly, you may as well not support it at all. What
| your product writes isn’t ODF. When your product reads ODF, it silently
| discards important parts of the data. (Yes, the formulas in spreadsheets are
| important. That’s the whole purpose of a spreadsheet program! Otherwise we
| may as well be using pencil, paper, and calculators.)


Should we waterboard Rob Weir? And other crucial questions…

,----[ Quote ]
| These are very interesting times for ODF and Open Standards. Microsoft’s
| latest outrage by Gray Knowlton does at least show that if there’s a company
| who practices the « Do as I say, not as I do », it’s Microsoft. Gray Knowlton
| is now calling for Rob Weir, chair of the ODF Technical Committee at the
| OASIS Consortium to resign. I understand Gray. Gray is the Product Manager of
| Microsoft Office at Microsoft. Which means he is ultimately to blame for the
| lousy job Microsoft engineers have done in implementing ODF inside Microsoft
| Office. Gray is in the front line, and you can bet he’s having to answer some
| tough calls from customers right now. Gray does not have to ride the smooth «
| try Seven after Vista » wave; he has to go through the clutter that
| Microsoft’s big heads have created by thinking: What if we had ODF wrecked
| inside Office and get the world to believe that it’s not our fault? That’s
| Gray’s problem. And this is how we come to the waterboarding of Rob. But I
| digress.
| [...]
| Bad, bad, evil Rob. Not only he didn’t go to your grand astroturfing party,
| but he apparently forgot to mention SP2 at the coffee machine ten times in a
| rowthe day you released it. That must be depressing. Anyway; talking about
| missing the chance to provide your input before things happen: How come
| Microsoft left the OASIS ODF TC in 2003?

Version: GnuPG v1.4.9 (GNU/Linux)


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index