OOXML — The Apple Headache


Up here in Norway, representatives from Microsoft keeps running around spreading the word that OOXML is implemented in several applications, among them several Apple products — or products for the Mac OS X platform — such as iWork ‘08, iPhone and NeoOffice. As an Apple user, I have an iWork ‘08 license, I have an iPhone and I use NeoOffice as my primary office suite. Therefore, I would like to test the allegations.

First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not OOXML (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, DRM and SharePoint metadata. Even the paper handling does not conform with Ecma 376. The documents produced by Microsoft Office 2007 goes by the name of MSOOXML, but in this article I will call it OOXML. However, this is not the point of this article. My point is to see if the document implementation in either iWork ‘08, iPhone or NeoOffice is usable in other applications.

Who can produce an OOXML document?

If we turn to the Apple website, Apple says the following on Pages ‘08 and compatibility:

Import your Microsoft Word documents into Pages ’08 with ease. Whether they’re Microsoft Office 2007 (Office Open XML) or earlier Word files, Pages will open them.

Great, I can open OOXML documents. But what if I have to make changes in the document, and return it to the sender? Saving documents as OOXML is not supported in any of the iWork ‘08 products. This is the list of supported document types:

Pages

  • Apple’s own format (.pages)
  • Older iWork versions
  • PDF
  • DOC (the old binary format)
  • RTF
  • Plain text

Numbers

  • Apple’s own format (.numbers)
  • PDF
  • XLS (the old binary format)
  • CSV

Keynote

  • Apple’s own format (.key)
  • Older iWork versions
  • QuickTime
  • PPT (the old binary format)
  • PDF
  • Pictures
  • Flash
  • HTML
  • iPod

Based on this list, I’m stuck for now. It’s not possible to create OOXML documents with iWork ‘08. What about NeoOffice? Will NeoOffice be able to create OOXML compatible documents?

A simple test document

First, I need to create an OOXML document, with the file extension .docx. With NeoOffice, I’ve produced a very simple document, containing some text and a picture.

OOXML test document created with NeoOffice

I save the document as «Microsoft Word 2007 Document (.docx)». Just to make sure, I save the document as ODF and OOXML.

In Mac OS X

As soon as the document is saved, I find it in Finder, the Mac OS X equivalent to Windows Explorer. I find both the ODF and the OOXML version:

OOXML and ODF in Finder

As you can see, OOXML is apparently not fully implemented in Mac OS X. Finder has a preview of the content of known file types, but it does not show the content of the OOXML file, like it does with ODF. The ODF document has the file extension .odt. Mac OS X also has functionality called Quick Look to preview the whole file without opening it. However, that does not work either:

OOXML in Quick Look

To compare it, the ODF file looks like this:

ODF in Quick Look

In Mac OS X applications

OK, we’ve sorted out that OOXML documents is not implemented in Mac OS X, apparently. What about other applications? By double clicking the OOXML document, Mac OS X will open the file in TextEdit, an advanced equivalent of Windows’ Notepad. This is what the document will look like in TextEdit:

OOXML in TextEdit

I would like to claim that the implementation of OOXML in TextEdit is so defective that it is useless. Furthermore, I do not know anyone that uses TextEdit for word processing.

In iWork ‘08

What happens if I open the document with my iWork ‘08 application, Pages? Here’s the answer:

OOXML in Pages

On the iPhone

What about the iPhone? Will it open my OOXML document? I send it by e-mail, where it appears in the inbox:

OOXML on the iPhone

I open the e-mail and find the document attached:

OOXML on the iPhone

Finally, I try to open the document. This is what happens:

OOXML on the iPhone

Clearly, iPhone is not able to open the OOXML document. I’d like to point out that the document is not password protected.

Conclusion

I do not own a license for Microsoft Office 2008 for Mac, and I will not buy one either. It might be possible to open documents produced by Microsoft Office 2008 for Mac with iWork ‘08, iPhone or NeoOffice, but that is irrelevant. One of the major points with interoperability, is vendor independence. If I have to buy a license for Microsoft Office 2008 for Mac, Microsoft has succeeded in creating a standard so difficult — not to say impossible — to implement, that users will have to buy Microsoft’s software.

As a final statement, I would like to point out that the allegations on OOXML beeing implemented in iWork ‘08, iPhone and NeoOffice are wrong.

Information and Links

Join the fray by commenting, tracking what others have to say, or linking to it from your blog.


Other Posts
Implementing ODF
Norway’s official press release on OOXML

Write a Comment

Take a moment to comment and tell us what you think. Some basic HTML is allowed for formatting.

Reader Comments

I don’t know what version of the software you are running on your iPhone, but since you are in Europe it is a safe bet to say that it is probably not yet 1.1.3, because when I send myself an e-mail with an OOXML attachment, such as a .DOCX file, I can indeed view that attachment on the iPhone without any problems.
It works pretty much exactly as depicted in this YouTube video: http://youtube.com/watch?v=oNcAjS7LqKM

Are there anything in the 1.1.3 changelog that indicates improved OOXML support? I have not checked, but I doubt it.

As I say in my conclusion, it might be possible to open documents created with either Microsoft Office 2007 or Microsoft Office 2008 for Mac. However, this is rather irrelevant, as my point is to point out that the allegations of OOXML implementation in NeoOffice, iPhone and iWork ‘08 are wrong. If I have to own a license for Microsoft Office, the whole idea of vendor independence is useless.

Type your comment here.

As you are well aware of, NeoOffice states that the support for OOXML is experimental. It’s a bit hasty to draw the conclusions based on experimental support IMHO.

Having trouble with the comment system, Fredrik? ;-)

