Document Features Supported on OpenDocument Import
Aspose.Words has impressive support in import and export of OpenDocument 1.1 and 1.2 documents. You can convert any loaded document (such as DOC, DOCX, or HTML) to ODT or start with a ODT document and convert it to any other supported format.
Most features in an OpenDocument have equivalents in Word Documents so conversion between these two formats is normally done with high fidelity.
Aspose.Words always saves documents in the OpenDocument 1.1 format.
See the following links in the documentation for further information:
|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.
All properties are read from ODT, however some Microsoft Word document properties do not have corresponding properties in ODT so will not be present after load.
|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||N/A|
|Digital Signature||Yes||A digital signature ensures that the content of a document has not been tampered with during transit. A signature is applied over the document so if any part of it is modified the signature is invalidated.
When you load a document into Aspose.Words the document signature is automatically lost. This is by design as the document is not the same anymore. You will need to reapply another signature during export, however currently Aspose.Words only signs PDF documents on output.
There are plans to support signing documents on export when saving in the OOXML, DOC, ODT or XPS format.
Detection, access and verification of digital signatures is supported.
Signing is not yet supported.
|Encryption||Planned||Encrypted documents can be loaded into Aspose.Words as long as the password supplied on load for the document is correct.
XOR obfuscation is currently unsupported.
Encrypting a document during save is currently unsupported with the exception when saving in DOC format.
Encrypted ODT documents may encounter an exception during load.
|Glossary Document/Quick Parts/Auto Text||N/A|
|Hyphenation||Yes||There is currently no API to access and modify hypenation settings in a document.||- ParagraphFormat.SuppressAutoHyphens|
|Key Map Customizations||N/A|
|Mail Merge Recipient Data||N/A|
|Themes||N/A||Only OOXML documents have native support for themes.
During export, theme formatting is applied as direct formatting to ODT.
During round-trip back to DOCX this formatting is retained but the theme information is lost.
|VBA Project (Macro)||N/A||Macros are not supported in ODT format.|
|VBA Project Digital Signature||N/A|
|Access and Use Embedded Fonts||N/A|
|Bibliography||Yes||Bibliography content is preserved on import.
Updating a bibliography is currently unsupported.
Bibliography text is saved to ODT as normal text.
|Sources/Citations||Yes||Sources and citations are preserved during import.
Inserting new sources is not supported.
Bibliography sources are not saved to ODT.
|Allow Only Comments||N/A|
|Allow Only Form Fields||N/A|
|Allow Only Revisions||N/A|
|Limit Formatting to Selection of Styles||N/A|
|Protection Password (Legacy)||N/A|
|Protection Password (OOXML)||N/A|
|Protected Sections||Yes||- Section.ProtectedForForms|
Footnote, Endnote and View settings are imported when loading an ODT format document.
|Asian Typography Settings||N/A|
|Endnote Options||Yes||- Document.EndnoteOptions|
|Footnote Options||Yes||- Document.FootnoteOptions|
|Mail Merge Settings||N/A|
|View Settings||Yes||- Document.ViewOptions|