Via Slashdot… Behold…the Open Document Format that Microsoft Rammed through the international standards committee…<\/p>\n
\nOffice 2007SP2 ODF Interoperability Very Bad<\/a><\/h3>\n
\t \t\tPosted \t\tby \t \t \t\t \t\t\tCmdrTaco<\/a><\/strong>
\nfrom the are-you-really-surprised<\/strong> dept.<\/strong><\/div>\n<\/div>\n\t\t\t\t\t\t\t\t\t \t\t \t\t\t \t\t\t \t\t\t \t\t \t<\/a> \t\t\t\t\t\t\t\t<\/span><\/p>\nDavid Gerard<\/a> writes "Microsoft Office 2007 SP2 claims support for ODF 1.1. With hard work and careful thinking, they have successfully achieved technical compliance but zero interoperability<\/a>! MSO 2007sp2 won’t read ODF 1.1 from any other existing application, and its ODF is only readable by the CleverAge plugin. The post goes into detail as to how it manages this so thoroughly."<\/em><\/div>\n<\/div>\n<\/blockquote>\nODF: The open standard file format that only Microsoft applications can use…<\/p>\n
[Update…]<\/em> In comments Jonathan Allen points out that ODF is the Oasis Group open document standard, not Microsoft’s, which is OpenXML. I was confusing the two, and the point of the Slashdot post. This isn’t about Microsoft’s own proprietary open standard. It’s about them applying their usual Embrace, Extend and Extinguish tactic on ODF. Here’s some of the Slashdot commentary…<\/p>\n
\n\nIf it achieves 100% technical compliance with the standard, but zero interoperability, this is certainly a problem with the standard itself.\n<\/p>\n
And the problem in this case is the missing formula specification. It’s not in ODF 1.1, and ODF 1.2 is still a draft. While this is Microsoft and we all "know" that this was intentional, ODF is what should be fixed first. We were all bashing OOXML specifications, but ODF 1.1’s far from perfect, as we can see.<\/p>\n<\/div>\n
…\n<\/p>\n
That is, curiously, not quite true. ODF 1.1 doesn’t fully specify formulas, but it does specify the general syntax that should be used for them, and Microsoft seems to have ignored this. (Also, in practice, the major spreadsheets are quite similar in terms of what expressions they accept in formulas. This makes it relatively simple to convert between MS Office formulas and OpenOffice.org ones, which are what most ODF-based apps use.)<\/p>\n
…<\/p>\n
The irony here is that the formula language used by OpenOffice (and by other vendors) is based on that used by Excel, which itself was not fully documented when OpenOffice implemented it. So an argument, by Microsoft, not to support that language because it is not documented is rather hypocritical. Excel supports 1-2-3 files and formulas and legacy Excel versions (back to Excel 4.0) neither of which have standardized formula languages. Why are these supported? Also, the fact that the Microsoft\/CleverAge add-in correctly reads and writes the legacy ODF formula syntax shows not only that it can be done, but that Microsoft already has the code to do it. The inexplicably thing is why that code never made it into Excel 2007 SP2.<\/p>\n<\/blockquote>\n
Just look at this. They’re in complete technical compliance, and yet if you read an ODF file format spreadsheet into Excel and then write it back out again it’s now locked utterly into MS Office’s specific implementation of ODF. You can no longer read it back into any other spreadsheet program that supports ODF, because it can’t read Microsoft’s ODF formula implementation.\n<\/p>\n
They just never stop, do they? I started out as a Microsoft platforms developer. Now I work on software that runs on many different platforms and swear to God I will never again be a Microsoft only developer. I will not help them betray the promise of the personal computer. I will not help them put handcuffs on the whole goddamned world just because that’s their business model.<\/p>\n","protected":false},"excerpt":{"rendered":"
Via Slashdot… Behold…the Open Document Format that Microsoft Rammed through the international standards committee… Office 2007SP2 ODF Interoperability Very Bad Posted by CmdrTaco from the are-you-really-surprised dept. David Gerard writes "Microsoft Office 2007 SP2 claims support for ODF 1.1. With hard work and careful thinking, they have successfully achieved technical compliance but zero interoperability! […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[108,102,45,86],"class_list":["post-3689","post","type-post","status-publish","format-standard","hentry","category-politics","tag-department-of-unsurprising-things","tag-the-corporate-teat","tag-the-criminal-mind","tag-the-redmond-follies"],"_links":{"self":[{"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/posts\/3689","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/comments?post=3689"}],"version-history":[{"count":0,"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/posts\/3689\/revisions"}],"wp:attachment":[{"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/media?parent=3689"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/categories?post=3689"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/brucegarrett.com\/brucelog\/wp-json\/wp\/v2\/tags?post=3689"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}