Anyway, we’ve had this discussion in my Norwegian weblog allready. As I said, at the moment it is not possible to use the so called implementations without having a license for Microsoft Office 2007 or 2008 for Mac. Probably.

[…] Microsoft is striding all over the place (even spamming YouTube) to give people the illusion that OOXML makes not just a representation of a single product from a single vendor. Actual users are not buying it (neither the argument nor Microsoft’s products) and it shows. First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not OOXML (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, DRM and SharePoint metadata. […]

[…] And finally, and rather amusingly, Martin Bekkelund; has done some testing of Microsoft’s claims that OOXML works on several Apple products. Unfortunately it appears as thought they have been somewhat “economical with the truth” [Surely not! Microsoft?]… […]

“First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not OOXML (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, DRM and SharePoint metadata. Even the paper handling does not conform with Ecma 376.”

I think you have to be careful about these statements. Both ODF and OOXML allow for use of binary content and for additional/alternative content in some cases. The only specific example I have found so far was baseless, in that the behavior of Office 2007 was specifically allowed in ECMA-376. (ODF also supports OLE enclosures, by the way.)

What needs to be looked at is how ECMA-376 provides for carrying of alternative content that may be useful in roundtripping back to older formats and how it is also easy to create conforming documents that make no reliance on such cases.

With regard to the quality of implementations on Apple and the fact that Finder preview support has never been claimed, and other usability matters, I think your experimentation is very valuable, especially with regard to the important ability to round-trip with either one of OOXML or ODF among products that claim to support one or the other.

Could you enlighten us what kind of format your embedded picture file actually is ?
Because it seems that a sample file I made that is very similar to your file is picked up fine by the iPhone of my friend.
Or better even give your readers a downloadable link to your sample files.

Sorry for my late answer.

The files are available right here:

http://filer.bekkelund.net/dokumenter/neooffice.docx
http://filer.bekkelund.net/dokumenter/neooffice.odt
http://filer.bekkelund.net/dokumenter/neooffice.xlsx
http://filer.bekkelund.net/dokumenter/neooffice2.xlsx

And for what ODF concerns, it is not ODF that is up for ISO certification. ODF is already ISO certified and selected as the mandatory document standard for the public sector in Norway. Therefore, discussing ODF is uninteresting in this setting.