[pieceofpeace]

That is not the point the Google spokesperson was trying to make.

The full quote: "It says a lot about Microsoft's approach to customer lock-in that the company touts its proprietary document formats, which only Microsoft software can render with true fidelity, as the reason to avoid using other products".

So they were complaining about MS making it hard to decode the Word format and making it tough to preserve format when importing.

[endtime]

.docx isn't hard to decode. ;) Though it is hard to render across browsers.

[blasdel]

OOXML is no easier to decode than the old memory-dump and COM-based DOC formats which were comprehensively documented first by third parties and then Microsoft. It's just like how SWF was trivial to decode long before it was 'opened'. Container formats are fucking easy.

What's always been insanely difficult is duplicating the API that the content interfaces with, bug for bug.

[nailer]

As someone who writes an Open Source OpenXML decoder I find it way easier than COM. The OpenXML specification docs are comprehensive, when there's a problem - usually detected by OpenOffice's parser as Word is very forgiving - the specs have a specific answer.

There's good development tools including a Firebox style Xpath app for Word too.

The main issue is MS Office 2007 and 2010 generating the legacy OpenXML formats by default, which include a world of possible features including quite a few from Lotus 123. There's too many edge cases to handle, and this isn't the right format for docs made this year.

[blasdel]

'decode' was probably the wrong word to use there — how about 'consume'?