void life(void)

As they did in the past with Java and HTML (just to cite two cases), Microsoft has now invested at least 12 months of work to try to fragment the ODF in the IT market: A shame.I swear I was ready to publish this week a post praising Microsoft for finally released SP2 of Office 2007 with native support for ODF, but unfortunately after the initial tests of various users, what we see is an absurd attempt to mislead consumers (who payed for the software) and fragment ODF in the IT industry.

When I use the word fragment, I mean the known tactic of using ‘creativity’ during the implementation of a standard to make the implementation only compatible with your software (people that had seen sites that only work in Internet Explorer already know what I’m talking about). Looking from outside, the documents appear identical but a most consistent inside look demonstrate that they are completely different, thus fragmenting the uniformity expected as a consequence of a standard adoption.

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.

When using Office 2007 to generate a new worksheet, the formulas will be stored in a way that only will be understood by Office 2007 (or by CleverAge, an MS Office plug-in to support ODF, developed as Open Source and sponsored by Microsoft), eliminating the possibility that any other existing application could be used to usefully read the document.

While the first problem simply throw out all the business intelligence inside the spreadsheet (formulas), the second locks in the user on Office 2007 forever (we have seen this movie before…).

The justification that could be used by Microsoft about it, is the lack of spreadsheet formula definition in ODF 1.0/1.1. Interesting to note that in ODF 1.2 (which is developed with the participation of Microsoft) this problem has been resolved with the creation of OpenFormula).

The first comparative table of Rob’s post, summarizes a test on the same subject that he did a few weeks ago, it is easy to see that even without any spreadsheet formula definition inside ODF 1.1, interoperability between the tested set of existing applications ( KOffice, OpenOffice, Google Docs, Symphony and Sun’s plug-in for Office) really exists on the real world (except for CleverAge that presented some problems). This means that all other developers are not concerned only to ‘comply with standard’s requirements’ (conformance) but also in developing a truly useful and interoperable application to users. Rob also says that the set of formulas used by these applications (based on OpenOffice) was developed based on existing formulas from Excel (at least ironic, huh?).

I also highlight that the problems presented on OpenOffice when Rob repeated his tests with the new version of the suite, were caused because the developers of OpenOffice 3.0 decided to incorporate ODF 1.2 as default. ODF 1.2 still under development in OASIS. No question about what led to this decision, but I’ve orientated all users of OpenOffice 3.0 that I know, to change the configuration of the office suite to use ODF 1.0/1.1 as the default file format (in the Options menu of OpenOffice, there is a group called “load / save” where it can be done). I admire the efforts of OpenOffice’s developers to incorporate the ODF 1.2 to their software, but I think it should have been placed as an additional feature, not as its default format (I’m using OpenOffice 3.0.1 configured to work with ODF 1.0/1.1 and I’ve had no interoperability problems at all).

I also enjoyed to see the comments that PJ (Groklaw) (I think it was PJ) made about MSOffice SP2. PJ isn’t a developer and therefore created a simple text document and find absurd results too.

PJ also wrote something very interesting, and I agree 100%:

“…Dear Microsoft, could you please do something about this? It’s just code, which means it can be fixed. But your code is proprietary, so we can’t fix it. Only you can. Like the old song says, could you please put on some speed? Others like Google Docs seem to be able to do ODF spreadsheets. Why can’t you? No doubt there will be improvements, but when?…”

As I don’t have a computer with Windows and I don’t have MS Office 2007 to test, I did some tests with SP2 trough the exchange documents with friends who have Office 2007 with SP2 installed and here are my 2 cents for all the tests that are appearing (and being published every second on the Internet):

Microsoft Office 2007 does not support encryption (password protection) in ODF documents !

I generated a simple text document (.odt) in ODF using OpenOffice and saved it with password protection. I sent the document (and password) to several friends and the result was the same: MS Office cannot open the document because it is password protected (some of those friends also have installed on their computers other tools that support ODF and on 100% of those tools it worked).

I also asked them to generate a document in Office 2007 with password protection and send me, but they said that when trying to do this, MSOffice presented a warning message saying that you cannot use password protection using the ODF format.

I would really like to find a good technical explanation for this, since the encryption and password protection are fully specified in ODF 1.0/1.1 (item 17.3 of the specification), and they are using existing algorithms, very familiar to any developer.

A comment from Rob in his post (that not dealt with the encryption) is able to comment with mastery the problem I found (and I fully agree with him):

“…I was taught to never assume malice where incompetence would be the simpler explanation. But the degree of incompetence needed to explain SP2’s poor ODF support boggles the mind and leads me to further uncharitable thoughts… ”

