New Leopard Build Supports Office 2007 Formats – Office:mac coming 6-8 months later

The folks over at MacShrine are reporting that Apple has seeded a new build of Leopard (Mac OS 10.5) internally. What really caught my eye was the last statement:

“TextEdit also features support to export and open new Word 2007 documents”

What’s interesting here is that there is no mention of the OpenDocument format supported by the OpenOffice suite. Oh well. (UPDATE: it would appear that OpenDocument is supported as well according to this post at Uneasy Silence). However, if TextEdit can read and write OpenXML documents and Leopard ships within the first half of 2007, Apple will be supporting the new Office format before Microsoft. I still fully expect that the next version of iWork will support the Office OpenXML (now ECMA-376) and OpenDocument file formats in its next release, which probably will be announced at MacWorld 2007.

But what I find even more interesting are the recent claims put out by Microsoft’s Mac BU who say they will have Office 2007 converters ready by Spring and that Office:mac 2007 will ship 6 to 8 months after the Windows version. What I find difficult to understand is why it’ll take so long? For starters, they all work at the same company that also happens to make the Windows version of Office 2007. Second, this is the same company that drafted the Office OpenXML format, so you’d think there’d be few folks with expert knowledge on the subject. And finally, this new format is now an EMCA standard, of which anyone who can read a spec could implement the format. And even though the spec only became a standard on 12/7/2006, the spec had been published well in advance.

It blows my mind that a group of folks who work at the same company, can’t get it together with other internal teams to make compatibility with the new file format a top priority. After reading some of the Mac Mojo post, it sounds like they even wrote their own XML parser to read the format. Why? I guess this gives some insight was to why Vista was a few years late.

It’ll be interesting to see what Apple has in store for iWork in 2007. My gut is starting to say that this is the beginning of the end for Office:mac. This could be Microsoft giving Apple a head start into the office market on the Mac. Eventually, Office:mac will be cede to iWork much in the same was as Internet Explorer did to Safari, even while Safari was a beta. The good thing is that with the Office OpenXML format, we now have an established standard so file incompatibilities should not be as problematic as they have been in the past.

Update #2: It appears I’m not the only who thinks that Office:mac is on its way out; Rob Griffiths of MacOSXHints.com has a piece over at MacWorld.com which points out that Office:mac will not have VB support for things like macros and other goodies. Of interest, the folks over at OpenOffice.org are working on VBA support. It’ll be interesting to see if Apple is able to leverage any of that code base.

Advertisements

4 thoughts on “New Leopard Build Supports Office 2007 Formats – Office:mac coming 6-8 months later

  1. Yes, I did say: “And finally, this new format is now an EMCA standard, of which anyone who can read a spec could implement the format. And even though the spec only became a standard on 12/7/2006, the spec had been published well in advance.”

    And my point was that Apple has apparently implemented support for both OpenDocument and Office Open XML formats in the latest builds of Leopard. It doesn’t matter if I have implemented a spec or not, nor weather or not ECMA-376 was rushed or not, Microsoft authored the spec. One would assume that they would have some deeper knowledge of the format than anyone else. Hell, Office 2007 seems to support it.

    My point is that it speaks volumes to Microsoft’s commitment to Office:mac if they can’t have access to the internal resources to get a file format converter out until late spring. Apple seems to have the resources to do this. It’s mind boggling that MS cannot.

    Like

  2. Yes, I did say: “And finally, this new format is now an EMCA standard, of which anyone who can read a spec could implement the format. And even though the spec only became a standard on 12/7/2006, the spec had been published well in advance.”

    And my point was that Apple has apparently implemented support for both OpenDocument and Office Open XML formats in the latest builds of Leopard. It doesn’t matter if I have implemented a spec or not, nor weather or not ECMA-376 was rushed or not, Microsoft authored the spec. One would assume that they would have some deeper knowledge of the format than anyone else. Hell, Office 2007 seems to support it.

    My point is that it speaks volumes to Microsoft’s commitment to Office:mac if they can’t have access to the internal resources to get a file format converter out until late spring. Apple seems to have the resources to do this. It’s mind boggling that MS cannot.

    Like

  3. You say “And finally, this new format is now an EMCA standard, of which anyone who can read a spec could implement the format. And even though the spec only became a standard on 12/7/2006, the spec had been published well in advance.”

    Have you ever tried to build a software to a spec? May be you should read up on that spec for ECMA-376. It was rushed through the ECMA committee like bills in the US congress with no real time to read the thing. This spec also compares binary formats that are proprietary and so is lots of this format in general, especially the backward compatibility measures.

    Compare this to ODF, also known as ISO 26300, which builds on lots of other specs and therefore can be implemented using existing building blocks. It also uses established specs for example to set formulas instead of reinventing the wheel.

    If you think reading a spec and implementing it in a software that is in any way or shape competitive is easy, then you better try to do so. By the way the ODF converter add-ons for MS Office are open source projects, sign up and grind your teeth on reading two specs and implement a conversion between them. Show us how easy it is!

    Like

  4. You say “And finally, this new format is now an EMCA standard, of which anyone who can read a spec could implement the format. And even though the spec only became a standard on 12/7/2006, the spec had been published well in advance.”

    Have you ever tried to build a software to a spec? May be you should read up on that spec for ECMA-376. It was rushed through the ECMA committee like bills in the US congress with no real time to read the thing. This spec also compares binary formats that are proprietary and so is lots of this format in general, especially the backward compatibility measures.

    Compare this to ODF, also known as ISO 26300, which builds on lots of other specs and therefore can be implemented using existing building blocks. It also uses established specs for example to set formulas instead of reinventing the wheel.

    If you think reading a spec and implementing it in a software that is in any way or shape competitive is easy, then you better try to do so. By the way the ODF converter add-ons for MS Office are open source projects, sign up and grind your teeth on reading two specs and implement a conversion between them. Show us how easy it is!

    Like

Comments are closed.