Document Features Supported on WordprocessingML Import


Feature Supported Comment See Also
Attached Template Yes Attached template is used to reference styles and other settings through the use of a separate document template.

The link to this template is imported from the source document and can be found in the API as the Document.AttachedTemplate property.
- Document.AttachedTemplate
Built-In Properties Yes All Built-in Document Properties can be accessed and modified in Aspose.Words API.

There are methods to update the “count” properties such as character, word and page count. All such properties are supported with the exception of the “line” count which is currently not updated.

- Document.BuiltInDocumentProperties

- Document.UpdatePageLayout

- Document.UpdateWordCount

Custom Properties Yes Custom Document Properties can be created, accessed and modified through the API. - Document.CustomDocumentProperties
Custom Payload Part N/A    
Custom XML Data Storage Planned Custom XML Parts can be accessed and modified in the DOM.

You can remove schemas linked to a part, however you cannot schemas in the document that are not referenced.

This feature will be supported in a future version.
- Document.CustomXmlParts
Digital Signature N/A Digital signatures cannot be added to WordML format.  
Embedded Package Yes

Embedded packages are generally supported by Aspose.Words. There are two ways documents can be embedded inside other documents:

- OLE (this is available in DOC and OOXML formats)

- Package Embedding (available in OOXML only)

Content can be extracted from both types of embedded packages by using the OleFormat.Save method.

Aspose.Words supports these in the following ways during conversion:

If you have an OLE embedded or linked object it will be preserved during any conversion (e.g. DOC to DOCX or DOCX to DOC etc).

If you have a Package Embedded document, then it will only be preserved during DOCX to DOCX conversion.

There is no way to save a Package Embedded document from DOCX into a DOC file without converting it into an OLE embedded object. Implementing conversion of Package Embedded to OLE is tricky and it will take a while to implement.

OLE objects contain “native data” and are supposed to be created by the actual OLE creating application. We at Aspose.Words have never attempted or planned to replace the behavior of OLE creating applications.

- Shape.OleFormat
Encryption N/A    
Font Table Yes    
Glossary Document/Quick Parts/Auto Text Planned   - Document.GlossaryDocument
Hyphenation Yes There is currently no API to access and modify hypenation settings in a document. - ParagraphFormat.SuppressAutoHyphens
Key Map Customizations Yes    
Mail Merge Recipient Data Yes   - Document.MailMergeSettings
Office Math N/A    
Themes N/A Only OOXML documents have native support for themes.

During export, theme formatting is applied as direct formatting to WordML

During round-trip back to DOCX this formatting is retained but the theme information is lost.
Toolbar Customizations Yes    
Variables Yes Variables allow you to store additional information in the document which is “hidden” from the main document.

This can be used to embed custom tracking data in the document itself.
- Document.Variables
VBA Project (Macro) Yes VBA Projects are preserved during open and save to different formats that support them. This means you can load an existing template/document and add content to it and the VBA Projects will remain properly.

There is no API to access the code behind or execute any of the macros. There is a method provided to remove all macros from a document.
- Document.RemoveMacros
VBA Project Digital Signature Yes The digital signature on a VBA Project is preserved during open and save even if the document content is modified.  
Background Yes A background of a Word document can be a solid color or an image. - Document.BackgroundShape
Thumbnail Planned   - BuiltInDocumentProperties.Thumbnail

Embedded Fonts

Feature Supported Comment See Also
Embed Fonts N/A    
Access and Use Embedded Fonts N/A    


Feature Supported Comment See Also
Bibliography Yes Bibliography content is preserved on import.

Updating a bibliography is currently unsupported.
Sources/Citations Yes Sources and citations are preserved during import.

Inserting new sources is not supported.
Citation Style Yes Document-wide citation style is preserved but there is no access to this setting in the DOM.  


Aspose.Words supports most document protection features.

Using Aspose.Words you can open a document that is password protected even without the password (as long as its not encrypted).

Once loaded you can remove any protection from a document.

See the following links in the documentation for further information:

Feature Supported Comment See Also
Allow Only Comments Yes   - Document.ProtectionType
Allow Only Form Fields Yes   - Document.ProtectionType
Allow Only Revisions Yes When this protection type is enabled, tracked changes are automatically turned on.

- Document.ProtectionType

- Document.TrackChanges

Limit Formatting to Selection of Styles Planned    
Protection Password (Legacy) Yes   - WriteProtection.SetPassword
Protection Password (OOXML) N/A    
Protected Sections Yes   - Section.ProtectedForForms
Protection Ranges Planned Currently protected ranges are lost upon import.  
Read Only Yes  

- Document.WriteProtection

- WriteProtection.IsWriteProtected


Feature Supported Comment See Also
Asian Typography Settings Yes    
Compatibility Options Yes   - Document.CompatibilityOptions
Endnote Options Yes   - Document.EndnoteOptions
Footnote Options Yes   - Document.FootnoteOptions
Mail Merge Settings Yes You can modify all mail merge settings, as well as setting a new mail merge data source for the document to use. - Document.MailMergeSettings
Print Settings Yes   - Section.PageSetup
Show/Hide Settings Yes    
View Settings Yes   - Document.ViewOptions
Web Settings Yes    
XML Settings Yes