It is impressive to see how Microsoft constantly shows disrespect for their customers, partners and the market in general and it is also impressive to see this clearly demonstration of their complete inability to change.

If anyone have more texts about ODF problems found on Service Pack 2, please put the links on the comments (we can use this post as a source for research about those problems).

Here is my recommendation: Don’t use Office 2007 with Service Pack 2 for manipulating ODF documents. If your decision is still using MS Office, install the Sun’s plug-in, but I really recommend that you search for another solution that natively support ODF documents. Don’t loose time (and money) with those who disrespect you.

For people who wants to follow the news about ODF in the world, I recommend a daily visit to Planet ODF (it indexes everything).


27 Responses to “Microsoft now attempt to fragment ODF”

  1. Charles

    Good points Jomar. Here’s a follow-up of your blog:

  2. kjs

    and why are you surprised that they implemented ODF so badly? The only surprise to me would have been if it would have worked well……..

  3. SPM

    The only way to deal with this is to file an anti-trust action to force royalty free full access to MS Office hooks, APIs, protocols, and formats, in order to allow third parties to write compatible import/export filters (similar to the EU deal on SMB protocol), and to force Microsoft to release these a year ahead of release of any new Office version, in order to allow these to be released on time. It is also necessary to allow users remove the Microsoft plugins and for OEMs to remove and ship MS Office with third party plug-ins instead, and for users to be able to set ODF as the default save filter format.

    It is clear that Microsoft will not provide a compatible ODF filter for interoperability, and therefore others will need to be allowed to do this for the sake of interoperability and fair and free competition.

  4. uqbar

    Good article. I visit your blog frequently and appreciate the work you are doing.

    So I have to say this, with the best of intentions: Your white text on black background is nearly unreadable - I always have to run off page styles to be able to view your web pages.

  5. orcmid

    Jomar, I respectfully disagree with you about 17.3 (http://wiki.oasis-open.org/oic/SpecAnalysis/1.1/17/17.3). As far as I can tell, there is insufficient information to implement ODF Package Encryption without looking at the OpenOffice.org implementation. There is no way to know what the tricks are from the specification.

    Note that the sample manifest (http://wiki.oasis-open.org/oic/SpecAnalysis/1.1/17/17.7/sample) doesn’t even honor the schema, omitting the required checksum and checksum name attribute values for password hashes. Also, actually putting the checksum in the file — as OO.o does — appears to be a security exposure if implemented the way 17.3 and 17.7.4-17.7.6 read (http://wiki.oasis-open.org/oic/SpecAnalysis/1.1/17/17.7/17.7.4), but that is a longer story and apparently not exactly what OO.o does anyhow.)

  6. VS Dude

    It’s “paid” not “payed.”

  7. Open Formats, God Damn It « DoctorMO’s Blag

    […] Formats, God Damn It In this article Rob Weir notes the difficulty in getting the new Microsoft Office 2007 SP2 to integrate with ODF […]

  8. jspitanga

    @VS Dude
    According to reliable dictionaries, both “paid” and “payed” may be correct, depending on the context.
    However, Microsoft Word 2007 dictionary does not recognise “payed” as a proper word and indicates it is misspelled.
    This shows how unreliable are Microsoft products.

  9. Microsoft Fragments ODF While Trying to Paint it as “IBM Thing” | Boycott Novell

    […] recent attempts to hijack ODF [1, 2] and one of the representatives from Brazil now claims that “Microsoft attempts to fragment ODF.” One of the first articles published about SP2 and for which I call the attention of everyone is […]

  10. Daeng Bo

    I’ve been crowing about this since December now.[1] MS implemented ODF completely differently than other, already completed implementations. It does appear to have been a conscious choice.

    Nobody has wanted to listen yet.

    [1]http://blog.ibeentoubuntu.com/2008/12/microsofts-odf-plans-business-as-usual.html — link to my own blog.

  11. jorgejhms's status on Friday, 08-May-09 14:37:25 UTC - Identi.ca

    […] soporte de odf en office es intento para dividir a usuarios http://homembit.com/2009/05/microsoft-now-attempt-to-fragment-odf.html […]

  12. popurls.com // popular today

    popurls.com // popular today…

    story has entered the popular today section on popurls.com…

  13. sam

    emailed the article to a few big names at M$… mebbie we’ll get this fixed.

  14. dsdsg

    Tip: White text on black background is NOT comfortable

  15. urbanus


  16. sam

    just got an email back from M$, they say they’re “looking into it” might check back in a future update and see if stuff is fixed.

  17. OpenSource și Guvernul | Emil CHERICHEȘ - passionate linux sysadmin

    […] invers. Își dezvoltă propriile standarde, își dezvoltă propriile aplicații pe care mai apoi încearcă să le impună, binențeles contra unei sume de […]

  18. Răzvan


    I’ve tried to inform the Romanian-speaking readers about this mattter - please see here:



  19. Floschi’s Blog» Blogarchiv » Link collection about Microsoft’s fail to ODF in SP2

    […] Jomar Silva: Microsoft now attempt to fragment ODF […]

  20. Matt

    This goes deeper than you think.

    Other problems :When I go from .XLS -> open in open office -> save in XLS again, and open in office 2003, the spreadsheets lose all data (not just formulas) as well.

  21. Difficile de supporter Microsoft quand il supporte ainsi l’ODF | Dico Micro

    […] de plus amples lectures : voir Maintenant Microsoft essaie de fragmenter ODF, par Jomar Silva/ODF […]

  22. Difficile de supporter Microsoft quand il supporte ainsi l’ODF | Encher.net

    […] de plus amples lectures, voir Maintenant Microsoft essaie de fragmenter ODF, par Jomar Silva/ODF […]

  23. [MS ColdPlot] « tagesuhu

    […] Não, não é paranóia, não, não é teoria da conspiração. Se a M$ tivesse realmente interesse em contribuir com a comunidade, o passo mais óbvio seria fazer o que todos os que querem contribuir fazem: dão suporte, financeiro, técnico ou ideológico a uma comunidade já organizada. Quisesse a M$ colaborar com a comunidade, o passo mais óbvio seria que tivesse alocado o capital na Free Software Foundation, na Open Source Alliance, no Gnome, no Debian, na Linux Foundation, etc. Tivesse em mente uma vontade de mudança, adotaria para seus softwares as licenças GNU, BSD ou outra aprovada pela OSI ou pela FSF, não criaria seu próprio rol de “licenças livres M$”, lançando apenas alguns códigos com estas licenças e mantendo fechados seus softwares e exigindo a anuência dos usuários com seus EULAs. Quisesse favorecer o software livre, teria contribuído com o Wine para que os softwares Windows rodassem facilmente nos kernels Linux, ao invés de lançar linhas de código no kernel para garantir que o Windows funcione bem quando virtualizado nele. Fosse favorável à liberdade, contribuiria para a adoção do ODF e sua interoperabilidade com o seu pacote Office, ao invés de lançar seu próprio formato livre e boicotar as funções dos arquivos criados pelo OpenOffice quando transpostos para o MSOffice. […]

  24. Родион Абдулов

    Вот это да… После прочтения даже мне тема стала интересна.

  25. Samsung un46d6000

    Do you mind if I quote a couple of your posts as long as I provide credit and sources back to your weblog? My blog site is in the very same area of interest as yours and my visitors would really benefit from a lot of the information you provide here. Please let me know if this alright with you. Thank you!

  26. LjRfcovz

    [url=http://www.lebron-xi.com/]Lebron x[/url] basketball shoes - Christmas color rendering motionless opt red color, more inclination be SWOOSH marks, shoelaces, utterance and the appear country-like spoil on the outsole outline counter was notably evident, ruby pattern and the privy of the shoe firmness with a stock Christmas knitting as cv, the overall design appropriate for LEBRON LEBRON basketball shoes like X display hanging in the vivid red lights on the Christmas tree.
    Every year seems to arrange become a Christmas LEBRON fans and [url=http://www.jordan11release2013.com/]jordan 11 2013[/url] fans the most nave on hour, this year, NIKE expectations in requital for everybody introduced again loud of color and atmosphere of Christmas LEBRON X LEBRON basketball shoes, red pitch and excellent harmonic, with just the propitious amount of unversed beautify fetish, more resolution be the theme of the ruby is precise deduce.
    Unconsciously, lebron’s friendship with NIKE heads. 10 years, both the uttermost brilliance or frustrated blink, [url=http://www.lebron-xi.com/]2013 Nike shoes[/url] fervour of basketball has in no way changed; Now, he finally stood at the zenith of the basketball dialect birth b deliver, LEBRON X LEBRON basketball shoes with a NIKE basketball shoe designers experience, cutting-edge technology and chief to stalwart consummate act as a service to his brobdingnagian and extraordinary depiction of a legend.

  27. Donnell

    Pretty! This was an incredibly wonderful post. Many thanks for
    providing these details.

Deixe seu comentário

Proudly powered by WordPress. Theme developed with WordPress Theme Generator.
Creative Commons License