Hi,I keep getting this message when trying to open a word. It told me 'Unable to open Open XML file pdge.docx. Problems were detected in the content, or the file name may contain invalid character (for example, /). Details: Can not open file. The file is corrupt.' But i can open it on another mac, same office. Second, as Zeyad mentioned, it seems to me that at least the package.rels-file and document.xml-file are ANSI. I don't know how Word handles these files but i experienced that it is very forgiving in respect of invalid documents (not so the productivity tool or packageexplorer - both indicate invalid documents!).
Filename extension | .XML (XML document) |
---|---|
Developed by | Microsoft |
Type of format | Document file format |
Extended from | XML, DOC |
Filename extension | .VDX (XML Drawing),.VSX (XML Stencil),.VTX (XML Template) |
---|---|
Developed by | Microsoft |
Type of format | |
Extended from | XML, VSD, VSS, VST |
Filename extension | .XML (XML Spreadsheet) |
---|---|
Developed by | Microsoft |
Type of format | Spreadsheet |
Extended from | XML, XLS |
The Microsoft Office XML formats are XML-based document formats (or XML schemas) introduced in versions of Microsoft Office prior to Office 2007. Microsoft Office XP introduced a new XML format for storing Excel spreadsheets and Office 2003 added an XML-based format for Word documents.
These formats were succeeded by Office Open XML (ECMA-376) in Microsoft Office 2007.
Besides differences in the schema, there are several other differences between the earlier Office XML schema formats and Office Open XML.
Specifies the Word Extensions to the Office Open XML FileFormat, which includes elements and attributes that extend the XML vocabularyfor representing word processing documents as presented in the ISO/IEC-29500specification.
This page and associated content may beupdated frequently. We recommend you subscribe to the RSSfeed to receive update notifications.
Date | Protocol Revision | Revision Class | Downloads |
---|---|---|---|
3/22/2021 | 15.0 | Major | PDF | DOCX |
Date | Protocol Revision | Revision Class | Downloads |
---|---|---|---|
2/16/2021 | 14.1 | Minor | PDF | DOCX |
8/18/2020 | 14.0 | Major | PDF | DOCX |
2/19/2020 | 13.0 | Major | PDF | DOCX |
11/19/2019 | 12.1 | Minor | PDF | DOCX |
9/24/2019 | 12.0 | Major | PDF | DOCX |
3/19/2019 | 11.1 | None | PDF | DOCX |
12/11/2018 | 11.1 | Minor | PDF | DOCX |
8/28/2018 | 11.0 | Major | PDF | DOCX |
4/27/2018 | 10.0 | Major | PDF | DOCX |
12/12/2017 | 9.1 | Minor | PDF | DOCX |
9/5/2017 | 9.0 | Major | PDF | DOCX |
12/15/2016 | 8.0 | Major | PDF | DOCX |
9/22/2016 | 7.0 | Major | PDF | DOCX |
7/15/2016 | 6.1 | Minor | PDF | DOCX |
9/4/2015 | 6.0 | Major | PDF | DOCX |
3/16/2015 | 5.0 | Major | PDF | DOCX |
10/30/2014 | 4.1 | None | PDF | DOCX |
7/31/2014 | 4.1 | Minor | PDF | DOCX |
4/30/2014 | 4.0 | Major | PDF | DOCX |
2/10/2014 | 3.2 | Minor | PDF | DOCX |
11/18/2013 | 3.1 | Minor | PDF | DOCX |
7/30/2013 | 3.0 | None | PDF | DOCX |
2/11/2013 | 3.0 | None | PDF | DOCX |
10/8/2012 | 3.0 | None | |
7/16/2012 | 3.0 | Major | |
4/11/2012 | 2.0 | None | |
1/20/2012 | 2.0 | Major | |
6/10/2011 | 1.05 | None | |
3/18/2011 | 1.05 | None | |
12/17/2010 | 1.05 | Minor | |
11/15/2010 | 1.04 | None | |
9/27/2010 | 1.04 | None | |
7/23/2010 | 1.04 | None | |
6/29/2010 | 1.04 | Editorial | |
6/7/2010 | 1.03 | Editorial | |
4/30/2010 | 1.02 | Editorial | |
3/31/2010 | 1.01 | Editorial | |
2/19/2010 | 1.0 | Major | |
11/6/2009 | 0.3 | Editorial | |
8/28/2009 | 0.2 | Major | |
7/13/2009 | 0.1 | Major |
From time to time, Microsoft maypublish a preview, or pre-release, version of an Open Specifications technicaldocument for community review and feedback. To submit feedback for a previewversion of a technical document, please follow any instructions specified forthat document. If no instructions are indicated for the document, pleaseprovide feedback by using the Open Specification Forums.
The preview period for a technical document varies.Additionally, not every technical document will be published for preview.
A preview version of this document may beavailable on the Word,Excel, and PowerPoint Standards Support page. After the previewperiod, the most current version of the document is available on this page.
Findresources for creating interoperable solutions for Microsoft software,services, hardware, and non-Microsoft products:
Plugfestsand Events, Test Tools,DevelopmentSupport, and Open SpecificationsDev Center.
Technical Documentation. Microsoft publishes OpenSpecifications documentation (“this documentation”) for protocols, fileformats, data portability, computer languages, and standards support.Additionally, overview documents cover inter-protocol relationships andinteractions.
Copyrights. This documentation is covered by Microsoftcopyrights. Regardless of any other terms that are contained in the terms ofuse for the Microsoft website that hosts this documentation, you can makecopies of it in order to develop implementations of the technologies that aredescribed in this documentation and can distribute portions of it in yourimplementations that use these technologies or in your documentation asnecessary to properly document the implementation. You can also distribute inyour implementation, with or without modification, any schemas, IDLs, or codesamples that are included in the documentation. This permission also applies toany documents that are referenced in the Open Specifications documentation.
No Trade Secrets. Microsoft does not claim any tradesecret rights in this documentation.
Patents. Microsoft has patents that might cover yourimplementations of the technologies described in the Open Specificationsdocumentation. Neither this notice nor Microsoft's delivery of thisdocumentation grants any licenses under those patents or any other Microsoftpatents. However, a given Open Specifications document might be covered by theMicrosoft Open SpecificationsPromise or the Microsoft CommunityPromise. If you would prefer a written license, or if thetechnologies described in this documentation are not covered by the OpenSpecifications Promise or Community Promise, as applicable, patent licenses areavailable by contacting iplg@microsoft.com.
License Programs. To see all of the protocols in scopeunder a specific license program and the associated patents, visit the Patent Map.
Trademarks. The names of companies and products containedin this documentation might be covered by trademarks or similar intellectualproperty rights. This notice does not grant any licenses under those rights.For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
Fictitious Names. The example companies, organizations,products, domain names, email addresses, logos, people, places, and events thatare depicted in this documentation are fictitious. No association with any realcompany, organization, product, domain name, email address, logo, person,place, or event is intended or should be inferred.
Reservation of Rights. All otherrights are reserved, and this notice does not grant any rights other than asspecifically described above, whether by implication, estoppel, or otherwise.
Tools.The Open Specifications documentation does not require the use of Microsoftprogramming tools or programming environments in order for you to develop animplementation. If you have access to Microsoft programming tools andenvironments, you are free to take advantage of them. Certain OpenSpecifications documents are intended for use in conjunction with publicly availablestandards specifications and network programming art and, as such, assume thatthe reader either is familiar with the aforementioned material or has immediateaccess to it.
Support.For questions and support, please contact dochelp@microsoft.com.