Compatibility with the MS Office 2007 new file format OOXML (docx, xslx, pptx, ppsx) is a frequent issue. Here are some links to articles about the nature of Office Open XML.Note: if you find broken links, please report them so that we update them. Sites sometimes change their address causing this kind of trouble.

What is called OOXML?The OOXML can be misleading because at the beginning, it could also aply to the OpenOffice XML developed by the OASIS. It has then been renamed to ODF (Open Document Format [for Office Applications]). For more information about ODF and OASIS, see: https://www.oasis-open.org/org and https://www.oasis-open.org/committees/t ... rev=officeNow (and especially in this topic), OOXML stands for the Microsoft file format Office Open XML.Additional resources:

The OOXML (Office OpenXML) container is a ZIP style archive, just like ODF - so in an emergency you can access most text content that way, without needing to install or download anything at all. Just rename the file to end with .ZIP

The converter is done by Novell and their build is slightly different from the Sun's version. They don't have the same position on development of OOo (even if we can't say there is any fork), that's why the Novell build has often more features than the Sun's version.

I had a look at the thread and opened quite a lot of links. I also had a look at the odf-converter-integrator for docx/xlsx/pptx. However, it supports only Windows and Linux...

I am using Mac OS X Version 10.5.6 and I would really need to convert these stupied MS Office 2007 documents (docx, xslx, pptx, ppsx).Is there anything, an extension or whatever that I could download for Mac OS X to open these documents.

If you ask me, OOo is unable to open MS Office xml documents of certain size (several megabytes of XML code, which means 40+ pages) - Office just hangs of throw an exception that document is broken.Knowing that the document only contains simple formatting (easily opened after re-saving in binary format), I think it's about perfect indication, that MS does not comply with their own standards.

where Jeremy Allison (@Google) complains about OOXML mainly because of 2 technical reasons:

Google wrote:No useful guide to specification. Although it has made the specification available, Microsoft has madeit impossible to find the relevant information swiftly as the specification is over 6,000 pages long.

Google wrote:Continued use of binary code. In addition, the specification continues to use binary code although thesignificant advantage of XML is that it is generally text based and therefore humanly readable.[...]In addition, many of these binary sections refer back to the Windows architecture which is unknown tosoftware engineers outside Microsoft, ...

IMHO, the main conclusion on the technical side of the problem is this:

Although OOXML may formally comply with Ecma, it was clearly not designed with an “open” spirit.Comparing the current with the future situation, interoperability is likely to become more difficultinstead of easier. The implementation of a fully compatible ODF importer (the current efforts regarding.doc and .xls) is not an easy task, but it is dwarfed by the implementation of a fully compatibleOOXML importer, which we estimate to take something between 50 – 500 person years, or evenlonger. Therefore, although it is theoretically possible to generate an OOXML document, this documentwill probably only use a very small subset of the standard.

Then he states the judicial implications of what MS refers to as “Open Specification Promise”.

Hundreds of man years for an acceptable import filter (leaving aside any export filter) and no guarantee (just a promise) that you won't be sued by MS or even third parties!

Please, edit this topic's initial post and add "[Solved]" to the subject line if your problem has been solved.Ubuntu 18.04, OpenOffice 4.x & LibreOffice 6.x

See textbox.docx which has a Microsoft Textbox containing some (Latin lorem ipsum ...) text in it. Nothing is visible in AOO (though all is visible in LO as LO supports Microsoft Textboxes).

I extracted document.xml from the .docx file. The file, when pretty printed as below, is 143 lines long. From what I understand, everything between the start tag <mc:AlternateContent> on line 16, and its matching end tag </mc:AlternateContent> on line 130, 13 lines from the end, is outside the OOXML Specification, so not visible in AOO. So much for Microsoft's using its own standards.